Seedable Cookie Policy

Last updated: 11 August 2026

Introduction

This Cookie Policy explains how Seedable (“Seedable”, “we”, “us” or “our”) uses cookies and similar technologies when you access or use our website, platform and related services (the “Platform”).

This policy should be read alongside our Privacy Policy and Terms of Service.

Some cookies and browser-storage technologies are strictly necessary for the Platform to operate, authenticate users, protect accounts and provide features requested by users. These technologies may operate automatically.

Other technologies, including certain analytics and behavioural-measurement technologies, are used only after consent where required by applicable law. Refusing non-essential technologies will not prevent you from accessing the Platform’s essential functions.

What Are Cookies?

Cookies are small text files stored on your device when you visit a website. They allow a website to recognise a browser, maintain a login session, remember preferences and provide requested functionality.

Seedable also uses similar browser technologies, including:

Local storage;
Session storage;
Browser-generated session identifiers;
Scripts that measure interactions with Platform features; and
Authentication tokens used to communicate securely with our service providers.

In this policy, we refer to these technologies collectively as “cookies” unless a distinction is necessary.

Types of Cookies We Use

i. Strictly Necessary Cookies

These cookies and storage technologies are required to operate the Platform and provide services requested by users.

They are used to:

Enable account registration, login and authentication;
Maintain and refresh secure user sessions;
Support email-verification and login-verification flows;
Honour the user’s “remember me” selection;
Complete founder and investor onboarding;
Protect accounts and prevent unauthorised access;
Apply access controls to authenticated pages; and
Support core Platform navigation and functionality.

The strictly necessary cookies currently used by Seedable include:

Cookie or technology	Provider	Purpose	Duration
sb-<project-reference>-auth-token and any numbered or chunked variants	Seedable using Supabase Auth	Stores and refreshes the authenticated session so users can securely sign in and access their accounts	Up to 400 days at browser level under the current Supabase SSR configuration, although the session may expire or be invalidated sooner; removed or invalidated following sign-out or session termination
seedable-pending-verification	Seedable	Maintains the pending account-verification flow	Up to 24 hours or until verification is completed or abandoned
seedable-pending-login-verification	Seedable	Maintains the pending login-verification flow	Up to 15 minutes or until the login flow is completed or abandoned
seedable-session-active	Seedable	Helps Seedable end a session-only login when the user has not selected persistent login	Browser session
seedable-cookie-consent	Seedable	Records the visitor’s cookie choices, consent-policy version and choice timestamp so Seedable can remember and honour those choices	180 days from the most recent choice, or until the visitor changes the choice or clears browser data. Seedable will request a new choice when the cookie expires, is cleared, or the consent framework changes materially. Saving or changing a choice replaces the previous browser preference. For authenticated users, Seedable also keeps a restricted server-side record of consent, refusal, changes and withdrawal so that Seedable can demonstrate and honour those choices. The retention of those records is explained in the Privacy Policy.
seedable-founder-onboarding	Seedable	Maintains the founder onboarding flow and associated route access	Up to 24 hours or until onboarding is completed
seedable-investor-onboarding	Seedable	Maintains the investor onboarding flow and associated route access	Up to 24 hours or until onboarding is completed

These cookies do not require consent where they are strictly necessary to provide the service requested by the user. Blocking them through browser settings may prevent login, verification, onboarding or other essential Platform features from working correctly.

ii. Functional Cookies

Functional storage technologies remember choices and provide user-requested features.

Seedable currently uses local storage for purposes including:

Remembering the selected light or dark theme;
Remembering whether a user selected a persistent or session-only login;
Temporarily remembering an email address during registration or login verification;
Enforcing short resend-code cooldowns;
Remembering the current founder or investor onboarding step;
Maintaining unread-message counts and recently seen message identifiers; and
Remembering a limited history of recently searched or viewed profiles so the user can revisit or clear that history.

Relevant local-storage entries include:

