This Cookie Policy explains how ResiSuite uses cookies, browser storage and similar technologies.
1. What these technologies are
Cookies are small files stored by a browser. Local storage and similar technologies may store identifiers, preferences, consent choices or session information on a device.
2. Current categories
Strictly necessary technologies
These are required to provide and secure the service. They may include:
- Supabase authentication and session storage;
- security and fraud-prevention identifiers;
- Cloudflare Turnstile and related security signals;
- load balancing and technical routing;
- cookie-consent records;
- essential interface or language preferences.
Functional technologies
These may remember optional preferences that improve the experience. Where legally required, they will be used only after consent.
Analytics technologies
ResiSuite does not currently activate non-essential analytics unless this is disclosed in the live cookie-preference interface.
If analytics is introduced, the provider, purpose and duration will be added to this policy and the technology will be blocked until consent where required.
Advertising technologies
ResiSuite does not currently activate advertising or behavioural-targeting cookies unless this is disclosed in the live cookie-preference interface.
Advertising technologies will require an appropriate opt-in where required.
3. Consent controls
Where consent is required, users will be offered clear choices:
- Accept all
- Reject non-essential
- Manage preferences
Rejecting non-essential technologies will be as easy as accepting them. Necessary technologies will continue to operate.
Consent choices are primarily stored in the browser. Where appropriate, a consent record may also be associated with an account.
Users may reopen Cookie settings and withdraw or change consent at any time.
4. Third parties
Cookies or similar technologies may be provided by infrastructure and security providers, including Supabase and Cloudflare. Optional analytics, error-monitoring or advertising providers will be identified before activation.
5. Duration
Some technologies expire when the browser session ends. Others remain for a defined period to preserve authentication, security or consent choices. The live cookie-preference interface should display provider and duration where technically available.
6. Browser controls
Users may also delete or block cookies through browser settings. Blocking necessary storage may prevent sign-in or other core functionality.
7. Updates
This policy will be updated when technologies or providers materially change.
8. Contact
Questions: support@mail.getresisuite.com
Current cookie and storage inventory
Exact third-party security names can vary because the provider controls them. This inventory reflects the application code audited for this version.
| Item | Provider / category | Purpose | Duration / status |
|---|---|---|---|
| sb-<project-ref>-auth-token (name may be chunked) First-party | Supabase necessary | Keeps an authenticated ResiSuite session and refresh state. | Cookie max age approximately 400 days; session tokens expire and refresh sooner Currently active |
| resisuite-otp-email First-party | ResiSuite necessary | Completes the requested passwordless email sign-in flow. | 10 minutes, or removed after successful verification Currently active |
| resisuite_cookie_consent First-party | ResiSuite necessary | Stores the device’s cookie category choice and schema version. | 180 days Currently active |
| Cloudflare Turnstile security storage (provider-controlled) Third-party | Cloudflare necessary | Protects email OTP requests from automated abuse when the challenge is used. | Provider-controlled and generally challenge/session limited Currently active |
| In-memory blob: preview URLs First-party | Browser / ResiSuite necessary | Displays a local preview of a selected upload; it is not persistent storage. | Only while a local file preview is open Currently active |
| No analytics keys currently registered First-party | None analytics | Analytics providers are not active in the current application. | Not applicable Not active |
| No advertising keys currently registered Third-party | None marketing | Advertising and behavioural marketing tags are not active. | Not applicable Not active |