Cookies and browser storage.

Sign-in and service access

Authentication uses functional session cookies. Cookie names and expiry follow the active authentication configuration. Third-party sign-in and payment providers may set their own cookies when you visit their pages.

Usage limits can use server-side counters and network identifiers. These records are separate from manuscript drafts.

Workspace recovery and preferences

• Browser IndexedDB stores local workspace files and recovery data. preflight_workspace_files identifies workspace files in the local file service.
• preflight-appearance-v1 stores workbench palette and accent preferences. Legacy theme keys may remain after migration.
• preflight_cookie_consent and legacy recite_cookie_consent identify current and legacy acknowledgment of the storage notice. Dismissal acknowledges this notice; it does not grant permission for optional tracking. The acknowledgment has no automatic expiry.
• Local files and preferences persist until the application or browser removes them. Exported filesystem files must be removed separately.

Advertising and external services

PreFlight does not use advertising cookies to monetize manuscript activity. Essential storage supports workspace and account functions.

Source lookups, authentication, and payments use external services. Local parsing does not make the connected application air-gapped; consult provider policies for their processing.

Clearing stored data

Use Account Settings for local-data controls and confirmed account deletion. Browser site-data settings can remove cookies, IndexedDB, and preferences; this can sign you out and remove recoverable local drafts.

Local clearing does not erase cloud records. Cloud purge has a separate authenticated endpoint and defined scope, described in the privacy policy.