1. What we use

Cookies store small values your browser returns on later requests. Local/session storage keeps information in the browser without automatically sending it on every request. OceanSheet currently uses necessary authentication/security cookies and browser storage for workflow drafts you create.

Our application templates do not load Google Analytics, advertising pixels, or remarketing tags. Continued browsing, connecting Google, or agreeing to the terms is not consent to optional tracking.

2. Necessary cookies

Cookie/categoryPurposeDuration
Session cookie, normally oceansheet-sessionServer-side session, sign-in, and secure authentication/authorisation flows.The configured session lifetime is 120 minutes of inactivity; browser/session settings may affect expiry. Signing out invalidates the current session.
XSRF-TOKENHelps prevent cross-site request forgery against account/application actions.Normally follows the session lifetime; refreshed during session/CSRF operations.
Persistent sign-in cookie, when “Remember me” is selectedMaintains sign-in between browser sessions.Until cookie expiry or clearing; signing out invalidates remember-me credentials. Browsers may shorten its lifetime.

Names can vary by configuration. These cookies provide the service you request rather than advertising. Blocking them can prevent sign-in, account actions, or an authorisation return from working.

3. Workflow drafts on your device

  • oceansheet.workflow-draft.session.v1 in session storage keeps unfinished workflow settings in the current tab, including during Google connection. It normally lasts until the tab session ends; browser session restore may retain it longer.
  • oceansheet.workflow-draft.v1 in local storage is written when you select Save draft. It remains until replaced, cleared after creating the workflow, or removed through browser settings.

Drafts include names, file/tab identifiers, columns, mappings, and filter values. These can contain personal information you enter. A draft is not a backup of spreadsheet rows or a saved server-side workflow. Clear site data on shared devices that should not retain confidential settings.

Deleting a server-side account does not clear browser storage on every device. Use browser site-data controls to remove those copies.

4. Google, Stripe, and privacy controls

When you choose Google sign-in, connect Drive, or open Picker, Google serves its own interfaces and may use its own cookies/storage, governed by Google's Privacy Policy and cookie information. OceanSheet cannot read Google's sign-in cookies.

When you choose to contribute, Stripe Checkout may use payment, security, and fraud-prevention technologies; see Stripe's Privacy Policy. Opening an external service is a separate action from browsing this website.

Brave Shields, ad blockers, and third-party cookie restrictions can affect Picker after Drive is authorised. Use Close picker and Having trouble? for recovery. You control your browser settings; a recovery tip does not request disabling protections across all websites.

5. Your choices and changes

Browsers can display, block, and delete cookies/site storage. Deleting them may sign you out or remove unfinished drafts. Those controls are separate from account deletion or revoking Google access.

New optional tracking will require appropriate notices and choices before it runs. Where consent is required, refusal must leave optional tracking disabled and withdrawal must be as easy as acceptance. We do not display an optional-tracking consent banner for trackers that are not loaded.

Report unexpected storage or ask questions at legal@oceansheet.com. Personal-data rights are explained in the Privacy Policy.