Demo mode. Payments and email are not connected. Records marked Demo are not charges, payouts, or verified accounts.

Draft version 28 October 2026. This text needs a lawyer before a public commercial launch. It does not name a registered company, address, certification, or regulatory approval. The paragraphs below stay in English until that review.

Cookie Policy

This draft lists the cookies this application sets. It does not describe analytics, advertising, or other cookies that are not in the code.

Draft prepared 31 October 2026. This date is not a legal approval date.

Text in square brackets is a missing business fact. Do not treat this page as final.

Introduction and scope

A cookie is a small value the server asks the browser to store and send back. Workcea uses cookies to keep a sign-in, to remember a language or currency you applied, to finish email verification on the same browser, and to attach a Veyro conversation to that browser. [LEGAL ENTITY NAME] and [PRIVACY CONTACT EMAIL] are not set. [POLICY EFFECTIVE DATE] is not set.

What cookies and similar technologies are

This policy uses “cookie” only for values stored as cookies. Workcea does not use localStorage or sessionStorage for preferences. Language and currency are also copied onto the user row when you are signed in. That row is server data, not a cookie. The session itself is an httpOnly cookie, not a value that page scripts can read.

Strictly necessary cookies

taskflow_session identifies the signed-in account. It is httpOnly, SameSite=Lax, path=/, and lasts 14 days. It is marked Secure when the site URL is https, the server is in production, or public launch is on. Signing out clears it. Changing the password makes older copies fail.

These cookies are not optional inside the product. Turning off the session cookie signs you out. The application does not offer a switch that disables them while keeping you signed in.

Authentication and security technologies

taskflow_verify_hint stores a verification token for 15 minutes so the browser that signed up can verify when email is not sent. It is httpOnly and uses the same SameSite and Secure rules as the session cookie. It is deleted when verification finishes. There is no separate CSRF cookie. Server actions rely on the framework’s same-origin checks. There is no third-party fraud script.

Preference storage

taskflow_locale and taskflow_currency are set when you use Apply Language or Apply Currency. They are httpOnly, last 365 days, and use the same SameSite and Secure rules. They are not advertising cookies. A signed-in choice is also stored on the user and restored at the next sign-in. Guests keep the cookie. Whether a preference cookie needs a consent banner in [COUNTRY/JURISDICTION] is a question for counsel. This version does not add a banner, because it does not load an optional tracker.

Analytics technologies

No analytics provider, page-view counter, or product-analytics script is configured. If one is added later, this draft has to name it before launch. Do not treat the absence of a banner as a decision that every future tool is allowed.

Advertising and marketing technologies

No advertising cookie, marketing pixel, or retargeting tool is implemented. Workcea does not write a sale or share of personal information for cross-context advertising in this code. The request page exists so a person can still ask. Saving the request does not switch off a tracker that is not there.

Third-party cookies and integrations

The cookies above are first-party cookies set by this application. veyro_session is an httpOnly cookie lasting 30 days. A request to the assistant can set it even when no model is called. OpenAI, Resend, and a payment provider are not setting cookies in the current configuration. A display-rate request, when configured, is a server fetch and does not set a browser cookie. The preview rate host is open.er-api.com. An embedded video or social plugin is not part of the layout.

How long cookies remain stored

The durations above are the maxAge values in the code: 14 days for the session, 365 days for language and currency, 15 minutes for the verification hint, and 30 days for the Veyro cookie. A browser can delete them sooner. Workcea does not keep a separate cookie ledger.

Cookie controls and user preferences

Change language or currency from the footer and use the Apply button. Sign out to clear the session. There is no preference center for optional cookies, because no optional analytics or advertising cookie exists. A lawyer should decide whether the preference cookies need an accept or reject control before launch in a particular country. This draft does not claim that the current design satisfies that rule.

Browser-level cookie management

You can block or delete cookies in the browser. Blocking all cookies will stop sign-in and will stop the language and currency choice from sticking. Blocking only third-party cookies does not remove the first-party cookies listed here.

International privacy considerations

Cookie rules differ by country. [COUNTRY/JURISDICTION] is blank. Counsel should decide whether a banner, a reject control, or a record of consent is required for these cookies before a public launch. This page is not that decision.

Policy changes

If Workcea later sets another cookie, this page has to name it. The preparation date is not an approval date. A new analytics or advertising cookie should not ship on a silent edit.

Contact information

Questions go through Contact. [PRIVACY CONTACT EMAIL] is not set. An internal inventory of these cookies is kept for the operator in the project documentation and is not a public promise of compliance.