Storage entry	Purpose	Duration
seedable-theme	Remembers the user’s light or dark theme preference	Until changed by the user, removed by Seedable or cleared through browser settings
Verification and login entries beginning with seedable-pending-, seedable-verification- or seedable-login-	Supports verification, login and resend-code flows	Until the relevant flow is completed or abandoned, the application removes the entry, or browser storage is cleared
seedable-session-mode	Remembers whether the user selected persistent or session-only login	Until sign-out, removal by the application or browser-storage clearance
Entries beginning with seedable:founder-onboarding: or seedable:investor-onboarding:	Remembers an authenticated user’s onboarding step	Until onboarding is completed, the application removes the entry or browser storage is cleared
Entries beginning with seedable:unread-messages: or seedable:seen-unread-messages:	Supports unread-message and notification functionality	Until overwritten or removed by the application or browser storage is cleared
Entries beginning with seedable:profile-history:	Stores a limited history of recently searched and viewed profiles	Until cleared by the user, overwritten or removed by the application, or browser storage is cleared

Where applicable, Seedable will provide a simple way to object to optional functional storage without affecting strictly necessary features.

iii. Analytics and Performance Technologies

Seedable uses browser-side measurement to understand how authenticated users interact with pitches in the Discover experience and to operate and improve Discover ranking.

The current Discover measurement records:

The authenticated viewer’s account identifier;
A randomly generated identifier for the current Discover page visit;
The identifier of the startup or pitch displayed;
Whether a pitch impression occurred;
The time of the first recorded impression;
Whether the viewer reached a meaningful view;
Cumulative qualifying active watch time;
The furthest point reached through natural video playback;
The video’s duration;
Whether the viewer opened the startup’s profile; and
Relevant event and update timestamps.

A pitch impression is currently recorded when at least 60% of the pitch card remains visible for at least 1 continuous second. A meaningful view is currently recorded after at least 5 seconds of qualifying active playback. Qualifying playback is measured only while the pitch is playing, sufficiently visible, the browser document is visible, the player is not seeking and the media is ready.

The temporary Discover page-visit identifier is generated in the browser and is not currently placed in persistent local storage. The interaction record is sent to and stored in Seedable’s Supabase database. The authenticated Supabase session is used to associate the record with the logged-in viewer.

These records are used to:

Measure pitch visibility and engagement;
Understand how users interact with Discover;
Calculate aggregated engagement metrics;
Improve Platform performance and usability;
Identify technical or playback issues;
Evaluate pitch engagement; and
Influence the ordering and relevance of pitches shown through the Discover ranking system.

Because these records can be associated with an authenticated user and may influence content ordering, they are not described as anonymous analytics.

Seedable does not currently use Google Analytics, Meta Pixel or a comparable third-party advertising analytics tool on the Platform. If such a tool is introduced, this policy and the consent controls will be updated before it is enabled.

Server-side retention of Discover interaction records is governed by the retention provisions in our Privacy Policy. Seedable retains individual-level records only for as long as reasonably necessary for the stated purposes and applies deletion or anonymisation in accordance with its documented retention process.

iv. Communication and Engagement Cookies

Seedable uses cookies and local storage to support communication and engagement features, including:

Maintaining authenticated access to messaging;
Displaying unread-message counts;
Avoiding duplicate unread-message notifications;
Supporting notifications and message-status updates; and
Delivering pitch videos and other user-requested content.

These technologies do not read private message content for advertising purposes.

Supabase provides database, authentication, storage and real-time infrastructure supporting these features. Seedable may also use server-side email-delivery providers for transactional messages such as verification emails. A server-side email provider is not treated as setting a browser cookie unless it actually stores or accesses information on the user’s device.

v. Advertising and Tracking Cookies

Seedable does not currently use cookies for:

Cross-site behavioural advertising;
Third-party advertising networks;
Personalised advertising;
Financial-product targeting;
Assessing investment suitability; or
Providing personalised financial or investment advice.

Seedable may measure the source of visits or the effectiveness of its own promotional activity in the future. Any non-essential advertising, referral or cross-site tracking technology will not be enabled until this policy has been updated and any consent required by applicable law has been obtained.

How We Use Cookies

Seedable uses cookies and similar technologies to:

