Privacy notice

Who controls what

There are two different relationships here, and they carry different obligations. Keeping them apart is the point of this section.

• Your account data — we are the controller. When you sign up, we decide what to collect and why: an email address, a name, a password hash, and what you told us you were routing. This notice governs that.
• The data you route — we are a processor. Tasks, workers, tags, task content and decision traces belong to you. We process them on your instructions, to run the routing you asked for, and for nothing else. We do not mine them, sell them, or use them to train models.

If the data you route includes personal data about your own staff or customers, you are the controller for it and we act under your instructions. Our standard data processing agreement covers that relationship and is already in force — nothing to request, though we will countersign a copy if your process needs one.

What we collect

Because you gave it to us: your name and email address, your password (stored only as a scrypt hash), your answer to the one signup question about what you are routing, and your workspace configuration.

Because the service runs: session records tied to your login, API-key hashes, usage counters for the assignments your workspace matched, and server logs containing IP addresses and request metadata for security and debugging.

Because you sent it through the API: whatever you put in tasks, workers, comments and attachments. Routing needs only tags and identifiers — anything richer is your choice, and if it contains personal data, that is a choice you make as controller.

We do not collect analytics about how you browse this site. There is no tracking pixel, no session recorder, and no advertising identifier anywhere in the product.

Why, and on what basis

• To provide the service — creating your account, authenticating you, running the routing engine, sending transactional email such as verification and worker invitations. Basis: performance of a contract.
• To keep it secure and working — logging, rate limiting, abuse prevention, incident investigation. Basis: our legitimate interest in operating a safe service.
• To bill and account — usage metering, and financial records once paid plans exist. Basis: contract and legal obligation.
• To reply when you contact us. Basis: legitimate interest.

We do not run marketing profiling and we do not send marketing email to addresses collected at signup unless you asked us to.

Who else sees it

Only the subprocessors listed below, each for one job. We do not sell personal data, and we do not share it with advertisers or data brokers — a category that includes analytics vendors, which is why there are none.

We may also disclose data where the law requires it. If we receive such a request and are legally permitted to tell you, we will.

International transfers

The platform runs in Frankfurt, Germany, inside the European Union. Your routing data stays there.

Two flows reach the United States: transactional email through SendGrid, and — only if your workspace uses the Worker-Portal Studio — the AI portal builder through OpenAI. Where personal data is part of those flows, it is transferred under the safeguards required by GDPR Chapter V.

The safeguard in both cases is the European Commission's Standard Contractual Clauses, incorporated in each provider's own data processing addendum, which we have accepted. The per-subprocessor detail is in Annex III of our DPA.

Both are avoidable if you need zero non-EEA processing: the Studio is opt-in, and worker invitations can be issued as links you deliver yourself rather than by email.

How long we keep it

• Account data — while your account exists, and up to 30 days after a deletion request while we complete it.
• Routing data — until you delete it or delete the workspace. Deleting a workspace removes its tasks, archives, comments, attachment records and live routing state, and queues the attachment bytes in object storage for deletion.
• Server logs — kept only as long as they are useful for security and debugging.
• Financial records — retained for the period tax law requires, once paid plans exist.

No automatic expiry. We do not currently age routing data out on a schedule. If your retention policy needs that, it is a manual deletion on your side today.

Your rights

If you are in the EU or UK you have the right to access your personal data, correct it, delete it, restrict or object to processing, and receive it in a portable form. You can also complain to your national data protection authority.

Much of this is self-serve: your account details are editable in the console, workspace data is exportable through the API at any time, and deleting a workspace deletes its contents. For anything else, email support@fivexer.com — we respond within one month, as GDPR requires.

If you are an end user whose data was routed through Fivexer by a customer of ours, that customer is the controller. Send your request to them; if you reach us instead, we will forward it.

Cookies & tracking

We set one kind of cookie: the session cookie that keeps you logged in. It is strictly necessary for the console to work, which is why there is no cookie banner asking for consent we do not need.

Local storage is used for interface preferences — your theme choice, the workspace you last had open, whether a panel was collapsed. That data stays in your browser.

Contact