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.
Privacy Policy
This draft explains how the Workcea application handles personal information in the version running today. It is written for review by a qualified privacy lawyer. It is not a statement that Workcea complies with any particular law.
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
Workcea is a freelance marketplace that lets a client publish a project, lets a freelancer publish a profile or a service, and lets the two people form a contract record. [LEGAL ENTITY NAME] is not yet confirmed. [REGISTERED BUSINESS ADDRESS], [COUNTRY/JURISDICTION], and [PRIVACY CONTACT EMAIL] are not yet confirmed. [POLICY EFFECTIVE DATE] is not set. The preparation note at the top of this page is not that date.
This notice covers the account, marketplace, support, and assistant features in this application. It does not describe a company that has been formed, a production domain that has been chosen, or a hosting contract that has been signed. A permanent public launch is not enabled.
Information Workcea collects
Workcea stores information you submit, information created by using the marketplace, and a small amount of technical information needed to keep you signed in and to remember a language or currency choice.
The application uses a SQLite database file on the machine that runs it. There is no separate customer-data warehouse in this repository.
Information provided by users
Registration asks for a name, an email address, and a password. The password is stored as a hash. Signup can also copy a guest language or currency choice onto the new user.
A profile can include a title, biography, skills, languages, location, availability, an hourly rate, and portfolio entries. A project can include a description, budget, deliverables, and files. A proposal includes a price, a delivery time, and a message. A service includes package prices, delivery times, and add-ons. A contract stores the agreed scope, messages, deliveries, revision notes, and reviews. A support ticket stores the name, email, category, and message you submit, plus an optional file.
Email verification and password reset can create a token. When email delivery is not configured, Workcea does not send that message. A short-lived httpOnly cookie can hold the verification token for the browser that signed up, for 15 minutes.
Information collected automatically
Signing in sets an httpOnly session cookie named taskflow_session. It expires after 14 days. The cookie is marked Secure when the app URL uses https, when the server is in production, or when public launch is turned on. Page scripts cannot read it.
Workcea does not run an analytics product, an advertising pixel, or a social sign-on flow in this codebase. It does not read a Global Privacy Control signal, because no advertising or sale integration was found to honor.
If a display-currency rate is configured, the server requests a USD rate table from that URL. The current preview uses open.er-api.com. That request does not include your name, email, or account id. The rate, the source host, and the retrieval time are kept in server memory for the cache period described in the Cookie Policy.
Public profiles and user-generated content
An open job, a public freelancer profile, and a published service can be read by visitors. The public profile shows the fields the freelancer published. An hourly rate appears only when the freelancer chose to show it. Demo profiles and demo services stay labeled.
A portfolio item appears on the public profile when it is published. Unpublished profile fields and draft services are not placed on the public page.
Reviews appear from completed contracts on this site. Workcea does not add ratings, testimonials, or verified-seller badges that are not stored records.
Jobs, proposals, services, orders, contracts, and messages
A proposal is visible to the client who owns the job and to the freelancer who sent it. Contract messages and files are visible to the client and the freelancer on that contract. Service-order messages follow the same pattern for the buyer and the seller.
Administrators can open users, jobs, services, reviews, reports, disputes, support tickets, finance records, and the audit log. That access is for operating the marketplace, answering a support request, reviewing a report, and recording a dispute outcome. It is not a promise that every record will be reviewed.
Support tickets are visible to the person who submitted them when that person is signed in, and to administrators. A guest who submits a ticket is told to sign in to read replies. The contact form does not send email.
How personal information is used
Workcea uses account data to sign you in, to show the dashboard that matches your role, and to keep a language or currency preference. It uses project, proposal, service, and contract data to operate those workflows. It uses support and report data to let an administrator read the request.
Fee summaries are calculated from the stored USD amount and the active schedule. A display currency changes the figure on screen. It does not change the stored cents, the client fee, or the freelancer commission.
Workcea does not use this information to sell advertising in the current application. No marketing email program is implemented.
Legal bases for processing, where applicable
Some privacy laws require a stated legal basis, such as a contract, a legal obligation, consent, or a legitimate interest. [COUNTRY/JURISDICTION] is not confirmed, so this draft does not select a basis for each activity.
Before a public launch, counsel should map each activity above to the basis that applies, including account creation, public profiles, messages, support, admin access, and any future email or payment provider.
Veyro and third-party AI processing
Veyro is the in-product assistant. It can suggest prompts and can prepare a support draft. It cannot hire a person, send a contract message, change an account, or move money. Its replies can be wrong.
The live model is not in use while the server API key is empty. In that state Workcea does not call an external model. A turn that only receives the unavailable reply is not stored. A POST to the assistant can still set an httpOnly cookie named veyro_session, for 30 days, so the browser can be tied to a later conversation.
When a key is configured, the code is written to send the conversation instructions, recent messages, and the new message to OpenAI, then store the user message and the reply. That path has not been verified with a live key. Do not treat live AI processing as happening today.
Before that key is turned on, the operator needs a checklist: the provider name, what text is sent, how long the provider keeps it, whether account identifiers are included, how a person can avoid the assistant, and a lawyer’s review of this section. The key must stay on the server.
Hosting, service providers, and international transfers
The database file lives on the computer that runs the application. A permanent host, region, and processor list are not chosen. [COUNTRY/JURISDICTION] is blank.
If the rate URL is set, that host receives the request for the rate table and not an account identifier. If email or a live model is later enabled, those providers would receive the content described in this notice. Counsel should decide whether those transfers need a stated safeguard before launch.
Data retention
This application does not run an automatic deletion job. Account, project, message, file, support, dispute, ledger, and audit records remain until an operator changes the database. No retention period has been chosen, so this draft does not invent one.
Some durations are implemented: the session cookie lasts 14 days, preference cookies last 365 days, the verification hint lasts 15 minutes, the Veyro cookie lasts 30 days, a verification link is described as 48 hours, and a password-reset link is described as two hours. Rate snapshots in memory are fresh for 6 hours and are not used after 24 hours.
Contract, dispute, support, and audit records may need to be kept after an account request so the marketplace can explain what happened. That decision is not automated today.
Account access, correction, export, and deletion requests
You can edit the profile and account fields the settings screens expose. You cannot download a full copy of the account from a self-service page. You cannot delete the account from a self-service page. Those tools are not built.
Send a request through Contact or the privacy-request form. Include the email on the account. The form requires a name and an email because a support ticket requires them. Workcea will match a signed-in request to that account. A guest request can be saved, and replies are visible after sign-in. No email notice is sent by the form.
A request is not completed when the ticket is saved. An administrator has to read it. Deletion, if it is later built, must not be described as immediate, and it must leave the records that disputes, security, and legal duties still require. The data-rights page repeats this limit.
Security measures and their limitations
Passwords are hashed. The session cookie is httpOnly. Security headers on responses include frame denial, a nosniff content type, a strict referrer policy, and a permissions policy that turns off camera, microphone, and geolocation. Administrator access requires a configured email and a verified account. Demo accounts cannot be administrators.
These controls are not a certified security program and they are not a payment-security certification. A person with access to the server can read the database file. A bug or a stolen password can expose data. Workcea does not promise that information cannot be lost or misused.
Children's privacy and minimum age
Signup does not ask for a date of birth and does not block an account by age. The product is not built for children, and it does not knowingly collect a child’s information as a separate category.
Counsel must choose a minimum age and say how it will be enforced before public launch. Until that exists, do not treat a number on this page as a rule the software applies.
Applicable privacy rights and jurisdiction-specific requirements
Privacy rights depend on where you live and on the law that applies to [LEGAL ENTITY NAME]. That place is not chosen. This draft therefore does not promise a response deadline, an appeal body, or a regulator.
People in some regions can ask for access, correction, deletion, a copy, or a limit on certain uses, and can object to some processing. People in some US states can opt out of a “sale” or “sharing” as those laws define the words. Whether those rights apply here is a legal question, not a fact this software can decide. Use the request pages. A lawyer must review the result before launch.
Changes to this policy
A later draft can replace this text. The page will keep a preparation date. That date is not an approval. A material change that the law requires to be announced needs a process the operator has not built, such as a notice on the account. Do not assume a silent edit is a notice.
Contact information and privacy requests
Privacy requests go through Contact or Do Not Sell or Share My Personal Information. There is no privacy inbox yet. [PRIVACY CONTACT EMAIL] is a placeholder. There is no data-protection officer and no named supervisory authority.
Until [LEGAL ENTITY NAME], [REGISTERED BUSINESS ADDRESS], [COUNTRY/JURISDICTION], [PRIVACY CONTACT EMAIL], and [POLICY EFFECTIVE DATE] are filled in, and a lawyer has reviewed this draft, this page stays a draft.