Operate and maintain the Platform;
Register and authenticate users;
Maintain and secure user sessions;
Support account verification and onboarding;
Remember user-selected preferences;
Provide messaging, notification and profile-history functionality;
Deliver and operate pitch-video features;
Measure authenticated engagement with Discover pitches;
Improve and rank content within Discover;
Monitor security, prevent misuse and diagnose technical problems; and
Comply with applicable legal and security obligations.

Seedable does not use cookies or behavioural data to provide financial advice, determine investment suitability, guarantee investment outcomes or endorse a particular investment.

Third-Party Cookies and Service Providers

Seedable uses Supabase as a service provider for authentication, session management, database services, file storage, application programming interfaces and real-time Platform functionality.

Supabase authentication cookies are normally stored under Seedable’s domain and may therefore be classified by a browser as first-party cookies. However, Supabase is a third-party service provider that processes authentication and Platform information on Seedable’s behalf.

Seedable is responsible for deciding why Supabase is used within the Platform. Supabase processes information in accordance with its contractual obligations, data-processing terms and applicable privacy documentation.

Seedable does not currently permit an independent advertising network to place tracking cookies through the Platform.

The Platform may contain links to external websites, including social-media websites. If a user follows an external link, the destination website may use its own cookies. Those cookies are controlled by the destination website and are governed by its own privacy and cookie policies.

Cross-Border Data Transfers

Supabase and other infrastructure providers may process Platform data in countries outside the country in which a user is located.

Where personal data is transferred internationally, Seedable uses safeguards required by applicable data-protection law. Further information about international transfers, hosting locations and applicable safeguards is provided in the Seedable Privacy Policy.

Cookies may be:

Session cookies, which normally expire when the browser session ends; or
Persistent cookies, which remain for a specified period or until they are removed.

The specific durations of Seedable’s current cookies and browser-storage entries are described above.

Some local-storage entries do not have an automatic browser expiry date. They remain until they are removed by the Platform, cleared by the user, overwritten, or removed through browser or device settings.

Server-side database retention is separate from the period for which information remains on a user’s device. Server-side retention is described in the Privacy Policy.

Managing Cookies

Users can manage cookies through Seedable’s Cookie Settings control and through their browser or device settings.

Browser controls generally allow users to:

View stored cookies;
Block or restrict cookies;
Delete existing cookies;
Clear local and session storage; and
Limit cookies for selected websites.

Blocking strictly necessary cookies may prevent login, verification, secure sessions, onboarding or other essential Platform features from working.

Rejecting or withdrawing consent for analytics will not disable strictly necessary authentication and security cookies. Where analytics consent is refused or withdrawn, Seedable will stop recording new non-essential Discover analytics for that user. Withdrawal does not invalidate processing that took place before consent was withdrawn.

Where consent is required, Seedable requests it before using non-essential analytics, advertising or tracking technologies.

Users are offered clear choices to:

Accept non-essential technologies;
Reject non-essential technologies; or
Manage individual categories of technology.

Consent is not inferred merely because a person continues to browse or use the Platform.

Users may withdraw or change their choice at any time through the Cookie Settings control. It must be as easy to reject or withdraw consent as it is to provide it.

Strictly necessary cookies remain active because they are required to provide authentication, security and other services requested by the user.

Updates to This Policy

Seedable may update this Cookie Policy when:

Its use of cookies or similar technologies changes;
A new service provider or analytics tool is introduced;
Cookie purposes or durations change;
Platform functionality changes; or
Applicable legal requirements change.

The updated policy will be published with a revised “Last updated” date. Where an update requires new consent, Seedable will request that consent before enabling the relevant technology.

Continued use of the Platform will not, by itself, be treated as consent to newly introduced non-essential cookies.

Contact

For questions about this Cookie Policy or Seedable’s use of cookies and similar technologies, please contact:

admin@seedable.co

Final Note

Seedable uses cookies and similar technologies to operate, secure and improve the Platform and to provide user-requested functionality.

Seedable’s Discover system records authenticated pitch-viewing and engagement information, as described above, and may use that information to improve the ordering and relevance of pitches. Seedable does not use cookies or engagement data to provide financial advice, determine investment suitability or guarantee investment outcomes.