Information used while exploring Marius Jasevicius’s data visualization design portfolio, preparing a project outline and deciding whether to start an email conversation.
1. Responsible professional and scope
This portfolio identifies MARIUS JASEVICIUS, an independent professional using the public name Marius Jasevicius, at 3700 McKinney Ave, Apt 2107, Dallas, TX 75204-1687, United States. Privacy questions can be addressed in an email draft to [email protected]. This notice describes the public portfolio and its enquiry interface. It also explains the boundary between information entered on a page, information handled by the services that deliver the page, and information you separately decide to send by email. It does not describe the internal practices of your own device, network or email provider.
2. Information you choose to provide
The project outline can contain your name, reply email, optional company or project name, selected area and message. For data visualization design, useful context is data definitions, sample tables, chart requirements and the question the report should answer. Only enter material you are entitled to share. An initial outline does not need identifiable customer rows, confidential business measures and unrestricted database access. There is no attachment control or request for an identity document. If a later project requires original files, first agree the transfer route, the intended purpose and the people who may access them. The form keeps a preview in your current page; it does not create an enquiry record on a website server.
3. What the form actually does
The chart-design form helps you assemble a short brief in the browser. A selected service, name, reply address, optional project name and written outline can appear in a local draft preview. It does not import a spreadsheet or connect to a data warehouse. Balance and Daylight use local illustrative images, not a visitor’s data. The separate mailto link can pass a draft into your configured email application; sending remains an additional action there. Preparing the outline creates no project account or website enquiry record.
4. Email and communication providers
Opening a mailto link passes the draft to the email application or service configured on your device. That provider may handle addresses, message contents, device details and its own service records under its policies. When you send a message, delivery can involve your provider, network services and the recipient's provider. This portfolio cannot control those systems, confirm that they have accepted a draft, or verify successful delivery. Check the final recipient, contents and any attachments in your email application before sending, especially when more than one email account is configured.
5. Purposes of an enquiry conversation
An initial data-visualization discussion can often use column definitions, a redacted sample or a description of the comparison. Do not paste private customer rows, health records, financial account details or database credentials into the outline. If actual source data is needed later, agree access, recipients and the intended analysis before transferring it. The portfolio’s form has no permission system for a dataset. A visually clear sample does not establish that it is appropriate to share the underlying information through an unrestricted email conversation.
6. Website delivery and technical data
Requesting a web page necessarily sends connection information to the infrastructure serving it. This can include an internet protocol address, the requested resource, approximate request time and browser or protocol information. Hosting, content delivery and security providers may process such information to deliver resources, handle failures or protect their networks. Their operational settings and applicable terms govern their own processing. A public page cannot establish every provider's logging or retention behavior. This notice therefore does not promise anonymous browsing or that the delivery infrastructure keeps no records.
7. Local assets, cookies and browser storage
The example chart values are fixed fictional content served with the page. No live analytics dataset is queried by the illustrations. Local fonts, graphics and the enquiry script load from the portfolio paths; the authored script does not write a data cache, cookie, localStorage or sessionStorage entry. A browser can still retain form entries through autofill or session restoration. Hosting and content-delivery services may process connection data to serve the resources. Their independent records are not the same as a saved copy of your proposed dataset.
8. Analytics, email protection and links
Cloudflare delivers this portfolio and may add Web Analytics for traffic and performance measurement, email-address protection and network error reporting headers. These features can process request, connection, browser and resource information independently of the local enquiry form. The page itself does not submit form fields to a website database. Its fonts and original example assets load from local paths. There are no social feeds, external media embeds, payment controls or file uploads. Your email provider has its own policies when you decide to open or send a draft. Browser site-data settings let you inspect and manage data held on your device.
9. Access, recipients and locations
An email discussion may be handled using communication and hosting services that operate in different countries. The site does not infer a visitor's residence from its English language or select a jurisdiction for them. Necessary service providers can process information within their roles, while any additional project recipient or collaborator should be addressed as part of the engagement discussion. Do not assume that sharing material through an initial enquiry establishes a confidentiality arrangement. If location, access restrictions or a particular transfer method matter to your project, raise those requirements before transmitting the material.
10. Retention and deletion requests
Retention questions should distinguish source tables from communication about a design brief. A dataset shared in a later engagement, a sent email and an unsent browser preview can have different purposes and custodians. The website does not establish a universal deletion schedule for those materials. Ask about the relevant message or project using enough context to locate it, rather than resending a complete private table. Handling a request may need to account for an ongoing engagement, applicable obligations and records held by your own email provider.
11. Security and practical choices
A dataset may identify people even when the chart intended for publication is aggregated. Consider whether a column description or a redacted sample is enough for the first design discussion. Avoid sending unrestricted database access or private rows through the outline. If a later engagement needs source information, establish the appropriate access route and review responsibilities. Local draft preparation is not a security review of that information. Check the email recipient and your provider’s controls before choosing to transmit any material.
12. Requests, children and updates
You can use the contact email to ask about information associated with your own enquiry, seek a correction, object to a proposed use or request removal where applicable. The appropriate handling depends on the request and relevant obligations; this notice does not replace rights that apply to you. Someone acting for another person should explain that authority. The portfolio is intended for professional design enquiries and is not directed at children. The notice may be updated when the site or communication workflow changes; the displayed revision date identifies the current published version.