1. Introduction
VENTRYA LTD, trading as Mail.Land, uses cookies, local storage, session storage, and similar browser technologies to operate the MailLand website and platform, keep you signed in, remember your preferences, and support certain security and verification workflows. This policy explains what these technologies are, why we use them, and how you can manage them.
These technologies work differently:
- Cookies are small text files sent by our servers and stored by your browser. Depending on how a cookie is set, it may be sent back to our servers with future requests (a regular cookie) or marked HttpOnly, which means it is sent with requests but cannot be read or modified by JavaScript running on the page. HttpOnly cookies protect the values they hold from being accessed by client-side scripts, including malicious scripts introduced through cross-site scripting.
- Local storage is a browser feature that lets a website store data on your device. Unlike cookies, local storage is not automatically sent to our servers with each request, and it persists until it is changed, removed, or your browser storage is cleared.
- Session storage works like local storage but is scoped to a single browser tab and is cleared when that tab is closed.
Consent requirements may vary depending on applicable law and future use of additional tracking technologies.
2. Cookies
MailLand uses a small number of cookies, all of which are essential to operating the platform or support a specific security feature you opt into.
access_token, refresh_token, and trusted_device are set as HttpOnly cookies, meaning JavaScript running on the page cannot read or modify them. csrf_token is intentionally readable by JavaScript, because our double-submit CSRF protection requires the page to read its value and echo it back on state-changing requests; this is a standard part of the double-submit pattern and does not weaken the protection it provides. In production, access_token, refresh_token, csrf_token, and trusted_device are also set with the Secure attribute, so they are only sent over HTTPS connections.
| Cookie Name | Purpose | Type | HttpOnly | Duration |
|---|---|---|---|---|
| access_token | Authenticates your session | Essential | Yes | Approximately 60 minutes |
| refresh_token | Renews your session without requiring you to sign in again | Essential | Yes | Approximately 7 days |
| csrf_token | Cross-site request forgery protection (double-submit pattern); intentionally readable by JavaScript so the page can echo its value back to our servers | Essential | No | Approximately 60 minutes, aligned with the access-token session lifecycle |
| trusted_device | Reduces repeated verification steps on a device you have marked as trusted | Security / Functional | Yes | 30 days; only written after you explicitly choose "Trust this device" |
| NEXT_LOCALE | Remembers your language preference | Functional | No | Not explicitly configured by MailLand; the duration follows the framework's and browser's default handling |
If we introduce additional cookies in the future, we will update this policy to describe them.
3. Local Storage
We use local storage to remember preferences and application state on your device between visits. Local storage data is not automatically sent to our servers; it is read by the application when needed.
| Key | Purpose | Retention |
|---|---|---|
| theme | Remembers your preferred display mode (light or dark) | Persists until you change it or clear your browser storage |
| activeTenantId | Stores your currently selected tenant so the platform loads the right workspace context | Persists until you log out, change tenants, or clear your browser storage |
| lastActiveWorkspaceId_<tenantId> | Remembers, per tenant, which workspace you last used | Persists until reset, the workspace becomes invalid, or you clear your browser storage |
| business_verification_draft | Stores a draft of your business verification submission so your progress is not lost. This can include business details, how you acquired your contacts and any opt-in descriptions, sample email subject lines and content, your email service provider and deliverability history, your suppression-list practices, and related notes | Persists until you successfully submit the form, clear it manually, replace it with a new draft, or clear your browser storage |
| mailland-status:last-document | Caches the last public status response on the Mail.Land status page, so the page can still show the last known service status if the live status feed is temporarily unavailable | No automatic expiry; overwritten by each newer status response and persists until you clear your browser storage |
| mailland-status:view | Remembers whether you chose the 24-hour or the 90-day uptime bars on the Mail.Land status page | Persists until you change the choice or clear your browser storage |
Status page cache. The key mailland-status:last-document is used only by the public Mail.Land status page. It is a functional item that is strictly necessary to show you the last known service status when the live status feed is unavailable. It stores only the public status document, contains no personal data, is not sent to our servers by the page and is not used for tracking or advertising, so no consent is required for it.
Status page subscribe form. When you open the subscribe dialog on the public Mail.Land status page, the page loads Cloudflare Turnstile from challenges.cloudflare.com to check that a person, not an automated script, is asking for status updates. Cloudflare, already one of our sub-processors, processes technical information such as your IP address and browser characteristics for that check. Turnstile is not loaded on any other page or before you open the dialog, and we do not use it for tracking or advertising.
4. Session Storage
We use session storage for short-lived data that only needs to exist for the current browser tab. Session storage is cleared automatically when you close the tab.
| Key | Purpose | Retention |
|---|---|---|
| verification_ticket | Temporary credential used during the email verification workflow | Current browser tab; removed after verification succeeds |
| masked_email | Stores the email display value used during verification; the application uses the masked address when the server supplies one, but may store the returned email address as a fallback | Current browser tab; removed after verification succeeds |
| admin_access_token | Authenticates an admin session | Current browser tab; cleared on logout |
| admin_refresh_token | Renews an admin session | Current browser tab; cleared on logout |
| admin_token_expiry | Tracks when the admin session token expires | Current browser tab; cleared on logout |
| admin_info | Stores serialized admin profile and session information used by the admin interface | Current browser tab; cleared on logout |
| sandbox-banner-dismissed | Remembers that you dismissed a sandbox/test-environment banner | Current browser tab |
5. Managing and Deleting These Technologies
You can manage or delete cookies, local storage, and session storage through your browser settings. Most browsers allow you to view, delete, and block cookies and site storage. Please note that blocking or deleting the essential cookies described above, or clearing local storage used to identify your active tenant, may prevent you from signing in or using parts of the MailLand platform.
Here is a brief guide for managing cookies and site storage in the most common browsers:
- Google Chrome: Open Settings, then navigate to Privacy and Security, then Cookies and other site data. From there you can view, block, or delete cookies and site storage.
- Mozilla Firefox: Open Settings, then navigate to Privacy and Security. Under the Cookies and Site Data section, you can manage your cookie preferences and clear stored data.
- Apple Safari: Open Preferences (or Settings on iOS), then navigate to Privacy. You can manage cookies and site data through the Website Tracking and storage options.
- Microsoft Edge: Open Settings, then navigate to Cookies and site permissions, then Manage and delete cookies and site data.
Please be aware that clearing site storage will remove saved preferences and drafts described in this policy, such as a saved theme choice or an unsubmitted business verification draft.
6. Changes to This Policy
We may update this Cookie and Local Storage Policy from time to time to reflect changes in the technologies we use, changes to the platform, or changes in applicable laws and regulations. When we make changes, we will update the effective date at the top of this page.
We encourage you to review this policy periodically to stay informed about how we use cookies, local storage, and session storage. Your continued use of the MailLand website and platform after any changes to this policy constitutes your acceptance of the updated policy.
7. Contact Us
If you have any questions or concerns about our use of cookies, local storage, or session storage, please contact us at [email protected].
For broader information about how we collect, use, and protect your personal data, please refer to our Privacy Policy.