Legal
Privacy policy
Last updated 14 November 2026
This policy covers the hosted Workly service: the public site at workly.run, the console at console.workly.run and the API at api.workly.run. It doesn't cover Workly when you run it yourself; that software doesn't send us anything.
The controller of your personal data is Euclides Invest AB, Org. no. 559510-0495, VAT no. SE559510049501, Rörsoppsvägen 8, 122 63 Stockholm, Sweden. Reach us at contact@workly.run.
What we collect
Your account
- Email address, to sign you in, and for the emails the service sends (sign-in links, invites, alerts you set up).
- Name, if you give one or your Google or GitHub account provides it, to show to the members of your workspaces.
- Sign-in identities. If you sign in with Google or GitHub, we store that account's ID and email address, so the same account signs you in next time. We don't get your password, and we only ask for your basic profile and email address.
- Workspaces, memberships, invites and roles, and when you accepted these terms.
- Sessions and API keys. Only hashes of them are stored, never the secrets themselves, with when an API key was last used.
- Connected apps. If you connect an app such as Claude or Cursor to a workspace, its name, the access you gave it, who connected it and when it was last used, with hashes of its tokens.
Billing
If you buy a paid plan, Stripe collects your billing name, email, address, VAT number if you give one, and payment card, and makes the invoices. We store your Stripe customer and subscription IDs and your plan; we never see your full card number.
What you send to Workly
Your tasks and schedules: their URLs, payloads and headers, and for each delivery attempt the response status, timing and the start of the response body. We process this only to deliver your tasks and show you their history. Finished tasks and schedule runs are deleted after 7 days; schedules and queues stay until you delete them.
If this content contains personal data, you are its controller and we process it on your behalf, as your processor. Please don't put more personal data in payloads than your endpoints need. Our data processing agreement is part of the terms and covers this processing.
Usage and technical data
- Usage counts per workspace (tasks created per day, API requests), to enforce plan limits and show you your usage.
- Server logs with IP addresses, requests and errors, to keep the service running and secure. They're kept for at most 30 days.
- Bot protection. The sign-in form may use Cloudflare Turnstile, which checks your browser for signs of automation. See Cloudflare's Turnstile privacy addendum.
- Analytics. To see how the site and the console are used and where they break, we run our own analytics (Dataflare) in our Cloudflare account, with the data stored in the EU. It is cookieless: it stores nothing on your device, and visitors are counted from a daily-rotating hash of the IP address and browser, so the IP address itself isn't kept. On the public site it records the pages you view, where you came from, your country, browser and device type, and page speed. In the console it also records what you do (such as signing in, finishing onboarding or creating a workspace), tied to your user and workspace IDs but never your email address or name. It never records what you type or your tasks' content, and doesn't record sessions. It isn't used for advertising and isn't shared with anyone.
Cookies
The console sets one cookie, workly_session, which keeps you signed in for up to 30 days, and while you sign in with Google or GitHub a short-lived cookie that ties the sign-in back to your browser. Both are strictly necessary, so they don't need consent. The public site and the docs set no cookies, and nothing here uses advertising trackers. Our analytics (see above) stores nothing on your device.
Why we process it, and on what basis
- To provide the service you signed up for: your account, sign-in, workspaces and task deliveries. Basis: performing our contract with you (GDPR article 6(1)(b)).
- To keep it secure and working: logs, rate limits, abuse and fraud prevention. Basis: our legitimate interest in running a secure service (article 6(1)(f)).
- To understand and improve the site and the service: our cookieless analytics. Basis: our legitimate interest in finding what's confusing or broken (article 6(1)(f)). You can object at any time by emailing us, or block it with any content blocker.
- To tell you about the service: changes to these terms, security notices, changes to your plan. Basis: contract and legitimate interest. We don't send marketing email without asking first.
- To meet legal obligations, such as keeping invoices and payment records for bookkeeping and tax. Basis: legal obligation (article 6(1)(c)).
We don't sell personal data, and we don't use your data or your tasks' content to train AI models.
Who processes it
We use these providers to run the service. Each processes personal data on our instructions, except that Stripe, Google and GitHub are also controllers of some of it for their own purposes: Stripe for fraud prevention and its legal obligations as a payment provider, Google and GitHub for your account with them. Their own privacy policies cover that part.
| Provider | What for | Where |
|---|---|---|
| Railway Corporation | Hosting of the service and its database | EU (Netherlands, europe-west4); US company |
| Cloudflare, Inc. | DNS, network proxy and DDoS protection, hosting of the public site, sending email, bot protection, hosting of our analytics, and nightly database backups (both stored in the EU) | Global network; US company |
| Stripe Payments Europe, Ltd. | Payments, invoices and tax for paid plans: your billing name, email, address, VAT number and payment card (we never see the full card number) | EU (Ireland); US parent company |
| Google LLC | Sign in with Google, only if you use it | US |
| GitHub, Inc. | Sign in with GitHub, only if you use it | US |
The service and its database run in the EU. Where a provider may access data from outside the EU/EEA, the transfer relies on the EU–US Data Privacy Framework or the European Commission's standard contractual clauses. We'll update this list before adding a provider.
We may disclose data when the law requires it, and then only what is required.
How long we keep it
- Account data: while your account exists. You can delete your account, or a workspace you own, in the console at any time, and it's deleted at once; if you ask us by email instead, we delete it within 30 days.
- Finished tasks and schedule runs: 7 days.
- Invoices and payment records: 7 years, as Swedish bookkeeping law requires.
- Unused sign-in links and codes: they expire after 15 minutes and are deleted soon after.
- Sessions: 30 days, or until you sign out.
- Server logs: up to 30 days.
- Backups of the database: 30 days. Data deleted from the service stays in them until they expire, and is only used to restore the service after a failure.
- Analytics events: 13 months.
Your rights
Under the GDPR you can ask for a copy of your personal data, have it corrected or deleted, restrict or object to our processing of it, and receive it in a portable format. Email contact@workly.run from the address on your account and we'll answer within a month. You can also complain to a data protection authority; ours is Integritetsskyddsmyndigheten (IMY).
Security
Traffic is encrypted with TLS. Sign-in tokens, sessions and API keys are stored only as hashes; signing secrets are encrypted at rest. The database is backed up every night, to storage in the EU. Deliveries can only reach public addresses, never our internal network. Access to production is limited to the people who run the service.
Children
Workly is a tool for developers and isn't meant for anyone under 16.
Changes
We'll update this page when what we do changes, and change the date at the top. For changes that matter, we'll email account holders before they take effect.
Contact us
Questions about privacy, or a request about your data: contact@workly.run