This policy covers browser storage and external resources on Supra Core's public informational pages, operated by TCP Labs. For personal information, recipients and your rights, read our Privacy Policy. You can contact us at info@supra-core.app.
1. Cookies, browser storage and requests
A cookie is information a browser can store and send with subsequent matching HTTP requests. Local storage and session storage are different: scripts read and write them within the website's browser storage, and the browser does not automatically attach their contents to every HTTP request.
Local storage can persist across visits. Session storage belongs to a page session, normally lasting until the tab or window is closed; browser session restoration can affect that lifetime. Browser settings can block or clear either technology.
A connection to an external service is a network request, not itself a cookie. It can nevertheless disclose your IP address and request headers to that service. The distinction matters: cookie controls alone do not prevent external resource requests.
Language preference
The supra_language cookie remembers your language choice for one year across the public site and workspace. It is a first-party preference cookie, not an authentication or tracking cookie. It uses Path=/, HttpOnly and SameSite=Lax, and Secure on HTTPS. You can change the language using the selector or remove this cookie in your browser; English is the default.
2. Preferences and form security
These pages store your requested display preference, your privacy choice and short-lived form-security data. No advertising or audience-analytics category is enabled by the site. Google reCAPTCHA is a separate optional connection for the contact form.
On smaller screens, scroll the table horizontally. You can also focus the table area with the keyboard.
| Name | Technology | Purpose and use | Provider | Persistence and deletion |
|---|---|---|---|---|
theme |
Local storage | Remembers light or dark mode when you use the theme button. Read on page load; dark mode is the default without a saved choice. | TCP Labs / Supra Core, first-party | No expiry is set by the page. Remains until cleared or evicted by the browser; changing the theme replaces the value. |
supra_privacy_v1 |
Local storage | Remembers an explicit acceptance or rejection of contact-form protection, with its version and expiry. It is not written merely because you visit a page. | TCP Labs / Supra Core, first-party | The choice is valid for 180 days after saving. An expired entry is ignored; changing the choice replaces it. Browser controls can remove it earlier. |
__Host-supra_contact |
Secure, HttpOnly, SameSite=Strict cookie | Binds a form verification token to this browser when you start a submission. It protects against forged requests; it is not an account session. | TCP Labs / Supra Core, first-party | Expires after 30 minutes; starting another submission renews that expiry. Only sent over HTTPS to this website. |
_GRECAPTCHA |
Provider cookie | Google documents this cookie for risk analysis when reCAPTCHA executes. The integration loads only after permission and a contact-form submission. | Expiry and any other Google cookies depend on the provider and browser. Use browser site-data controls to inspect or remove them; withdrawing site permission does not delete Google's cookies. |
The first-party preferences and form-security cookie belong to this website's origin; they are not shared across unrelated websites by that storage mechanism. They are not a login session and contain no password or API key. This description does not apply to Google's cookies, which belong to the provider's domains.
3. Optional reCAPTCHA and other resources
The public pages do not import Google Fonts. If you enable contact-form protection and submit a message, the landing loads Google reCAPTCHA v3 from www.google.com, with related resources from Google domains such as www.gstatic.com. Google receives network, browser and interaction information to assess the request. Existing Google cookies may also be sent according to browser rules.
reCAPTCHA is not loaded merely by visiting a page or saving an acceptance. A remembered acceptance allows it to load when you next submit the contact form. The resources may be cached according to browser rules and provider headers. See the reCAPTCHA FAQ, Google Privacy Policy and Google Terms of Service.
The page scripts, icons, images and Halo animation libraries are served as website assets. Loading local assets is distinct from following a link to GitHub, X or another external website. Those destinations apply their own storage and privacy practices when you visit them.
4. Your choices and consent
Use the theme button to change the appearance. To remove stored preferences, use your browser's site-data controls for this website. Clearing cookies alone may not clear local or session storage: include site data in the deletion. Clearing the theme preference returns these pages to their default appearance on the next load.
A privacy banner appears on your first visit and whenever no valid saved choice is available. Accept all, Reject non-essential and Customize use the same saved preference as the form and the panel reopened from the contact form or this Cookie Policy. Acceptance and rejection have equal prominence; there are no optional analytics or advertising switches. Closing the banner without choosing gives no permission. Both acceptance and rejection are remembered for 180 days across page visits and browser sessions, unless you clear site data. Clearing cookies alone does not necessarily remove the choice in local storage.
Use the Privacy choices button on this page or in the contact form to change your decision. Without permission, use the email address next to the contact form. Acceptance does not load Google until you submit the form. The required acknowledgement of the Privacy Policy is not consent to reCAPTCHA.
If reCAPTCHA has loaded, withdrawing permission reloads the page to stop it; unsent form text is discarded. Withdrawal cannot undo requests already made or remove provider cookies. Blocking browser storage prevents a saved permission from enabling the form. Clearing browser data does not erase request records or correspondence held by service providers.
Rules on device storage apply to similar technologies as well as cookies. Consent is required where the legal exception for transmission or a service explicitly requested by the user does not apply. The functional purpose of a setting is not a blanket exemption for other uses.
Merely visiting the site, scrolling or following a policy link does not provide consent to tracking.
5. Updates and contact
This policy will be revised when the storage or resources described here change, with the update date shown above. A policy update does not replace consent where it is required.
For questions about browser data, contact info@supra-core.app. Information about your personal-data rights and how to make a complaint is in the Privacy Policy.