Oracle — Cookie & Browser Storage Policy
Effective date: 3 November 2026
1. How Oracle uses cookies
Oracle is a goal-oriented journaling website. We use cookies and browser storage to operate account sessions, protect sign-in and account changes, and preserve certain short-lived workflow details while you use the Service. We aim to avoid collecting more information from your device than is needed to provide Oracle.
This policy explains the browser technologies used by Oracle (trading name of a UK sole trader) at https://oracle-pi-beryl.vercel.app/. For wider personal-data processing, including journals and AI, read our Privacy Policy.
Cookies are small values stored by your browser and sent with relevant web requests. Similar technologies, such as sessionStorage and localStorage, can store information in your browser without sending it automatically with every request. They may also be covered by UK rules on storing information or accessing information on a person's device.
2. Essential Oracle cookies currently identified
The application's inspected identity code sets the following cookies when required for a working sign-in or protected account operation:
| Cookie | Purpose | Classification | Security / expiry |
|---|---|---|---|
oracle_v2_session | Maintains a server-managed Oracle session so the right account and journal are shown. | Essential authentication | Set by Oracle; HttpOnly, SameSite=Strict and Secure in the hosted HTTPS environment. Expiry follows the deployed session setting. |
oracle_v2_intent | Links an account operation (for example registration, sign-in or recovery) to an intent/security proof, helping protect sensitive changes. | Essential account/security | Set by Oracle; same hosted cookie protections and configured expiry. |
These cookies are used to provide a service the user requests and protect account security. Such essential cookies ordinarily do not require consent under the strictly necessary exception to UK PECR, but this disclosure should remain available.
3. Browser storage for app workflows
Oracle's inspected web code also uses storage in the browser for limited interface and request-recovery information. Examples include:
- Temporary account-upgrade and sign-in operation identifiers, so a retry does not accidentally perform a second operation.
- State associated with an unfinished password-recovery or account-deletion process.
- Temporary controls such as the selected start of a review week or whether a subscription offer has already been shown in a browser session.
This is primarily sessionStorage, which normally remains available while the relevant browser tab/session exists. A small amount of localStorage may be used to remember an interrupted deletion-related process across page reloads.
This information should not be treated as a permanent copy of your entire journal history. Journal and account data are stored and managed as explained in the Privacy Policy.
4. Stripe Checkout and third parties
If you choose a free trial or paid Oracle Plus subscription, Oracle redirects you to Stripe Checkout. Stripe may use its own cookies or device storage on its pages to process payments, remember necessary payment-session information and prevent fraud. Stripe operates those payment interfaces and provides its own privacy information at https://stripe.com/privacy.
If Google Sign-In is introduced, Google and Supabase may also use relevant cookies or session storage during the sign-in flow.
We do not assume that cookies set by third parties are controlled by Oracle, and we will update this policy if our integration changes.
5. Analytics, advertising and optional cookies
Our current review of Oracle's web app did not establish that Google Analytics, Meta Pixel, cross-site advertising tags or other optional marketing trackers are currently installed. We therefore do not describe them as active Oracle features or claim to operate a cookie-consent banner that may not exist.
If we introduce optional analytics or advertising cookies, we will update this policy before use. Where UK law requires consent, we will ask before placing them and provide a way to withdraw that consent. Some narrowly defined statistical or appearance-related technologies may qualify for an exception only if the conditions in current ICO guidance are met, including clear information and a simple, free way to object. Those exemptions do not authorise tracking people for advertising.
6. Your choices
You can view, block or remove cookies through your browser settings. Removing essential Oracle cookies can sign you out, interrupt unfinished actions or require you to authenticate again.
Where Oracle later uses optional cookies that require consent, you will be able to manage that choice through the appropriate preference mechanism; no such control is promised here unless actually deployed. Where Oracle relies on a statistical/appearance exception, an appropriate simple opt-out must be available.
7. Updates and questions
We will update this policy as our website, authentication and billing services change. The effective date above applies to this version. Material tracking changes may require a fresh consent or notification, depending on the circumstances.
Contact contact@postonomy.net if you have questions about browser storage or data protection. Operator: Oracle (trading name of a UK sole trader).