ARVO
LOCK IN

Cookie Policy

Last updated: [LAST UPDATED DATE]

This Cookie Policy explains how ARVO ("ARVO", "we", "us", or "our") uses cookies and similar browser-storage technologies when you use the ARVO website and application.

Operator: [LEGAL ENTITY / OPERATOR NAME]

Contact: [PRIVACY / SUPPORT EMAIL]

1. What are cookies and similar technologies?

Cookies are small pieces of information that websites may store on your device.

Web applications may also use similar browser technologies such as:

  • local storage;
  • session storage;
  • authentication/session storage;
  • other browser-based storage mechanisms.

For simplicity, this Policy describes both cookies and relevant similar technologies used by ARVO.

2. How ARVO uses browser storage

ARVO currently uses browser storage primarily to operate the Service and remember functional preferences.

This may include storage used for:

  • authentication and session management;
  • maintaining signed-in state;
  • language preference;
  • appearance/theme preference;
  • selected trading account;
  • application state or preferences required for functionality.

3. Strictly necessary / functional technologies

Some storage mechanisms are necessary for ARVO to function correctly.

For example, ARVO may need to maintain authentication/session information so that a signed-in user can securely access their account.

Functional storage may also remember preferences so that users do not need to configure the same settings every time they use the Service.

Disabling necessary browser storage may prevent parts of ARVO from functioning correctly.

4. Authentication

ARVO uses authentication infrastructure associated with Supabase / Lovable Cloud.

Authentication-related browser storage may be used to:

  • maintain your signed-in session;
  • authenticate requests;
  • refresh or preserve session state;
  • protect access to authenticated features.

Exact technical storage names and durations may depend on the authentication infrastructure and configuration used by the Service.

5. Local preferences

ARVO may use browser storage for functional preferences such as:

  • language;
  • theme or appearance;
  • selected account;
  • other user-interface preferences.

These technologies are intended to improve the functional experience of using ARVO rather than to create advertising profiles.

6. Analytics cookies

At the time represented by this Cookie Policy template, the audited ARVO application does not contain an identified analytics tracking service.

Accordingly, ARVO is not currently describing analytics cookies as an active category of tracking technology.

If analytics technology is introduced later, this Policy and any applicable consent mechanism must be reviewed before or when that technology is deployed.

7. Advertising and marketing cookies

At the time represented by this template, the audited ARVO application does not contain identified advertising or marketing tracking technologies.

ARVO therefore does not currently use the audited application to place advertising/marketing cookies for behavioural advertising.

If this changes, this Policy must be updated and appropriate consent controls implemented where required.

8. Third-party services

Certain third-party services used by ARVO may process technical information or use their own mechanisms where necessary to provide their functionality.

Current relevant services may include:

  • Supabase / Lovable Cloud infrastructure;
  • Google authentication;
  • Google-hosted fonts or related resources where currently implemented.

Where you interact with a third-party provider, its own privacy and cookie practices may also apply.

9. Google authentication

If you choose Google as an authentication method, Google may use cookies or other technologies as part of its own authentication service.

Those technologies are controlled by Google and are subject to Google's own policies.

ARVO does not control Google's independent processing outside ARVO's own Service.

10. Cookie consent

Based on the current audited ARVO implementation, no analytics or advertising tracking service was identified.

The currently identified ARVO browser-storage mechanisms are primarily authentication and functional technologies.

Whether a particular consent mechanism is legally required depends on the technologies actually deployed, the user's jurisdiction, and applicable law.

If ARVO introduces non-essential technologies in the future, the consent implementation must be reviewed before those technologies are activated for users where prior consent is required.

11. Managing browser storage

You can control or delete cookies and browser storage through your browser settings.

Blocking or deleting authentication or functional storage may:

  • sign you out of ARVO;
  • reset preferences;
  • prevent authenticated functionality from working correctly;
  • require you to configure preferences again.

12. Storage inventory

Before final publication, insert the verified production storage inventory here.

Suggested format:

NAME / KEY: [STORAGE KEY]

TYPE: [COOKIE / LOCAL STORAGE / SESSION STORAGE]

PURPOSE: [PURPOSE]

CATEGORY: [STRICTLY NECESSARY / FUNCTIONAL]

DURATION: [DURATION]

PROVIDER: [ARVO / SUPABASE / OTHER]

Only include technologies actually used by the production application.

Do not add generic analytics or marketing cookies that ARVO does not use.

13. Changes to this Cookie Policy

ARVO may update this Cookie Policy when:

  • browser-storage practices change;
  • new functionality is introduced;
  • third-party services change;
  • applicable legal requirements change.

The "Last updated" date at the top will indicate the latest revision.

14. Contact

For questions about ARVO's use of cookies or similar technologies, contact:

[LEGAL ENTITY / OPERATOR NAME]

Privacy: [PRIVACY EMAIL]

Address: [REGISTERED ADDRESS]

Jurisdiction: [JURISDICTION]