Crofts policies
Cookie Policy
This policy describes cookies and similar browser storage used by Crofts. It is based on the application’s current implementation; providers and storage may change as the service develops.
Last updated: 20 November 2026
Effective date: [EFFECTIVE DATE]
2. How Crofts uses cookies and similar technologies
The current application uses browser storage for authentication, a short-lived bank linking flow, optional interface preferences and form continuity. Vercel Analytics is integrated for site-usage events but is not mounted unless you allow analytics. The application does not currently configure marketing or advertising cookies.
Here is the storage identified in the application code. Some keys contain an account or project identifier rather than a fixed value.
| Cookie / Storage Key | Provider | Purpose | Category | Duration |
|---|---|---|---|---|
| sb-<project-ref>-auth-token (localStorage) | Supabase | Keep the signed-in session available and refresh it. | Strictly necessary | Until sign-out, session expiry or browser storage is cleared; exact session settings depend on the Supabase project. |
| crofts:cookie-preferences:v1 (localStorage) | Crofts | Remember your essential, functional and analytics choices. | Strictly necessary | Until you change the choice or clear browser storage. |
| croft-plaid-link-token (sessionStorage) | Crofts / Plaid | Resume a bank-link flow after the user starts linking and returns from an OAuth step. | Strictly necessary for the requested flow | Current browser tab session; removed when the flow succeeds or ends. |
| sidebar_state (cookie) | Crofts | Record the sidebar open/collapsed value when toggled; the current UI does not read it back. | Functional preference (optional) | Up to 7 days, only when functional preferences are allowed. |
| crofts:mortgage-comparison:amount (sessionStorage) | Crofts | Restore the mortgage comparison amount during the current tab session. | Functional preference (optional) | Current browser tab session, only when functional preferences are allowed. |
| croft:add-property-draft:<user-id> (sessionStorage) | Crofts | Keep an unfinished Add Property form draft in the current tab. | Functional preference (optional) | Current browser tab session, only when functional preferences are allowed. |
| No Crofts cookie or browser-storage key identified | Vercel Analytics | Send site-usage events when analytics consent has been given. | Analytics (optional) | No client-side storage duration identified in the Crofts integration; provider-side retention should be confirmed. |
3. Strictly necessary storage
Authentication storage is needed to keep you signed in. The short-lived Plaid Link token is stored only after you start the bank-linking feature and is needed to complete the requested flow. The preference record remembers the choice you made so Crofts can honour it. These items are not optional in the preference panel while the related service is being used.
4. Functional and preference storage
If you allow functional preferences, Crofts may store the sidebar state, the mortgage comparison amount and an unfinished Add Property form in this browser tab. The sidebar cookie currently records its value when toggled but does not restore that value after a reload. These conveniences are not required for the core service. If you reject or later switch off functional preferences, Crofts stops using them and removes the related preference cookie and current-tab form/comparison values where possible.
5. Analytics
Crofts integrates Vercel Analytics to understand site visits and usage. Analytics is optional and is not mounted until you enable it. The Crofts integration does not identify a Vercel Analytics cookie or browser-storage key; it sends analytics events to Vercel. Vercel’s processing and retention are subject to its own terms and configuration.
6. Marketing
The application code reviewed for this policy does not configure marketing or advertising cookies or tags.
7. Authentication and session technologies
Crofts uses Supabase authentication with a session persisted in local storage and automatically refreshed by the Supabase client. A separate, temporary session-storage value supports the Plaid bank-link OAuth flow when you choose to connect an account. Server-side authentication tokens are not browser cookies.
8. Third-party technologies
The app loads its typeface from Google Fonts. This makes a request to Google’s service, which may receive technical information such as your IP address and browser details. The app also includes Vercel Analytics, which only runs after your analytics choice. Optional bank-linking and document-parsing features connect to Plaid and Google Gemini when enabled and used. These services may have their own privacy notices and terms.
9. Managing your choices
You can accept all optional technologies, reject them, or choose functional preferences and analytics separately. Use the controls below or the permanent “Cookie settings” button in the site footer to change your choice later. Strictly necessary storage stays on.
10. Browser settings
Most browsers let you review, block or delete cookies and clear site storage. If you block essential storage, sign-in or other core features may not work correctly. Clearing storage may also remove your saved Crofts preferences.
11. Changes to this policy
We may update this policy when the technologies used by Crofts change or when needed for legal or operational reasons. The latest version and its update date will appear here.
12. Contact
For questions about cookies or privacy, contact [LEGAL ENTITY NAME] at [CONTACT EMAIL] or use the Privacy Policy contact details.