Cookies and Device Storage
An inventory of session cookies, language preferences and drafts kept in your browser.
Draft updated: Draft version 0.1
Cookies and similar technologies
Cookies are small records a browser stores and may attach to requests to the relevant site. Local storage and session storage are records the application keeps on your device. howk uses these technologies for sessions, security, language, appearance and selected editing conveniences.
The inventory below describes the current application and its default settings. Records added by the live server, domain, CDN or external services need a separate pre-publication audit. Not every record is created on every page or on a first visit.
Current storage inventory
Durations describe current application behaviour. A cookie’s expiry may be renewed when it is set again, and browser settings or session restoration may affect storage. Local storage has no automatic expiry unless stated below.
sessionid
- Type
- First-party cookie
- Purpose
- Recognise the signed-in account session.
- Retention
- Current default: 14 days. Signing out ends the session.
csrftoken
- Type
- First-party cookie
- Purpose
- Protect form and API actions against cross-site request forgery.
- Retention
- Current default: 364 days; expiry may be renewed when set again.
NEXT_LOCALE
- Type
- Language-preference cookie
- Purpose
- Remember the selected interface language; may be created when language routing needs it.
- Retention
- No persistent expiry is configured; lasts for the browser session.
howk.theme
- Type
- Local storage
- Purpose
- Remember a light or dark appearance choice.
- Retention
- Until changed or site data is cleared; no automatic expiry.
howk.pref.*
- Type
- Local storage
- Purpose
- Remember device preferences such as the sidebar, document rail, preview display and invitation indicator.
- Retention
- Until changed or site data is cleared; retained after sign-out.
howk.draft.*
- Type
- Local storage
- Purpose
- Restore unsaved input in supported profile and publishing forms. May contain personal content.
- Retention
- Removed when the relevant draft is saved or discarded, on application sign-out or when site data is cleared; otherwise no automatic expiry.
persona.templates.dismissed
- Type
- Local storage
- Purpose
- Remember dismissed or used Persona starting suggestions; does not store Persona note text.
- Retention
- Until site data is cleared; retained after sign-out.
howk.ai-export-acknowledged
- Type
- Local storage
- Purpose
- Remember acknowledgment of the sensitive-data warning for AI export in this browser. This is not general data-processing consent.
- Retention
- Until site data is cleared; retained after sign-out.
howk.verify-banner-dismissed
- Type
- Session storage
- Purpose
- Remember dismissal of the email-verification reminder.
- Retention
- For the tab’s browser session; browser session restoration may affect this.
Your choices and clearing data
You can clear cookies and site data or block storage through your browser settings. Blocking session or security cookies may prevent login or form submission. Clearing site data also removes local drafts and remembered preferences.
Signing out through the application clears local form drafts. Theme and layout preferences, dismissed Persona suggestions and the AI-export warning acknowledgment may remain after sign-out. Clear site data separately on shared devices. Deleting server-side account data does not automatically clear every record in your browser.
Measurement and error monitoring
Current product statistics are calculated from account and content records on the server. The application code does not integrate an advertising pixel or a separate marketing-analytics tool. Sentry error and performance monitoring is supported; its activation, data flows and possible device access require verification in the live environment.
Storage strictly necessary for communication or a requested service must be assessed separately from preferences or measurement. Not using cookies does not by itself remove consent or other data-protection duties. The required permissions must be determined and implemented rather than treating all storage as essential.
Details to complete before publication
- Verify cookie domains, durations, providers and security attributes in the live environment.
- Review necessity and legal grounds for language, appearance, draft and acknowledgment records.
- Implement prior choice, withdrawal and preference controls for processing that requires consent.
- Add data flows for Sentry, the CDN and any future analytics or payment tools to the inventory.