Cookie policy

This policy explains storage used by the Citation application operated by RELOAD TECHNOLOGIES - FZCO. It should be read with our Privacy policy, which explains the associated personal information, service providers, and your rights.

A cookie is a small value your browser stores and sends with relevant requests. Local storage keeps information for a site between visits. Session storage normally keeps information for a tab’s session, although browser session restoration may preserve it. These technologies can contain identifiers, preferences, or work in progress, even when they are not used for advertising.

The inventory below describes the current application. Exact cookie prefixes vary by the authentication project, and a large authentication value may be split into several cookies. Optional features set their own values only when the corresponding flow is used.

Supabase authentication cookies

sb-<project-ref>-auth-token, sometimes with numbered suffixes, carries the session information used to recognise your account and refresh sign in. Authentication flows can also use a cookie ending in auth-token-code-verifier to complete secure sign in. These are set on Citation’s site through the Supabase authentication library. The installed library sets a maximum cookie lifetime of 400 days and can rewrite values as the session refreshes. A token can expire, be revoked, or be removed sooner; cookie lifetime is not a guarantee of continued access.

Password recovery

citation_recovery_flow protects the password recovery exchange. It contains encrypted recovery state and is limited to the verification route. Its maximum lifetime is 15 minutes, and a successful verification clears it. It is only needed when you request password recovery.

Integration connection

citation-integration-<provider> binds an external authorisation callback to the browser that started it. It is used only for a configured account connection, has a maximum lifetime of 10 minutes, and is cleared when the callback completes successfully.

Referral sign in flow

citation_referral_flow preserves a signed referral code during an enabled Google sign in flow started with a referral link. Its maximum lifetime is one hour, and the callback clears it. Its presence does not mean Citation has an active paid referral reward.

Sign in and recovery cookies support authentication and account protection. A referral value serves attribution and should not be assumed to have the same legal classification as an authentication cookie. Cookie purposes and any applicable consent requirement must be reviewed for the jurisdictions in which Citation is offered.

The following local storage entries belong to Citation. They are not advertising audience identifiers. Unless removed by the application or browser, local storage has no automatic expiration date.

Navigation and display preferences

citation:location:, citation:library-sort:, and citation:sidebar: entries remember workspace or folder context, list ordering, and expanded sidebar sections. They include an account identifier so preferences can be associated with the appropriate account on the device.

Unsynced document recovery

citation:sync: entries can contain document editing state when changes have not yet been saved to the server. The current key includes account and document identifiers. The application removes a pending value after a successful save when no further changes are waiting. If saving does not finish, the value can remain on your device.

Earlier getting started progress

The application can read an existing citation:getting-started:v1: entry to carry earlier checklist progress into your account. Current progress is stored with the account. A legacy browser entry may remain until browser storage is cleared.

These values are accessible to the application running in your browser. In particular, a recovery entry may contain document content, not just a preference. Signing out should not be treated as a promise that all local entries have been erased. Use a trusted device for sensitive work.

Session storage supports continuity while you move around Citation. It is normally removed when the tab session ends, subject to your browser’s restore behavior. Some entries are removed earlier when the intended action completes.

• citation:pending carries text or a source query entered on the homepage into the workspace after sign in. It can contain the draft text you entered.
• citation:document-tabs:v1: remembers open document tabs for the relevant workspace context.
• citation:review-save: keeps identifiers used to restore the review state of assistant suggestions.
• citation:search-reveal carries a search selection so the editor can reveal the requested passage.
• citation:auth-workspace-entry and citation:onboarding-target carry navigation hints for sign in and getting started actions.

Ordinary browser caching of scripts, fonts, and images is separate from this storage. Citation also uses temporary memory while the app is open. Clearing website storage does not erase data already saved to your Citation account.

The current application does not load an advertising pixel, a marketing analytics SDK, or an optional analytics cookie. Document word counts and reading estimates are writing features, not an advertising tracker. Hosting, security, authentication, and usage logs still exist and are covered by the Privacy policy.

Citation currently has no cookie preference centre, consent banner, or optional cookie toggle. We do not interpret continued browsing as consent to optional tracking. Before introducing any storage that requires consent, an appropriate choice must be available before that storage is used. Persistent preferences and referral attribution also require an assessment of any applicable consent or exemption rules before publication.

If you leave Citation to sign in with a provider, connect a service, or follow an external link, that provider may use its own cookies on its own site. Its notice and controls govern that activity. This inventory does not claim to describe every cookie on an external provider’s website.

Your browser’s privacy or site settings let you inspect, block, or remove cookies and stored website data for Citation. You can also use a separate browser profile on a shared device. Clearing authentication cookies can sign you out. Blocking necessary storage can prevent sign in, recovery, connected account setup, or preference persistence from working.

Before clearing local or session storage, confirm that your document changes have saved and export anything important. Removing recovery data can permanently discard changes that never reached the server. Clearing device storage does not delete server records, cancel a provider’s authorisation, or recall shared copies.

For account data requests or questions about an unfamiliar value, contact hello@alptekincan.com. Share the cookie or storage name and the page where it appeared, but do not send its value if it could contain a session token, private text, or other sensitive information.

We will revise this inventory when the application’s storage changes. The date at the top identifies the latest review draft. A change to this notice does not by itself supply consent for a new purpose. The operator must confirm the deployed storage inventory and any required controls before publication.