Privacy Notice
Last updated 15 November 2026
This notice explains what personal data PolyWorker.com collects, why, who we share it with, and the rights you have. We've tried to keep it plain. We don't sell your data, we don't run advertising or analytics trackers, and we don't read your jobs, tasks or notes as part of running the Service.
1. Who is responsible for your data
cr0bar Limited is the data controller for the personal data described here. We're a company registered in England and Wales (company number 07332447), with our registered office at Suite 5 Admirals Yard, Low Road, Hunslet, Leeds, England, LS10 1AE. We are registered with the Information Commissioner's Office (ICO) under reference ZA902799.
For any question about this notice or your data, use our contact form.
2. What we collect
| What | Details | Where it comes from |
|---|---|---|
| Account details | Your name, email address, a salted hash of your password (we never store the password itself), timezone, weekly capacity setting, default assistant model, and when you created, confirmed and last signed in to your account. We also record that you accepted our Terms and which version. | You, and our systems |
| Your work content | What you put in for each job: an alias, employer and role, employment type, status, pay rate and schedule, expected hours, timezone, core hours, stand-up time, manager's name, communication tools, device or profile, start and end dates, AI access setting and "where I left off" notes. Also your tasks, time entries, meetings, notes (including contacts you add) and tags. | You (and the assistant, if you ask it to add things) |
| Connected calendars | Only if you connect one: the calendar link (stored encrypted, because anyone holding it can read that calendar), the name you gave it, and for each upcoming meeting its title, start and end time and location, plus the meeting's ID so we can keep it up to date. We don't import descriptions, attendees, attachments or meetings that have already started. | You, via your calendar provider (for example Microsoft or Google) |
| Payments | Only if you buy a plan: which plan, the amount and currency, any discount, the date, Stripe's reference numbers for the payment, the time you agreed to the payment terms, and the date your paid access runs to. We do not see or store your card details: you enter them on Stripe's own page. Stripe collects what it needs to take the payment (such as your card, name, billing address and email) and handles it under its own privacy policy. | You, and Stripe |
| Assistant conversations | Your messages to the assistant, its replies, and a record of the actions it took. | You and the assistant |
| Activity log | A record of changes made in your account, including those made by the assistant. | Our systems |
| Sign-in security | Only if you turn them on: your authenticator-app secret (stored encrypted), one-time recovery codes (stored only as hashes), a temporary support code if you make one (stored encrypted, valid for 24 hours, and deleted once checked), and for each passkey its public key, the name you gave it, its type, and when it was added and last used. Your fingerprint, face or device PIN never reach us: they stay on your device. | You |
| Security checks | When you create an account, ask for a password reset or use the contact form we create a short-lived check (a random code and its answer) to tell people from bots. It is deleted when used or when it expires. It runs on our own servers: we don't use Google reCAPTCHA or any similar third-party service. | Our systems |
| Technical data | Your IP address, browser and device type (user agent), the pages and requests made, timestamps and error details. These appear in server logs and are also used for rate limiting and security. | Your browser |
| Cookies | Strictly necessary cookies that keep you signed in and protect forms. See our Cookie Policy. | Your browser |
| Messages with us | If you use the contact form, we receive your name, email address, the topic and your message by email, and if you were signed in, the email address and ID of your account so we can verify you. We keep the message and our reply. | You |
We don't take payments, so we don't collect card details. We don't use analytics, advertising or tracking tools, and the Service loads no third-party scripts or fonts.
Other people's information
Your content may mention other people, such as a manager, colleagues or contacts. Meeting titles that come from a connected calendar can name people too. We only process this to provide your workspace and have no relationship with those people beyond that. Please keep it to what you need, and don't add sensitive details about other people (such as health information).
Sensitive information
We don't ask for "special category" data (such as health, trade union membership, religion or ethnicity) and the Service doesn't need it. Because notes and messages are free text, please don't put that kind of information in them.
3. Why we use it, and our legal basis
| Purpose | Legal basis (UK GDPR) |
|---|---|
| Keep your schedule in step with a calendar you connect, by fetching it from your calendar provider every 30 minutes | Contract: you asked for this feature. You can pause or remove a calendar at any time |
| Take payment for a plan, give you the access you paid for, and keep records of payments | Contract, and legal obligation (we must keep accounting records) |
| Create and run your account, and provide the features you use (jobs, tasks, schedule, time tracking, notes, activity log) | Contract: it's needed to provide the Service you've signed up for |
| Send service emails: address confirmation and password resets | Contract |
| Run the AI assistant when you use it, including sending relevant data to the model provider you select | Contract: you ask for this feature. You can choose not to use it, and you can block it per job |
| Two-step sign-in and passkeys, if you choose to use them | Contract and legitimate interests: keeping your account secure |
| Block spam and automated abuse: the security check on sign-up, password reset and the contact form, and a hidden form field that only bots fill in | Legitimate interests: protecting the Service and its users from abuse |
| Keep the Service secure and stable: server logs, rate limiting, abuse and fraud prevention, fixing faults, backups | Legitimate interests: keeping the Service and your data safe and reliable |
| Confirm that someone asking for help is the account holder, using a support code you make and read out | Legitimate interests: stopping others getting help with, or information about, your account |
| Respond to your requests, queries and complaints | Contract or legitimate interests, depending on the request |
| Meet legal obligations, respond to lawful requests from authorities, and establish, exercise or defend legal claims | Legal obligation, or legitimate interests |
We don't send marketing emails. If that changes, we'll only do so with your consent, which you can withdraw at any time.
We don't make decisions about you based solely on automated processing that have legal or similarly significant effects. The assistant gives suggestions and carries out tasks you ask for; it doesn't make decisions about you.
4. Who can see your data
Each account's data is kept separate, and the Service only shows you your own. We can't read your authenticator-app secret without the server's encryption key, and we never hold the private part of a passkey. Administrator screens show account details only (such as name, email, sign-up date and status) and not your jobs, tasks, time entries or notes. We don't read your content in normal operation. Access to the database and servers is limited to people who need it to run the Service, and we'd only look at your content if you ask us to help, or where needed to investigate abuse, a security incident or a legal request.
5. The AI assistant (Polly) and AI providers
The assistant is optional. When you send it a message, the Service builds a request containing:
- your name, timezone and weekly capacity setting, and the current date and time;
- for each job in scope: its alias, role, employer, status, expected hours, timezone and core hours, and, as the assistant asks for them, the job's tasks, notes, meetings (including any imported from a connected calendar), time totals, manager, tools, device, pay schedule, start date and "where I left off" notes. Your pay rate is not sent. In an all-jobs conversation, your personal notes can be included too;
- your message and up to the last 24 messages of that conversation, plus a short record of the assistant's earlier actions; and
- the results of any tools the assistant calls.
Scope and AI access. A conversation limited to one job can only use that job's data, and this is enforced by the Service itself. Each job also has an AI access setting. Jobs set to No AI access are never included, and jobs set to Local models only are only included when a local model is used.
Who receives it. Depending on the model you choose, the request goes to:
- Anthropic (Claude models) or OpenAI (GPT models), who are US-based cloud AI providers, acting as our processors; or
- local models (run through Ollama) on infrastructure we control, in which case the data isn't sent to a third-party AI provider. Local models are labelled "(local)" in the model list.
Which providers and models are switched on can change over time. Under their commercial API terms, these providers say they don't use API inputs and outputs to train their models by default, but they may keep data for a limited period for safety and abuse monitoring. Their own policies apply to that handling: Anthropic and OpenAI.
Assistant replies can be inaccurate. See our Terms.
6. Who we share data with
We share personal data only with organisations that help us run the Service, and only as far as needed:
- Hosting and infrastructure providers that run our servers and store backups;
- Email delivery providers that send confirmation and password-reset emails for us (they see your email address and the content of those emails);
- Your calendar provider (for example Microsoft or Google), only if you connect a calendar: our servers request your calendar link from them, so they see our server's address and the request;
- Stripe, our payment provider, only if you buy a plan: it receives your email address, the plan and the amount, and takes your payment details directly from you;
- AI providers (Anthropic and OpenAI), only when you use a cloud model, as described above;
- Professional advisers (such as lawyers, accountants and insurers) where needed;
- Regulators, courts, law enforcement or other authorities, where the law requires or permits; and
- a buyer or successor, if we sell or restructure the business, on terms that protect your data.
These providers act on our instructions under contracts that require them to protect your data. We don't sell your personal data or share it for advertising.
7. Sending data outside the UK
Our AI providers are based in the United States, so using a cloud model involves sending data there. Stripe may also process payment data in the United States and elsewhere. Some of our other providers may also process data outside the UK. When data leaves the UK we make sure it has appropriate protection, for example by relying on the UK-US data bridge where the provider is certified under it, or on the ICO-approved International Data Transfer Agreement or the UK Addendum to the EU standard contractual clauses. Use our contact form if you'd like more information about the safeguards.
8. How long we keep data
| Data | How long |
|---|---|
| Account details and your content | While your account is open. When you ask us to close it, we delete it from the live service within 30 days. |
| Calendar link and imported meetings | Until you remove the calendar. Removing it deletes its upcoming meetings and the saved link. Meetings that had already started are kept as ordinary entries in your schedule until you delete them or close your account. |
| Payment records | Six years, because UK law requires us to keep accounting records. If you close your account we keep these records but use them for nothing else. |
| Support code | 24 hours at most. It is deleted as soon as support has checked it, or if you cancel it or make a new one. |
| Authenticator-app secret, recovery codes and passkeys | Until you remove them, turn two-step sign-in off, or close your account. |
| Security checks (captcha) | Deleted when used. Unused ones expire after about ten minutes and are cleared out shortly afterwards. |
| Backups | We keep a rolling set of recent backups (around the last 14 daily copies plus short-lived copies taken before upgrades). Deleted data drops out of backups as they are replaced, so it can remain in a backup for a few weeks after deletion. We don't use backups for anything except recovery. |
| Server logs and security records | A limited period, long enough for security and fault-finding. |
| Accounts whose email address was never confirmed | We may delete these. |
| Messages you send us | As long as needed to deal with your request, and then for a reasonable period afterwards in case of follow-up or a dispute. |
| Records we must keep or need for legal claims | As long as the law requires or as needed to protect our legal position. |
9. Keeping your data safe
We use measures suited to the sensitivity of the data, including encrypted connections (HTTPS), salted password hashing, optional two-step sign-in with an authenticator app or passkeys, encryption of authenticator secrets and calendar links, protection against cross-site request forgery, security headers, rate limiting on sign-in and sign-up, strict separation between accounts and between jobs in assistant conversations, and limited access to our systems. No system is completely secure. Choose a strong, unique password. If a personal data breach is likely to put you at risk, we'll tell you and the ICO as the law requires.
10. Your rights
Under UK data protection law you have the right to:
- be informed about how we use your data (this notice);
- access a copy of the personal data we hold about you;
- have it corrected if it's wrong or incomplete (you can edit most of it yourself in the Service);
- have it erased in certain circumstances;
- restrict or object to some uses, including where we rely on legitimate interests;
- data portability: receive the data you gave us in a common, machine-readable format. You can already export your time entries as CSV from the Time page; and
- withdraw consent where we rely on it (we currently don't need it).
To use any of these, send us a message through our contact form and choose Privacy or data request. Send it while signed in, or write from the email address registered to your account, so we can be sure it's you. We'll respond within one month. It's free, unless a request is clearly unfounded or excessive. We may ask you to confirm your identity.
You can also change or delete most of your content directly in the Service at any time.
Complaints
We'd like the chance to fix any concern first, so please contact us. You also have the right to complain to the Information Commissioner's Office (ico.org.uk/make-a-complaint, telephone 0303 123 1113).
11. Children
The Service is for adults who are at least 18. We don't knowingly collect data from anyone under 18. If you think a child has signed up, contact us and we'll delete the account.
12. Changes to this notice
We'll update this notice if our practices change, and show the date above. For significant changes, we'll tell you by email or in the Service.