@ever-co/legal 0.1.2 → 0.2.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (88) hide show
  1. package/dist/content/aup/ever-async/en.html +778 -0
  2. package/dist/content/aup/ever-async/en.json +343 -0
  3. package/dist/content/aup/hust/en.html +9 -0
  4. package/dist/content/aup/hust/en.json +2 -2
  5. package/dist/content/cookies/ever-async/en.html +457 -0
  6. package/dist/content/cookies/ever-async/en.json +185 -0
  7. package/dist/content/cookies/ever-demand/en.html +5 -2
  8. package/dist/content/cookies/ever-demand/en.json +2 -2
  9. package/dist/content/cookies/ever-rec/en.html +5 -2
  10. package/dist/content/cookies/ever-rec/en.json +2 -2
  11. package/dist/content/cookies/ever-teams/en.html +5 -2
  12. package/dist/content/cookies/ever-teams/en.json +2 -2
  13. package/dist/content/cookies/ever-works/en.html +5 -2
  14. package/dist/content/cookies/ever-works/en.json +2 -2
  15. package/dist/content/cookies/gauzy/en.html +5 -2
  16. package/dist/content/cookies/gauzy/en.json +2 -2
  17. package/dist/content/cookies/githands/en.html +5 -2
  18. package/dist/content/cookies/githands/en.json +2 -2
  19. package/dist/content/cookies/hust/en.html +5 -2
  20. package/dist/content/cookies/hust/en.json +2 -2
  21. package/dist/content/dpa/ever-async/en.html +1848 -0
  22. package/dist/content/dpa/ever-async/en.json +640 -0
  23. package/dist/content/privacy/ever-async/en.html +1350 -0
  24. package/dist/content/privacy/ever-async/en.json +364 -0
  25. package/dist/content/privacy/ever-corporate/en.html +86 -3
  26. package/dist/content/privacy/ever-corporate/en.json +2 -2
  27. package/dist/content/privacy/ever-demand/en.html +99 -2
  28. package/dist/content/privacy/ever-demand/en.json +2 -2
  29. package/dist/content/privacy/ever-rec/en.html +110 -3
  30. package/dist/content/privacy/ever-rec/en.json +2 -2
  31. package/dist/content/privacy/ever-teams/en.html +97 -1
  32. package/dist/content/privacy/ever-teams/en.json +2 -2
  33. package/dist/content/privacy/ever-tech/en.html +86 -3
  34. package/dist/content/privacy/ever-tech/en.json +2 -2
  35. package/dist/content/privacy/ever-works/en.html +74 -5
  36. package/dist/content/privacy/ever-works/en.json +2 -2
  37. package/dist/content/privacy/everiq/en.html +107 -0
  38. package/dist/content/privacy/everiq/en.json +2 -2
  39. package/dist/content/privacy/gauzy/en.html +88 -3
  40. package/dist/content/privacy/gauzy/en.json +2 -2
  41. package/dist/content/privacy/githands/en.html +83 -2
  42. package/dist/content/privacy/githands/en.json +2 -2
  43. package/dist/content/privacy/hust/en.html +186 -37
  44. package/dist/content/privacy/hust/en.json +3 -3
  45. package/dist/content/privacy/traduora/en.html +93 -0
  46. package/dist/content/privacy/traduora/en.json +2 -2
  47. package/dist/content/refund/ever-rec/en.html +595 -0
  48. package/dist/content/refund/ever-rec/en.json +336 -0
  49. package/dist/content/security/ever-async/en.html +853 -0
  50. package/dist/content/security/ever-async/en.json +417 -0
  51. package/dist/content/security/ever-corporate/en.html +768 -0
  52. package/dist/content/security/ever-corporate/en.json +380 -0
  53. package/dist/content/security/ever-tech/en.html +768 -0
  54. package/dist/content/security/ever-tech/en.json +380 -0
  55. package/dist/content/security/traduora/en.html +768 -0
  56. package/dist/content/security/traduora/en.json +380 -0
  57. package/dist/content/subprocessors/ever-async/en.html +852 -0
  58. package/dist/content/subprocessors/ever-async/en.json +166 -0
  59. package/dist/content/subprocessors/ever-corporate/en.html +403 -9
  60. package/dist/content/subprocessors/ever-corporate/en.json +6 -2
  61. package/dist/content/subprocessors/ever-demand/en.html +443 -13
  62. package/dist/content/subprocessors/ever-demand/en.json +6 -2
  63. package/dist/content/subprocessors/ever-rec/en.html +493 -10
  64. package/dist/content/subprocessors/ever-rec/en.json +6 -2
  65. package/dist/content/subprocessors/ever-teams/en.html +435 -8
  66. package/dist/content/subprocessors/ever-teams/en.json +6 -2
  67. package/dist/content/subprocessors/ever-tech/en.html +443 -9
  68. package/dist/content/subprocessors/ever-tech/en.json +6 -2
  69. package/dist/content/subprocessors/ever-works/en.html +354 -13
  70. package/dist/content/subprocessors/ever-works/en.json +6 -2
  71. package/dist/content/subprocessors/everiq/en.html +484 -3
  72. package/dist/content/subprocessors/everiq/en.json +6 -2
  73. package/dist/content/subprocessors/gauzy/en.html +353 -20
  74. package/dist/content/subprocessors/gauzy/en.json +6 -2
  75. package/dist/content/subprocessors/githands/en.html +451 -13
  76. package/dist/content/subprocessors/githands/en.json +6 -2
  77. package/dist/content/subprocessors/hust/en.html +502 -12
  78. package/dist/content/subprocessors/hust/en.json +14 -2
  79. package/dist/content/subprocessors/traduora/en.html +461 -4
  80. package/dist/content/subprocessors/traduora/en.json +6 -2
  81. package/dist/content/tos/ever-async/en.html +1350 -0
  82. package/dist/content/tos/ever-async/en.json +687 -0
  83. package/dist/content/tos/ever-rec/en.html +40 -11
  84. package/dist/content/tos/ever-rec/en.json +5 -5
  85. package/dist/content/tos/hust/en.html +32 -8
  86. package/dist/content/tos/hust/en.json +10 -2
  87. package/dist/index.json +12493 -8166
  88. package/package.json +1 -1
@@ -755,6 +755,7 @@ data is most likely to reach.</p>
755
755
  <th>Sub-processor</th>
756
756
  <th>Purpose</th>
757
757
  <th>Location</th>
758
+ <th>Transfer mechanism</th>
758
759
  <th>Personal data</th>
759
760
  </tr>
760
761
  </thead>
@@ -763,32 +764,128 @@ data is most likely to reach.</p>
763
764
  <td>Cloudflare, Inc.</td>
764
765
  <td>Authoritative DNS, TLS termination, reverse proxy and bot filtering in front of everdemand.co, docs.everdemand.co and the content management system behind the website, and the tunnel that carries requests to our own servers.</td>
765
766
  <td>United States, with the connection terminated at the edge location nearest to the visitor</td>
767
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
766
768
  <td>IP address, request URL, headers and TLS metadata, cookies in transit</td>
767
769
  </tr>
768
770
  <tr>
769
771
  <td>Functional Software, Inc. d/b/a Sentry</td>
770
772
  <td>Error and performance monitoring for the website, the documentation site and the content management system, so that a failure is visible to us with enough context to fix it.</td>
771
773
  <td>United States</td>
774
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
772
775
  <td>IP address, browser and device, page or route being viewed, request context and breadcrumbs, which can contain fragments of what was submitted</td>
773
776
  </tr>
774
777
  <tr>
775
778
  <td>iubenda s.r.l.</td>
776
779
  <td>Cookie banner and consent record on everdemand.co — it displays the choice, applies it, and stores the proof of what you chose.</td>
777
780
  <td>Italy</td>
781
+ <td>None needed — established in the EEA</td>
778
782
  <td>IP address, consent choices and the record of them, timestamp and user agent</td>
779
783
  </tr>
780
784
  <tr>
781
- <td>Google LLC (reCAPTCHA)</td>
785
+ <td>Google Ireland Limited (reCAPTCHA)</td>
782
786
  <td>Bot protection on the public forms — contact, pricing notification and newsletter sign-up. It loads only on a page carrying a protected form.</td>
783
787
  <td>United States</td>
788
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
784
789
  <td>IP address, browser and device signals, mouse and interaction telemetry</td>
785
790
  </tr>
786
791
  <tr>
787
- <td>GitHub, Inc.</td>
792
+ <td>GitHub, Inc. (a Microsoft Corporation company)</td>
788
793
  <td>Source hosting, build pipeline and container registry for the website, the documentation site and the published source code. This is how the site is built and shipped, not where visitor data lives.</td>
789
794
  <td>United States</td>
795
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
790
796
  <td>contributor account names and public profile data, developer identity in build logs</td>
791
797
  </tr>
798
+ <tr>
799
+ <td>Cloudflare, Inc. (R2 object storage)</td>
800
+ <td>Holds the encrypted off-site copy of our backups - Postgres WAL and dumps, Velero, etcd, Proxmox configuration and MinIO mirrors - as the third tier of the backup chain (node8 NVMe, then Ceph RGW, then Cloudflare R2). Encrypted by us before it leaves our network.</td>
801
+ <td>United States</td>
802
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
803
+ <td>client-side encrypted backup archives only - no plaintext is ever readable by the provider, the archives themselves derive from every category of data the products hold</td>
804
+ </tr>
805
+ <tr>
806
+ <td>Google Ireland Limited (Google Workspace)</td>
807
+ <td>Hosts the corporate mailboxes that receive every support, privacy and rights request our own documents tell data subjects to write to, plus the recruitment mailbox that holds candidate CVs.</td>
808
+ <td>Ireland (contracting) / United States and global (Google LLC)</td>
809
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
810
+ <td>all inbound and outbound company email, support, DSAR and privacy correspondence with data subjects, candidate CVs and application correspondence (ever-tech careers), customer and supplier correspondence and attachments</td>
811
+ </tr>
812
+ <tr>
813
+ <td>Cloudflare, Inc. (Turnstile)</td>
814
+ <td>Checks that the person completing registration, onboarding or an anonymous flow is not a bot; on ever-works the API refuses the anonymous flow when no CAPTCHA provider is configured, which is why it is unconditional there.</td>
815
+ <td>United States</td>
816
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
817
+ <td>IP address, user agent and device signals, mouse, touch and timing interaction signals, Turnstile challenge cookie</td>
818
+ </tr>
819
+ <tr>
820
+ <td>Clerk, Inc.</td>
821
+ <td>Holds the account identity for the hosted cloc platform - name, email address, avatar, password or federated identity, sessions and multi-factor settings - so that our own database does not, and brokers the short-lived source-control credential used when the Service acts in a user's name.</td>
822
+ <td>United States</td>
823
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
824
+ <td>name, email address and avatar, password hash or federated identity, session, device and sign-in records, organisation membership and role, social-connection claims where a user signs in that way, the short-lived source-control credential brokered for a single request and not stored</td>
825
+ </tr>
826
+ <tr>
827
+ <td>Tavily</td>
828
+ <td>The default provider for public web search and page extraction, used by agents researching a topic and by the automated research that runs when an account is created, where the queries are built from the new account holder's name and email domain.</td>
829
+ <td>United States</td>
830
+ <td>To be confirmed — we do not yet evidence a mechanism</td>
831
+ <td>search queries, including a person's name and their employer's email domain, the addresses of pages retrieved and the extracted page content, our API key and request metadata</td>
832
+ </tr>
833
+ <tr>
834
+ <td>ui-avatars.com</td>
835
+ <td>Generates placeholder avatars where a person has no avatar of their own. The person's name or GitHub username is placed in the image URL, so it is disclosed to this provider every time the image is rendered in a customer's browser.</td>
836
+ <td>UNKNOWN - not published by the provider</td>
837
+ <td>To be confirmed — we do not yet evidence a mechanism</td>
838
+ <td>the developer's name or GitHub username, in the request URL, the viewing user's IP address and user agent</td>
839
+ </tr>
840
+ <tr>
841
+ <td>Prospect One sp. z o.o. (jsDelivr)</td>
842
+ <td>Serves the Lottie animation runtime hard-coded into the ever-works login and register pages, so every person who opens the login page hands their IP to it before authenticating.</td>
843
+ <td>Poland (operator); delivery worldwide</td>
844
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
845
+ <td>IP address, user agent, referring page URL</td>
846
+ </tr>
847
+ <tr>
848
+ <td>UNKNOWN - community-run npm CDN; no obtainable DPA counterparty identified</td>
849
+ <td>Second permitted origin for the Lottie animation runtime on the ever-works login and register pages.</td>
850
+ <td>United States (unverified)</td>
851
+ <td>To be confirmed — we do not yet evidence a mechanism</td>
852
+ <td>IP address, user agent, referring page URL</td>
853
+ </tr>
854
+ <tr>
855
+ <td>Resend, Inc.</td>
856
+ <td>Sends transactional mail for the products and domains configured against it, relaying onward through Amazon SES.</td>
857
+ <td>United States</td>
858
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
859
+ <td>recipient name and email address, message subject and body, delivery and bounce metadata</td>
860
+ </tr>
861
+ <tr>
862
+ <td>Langfuse GmbH</td>
863
+ <td>Stores the full prompts and completions of AI features together with model, latency and cost metadata, so that agent behaviour can be traced and scored.</td>
864
+ <td>Germany</td>
865
+ <td>None needed — established in the EEA</td>
866
+ <td>full prompt and completion text, which can contain user-authored content and personal data, user and session identifiers, model, latency, token and cost metadata, developer scoring outputs</td>
867
+ </tr>
868
+ <tr>
869
+ <td>OpenRouter, Inc.</td>
870
+ <td>Is the model provider behind the default 'Ever Works AI' option and the hard-coded default for AI Chat on every provisioned tenant site, receiving the raw prompt and forwarding it to whichever upstream model the selected model id resolves to.</td>
871
+ <td>United States</td>
872
+ <td>To be confirmed — we do not yet evidence a mechanism</td>
873
+ <td>full prompt text, including any customer or end-user content pasted into an agent - repo text, CVs, job descriptions, chat messages, generated completions, agent tool-call arguments, API key metadata and usage accounting</td>
874
+ </tr>
875
+ <tr>
876
+ <td>Chargebee, Inc. - VERIFY; Chargebee Europe BV (Netherlands) is the EEA entity if it is the one contracting.</td>
877
+ <td>Handles subscription billing and invoicing for the hosted Gauzy service.</td>
878
+ <td>United States / Netherlands</td>
879
+ <td>To be confirmed — we do not yet evidence a mechanism</td>
880
+ <td>billing identity and address, plan, invoice and payment history</td>
881
+ </tr>
882
+ <tr>
883
+ <td>Shopify International Limited</td>
884
+ <td>Runs the storefront and order pipeline for the shop product, holding customer, order and payment-status records.</td>
885
+ <td>Ireland (contracting) / Canada and United States (Shopify group)</td>
886
+ <td>Standard Contractual Clauses (EU 2021/914)</td>
887
+ <td>customer name, email address and shipping address, order and payment status, browsing and cart events on the storefront, cookies set by the storefront</td>
888
+ </tr>
792
889
  </tbody>
793
890
  </table>
794
891
  <p>The full and current list, including everything below, is published at
@@ -8,7 +8,7 @@
8
8
  "locale": "en",
9
9
  "version": "1.0.2",
10
10
  "effectiveDate": "2026-08-02",
11
- "sha256": "3ecb91e6b0dd8c885e3aea509db7000d8866e7c3d540447b4b93e1e692d065f4",
11
+ "sha256": "ddcf14329e5a45638b74eae654b617b6d7c9c5c3a83e58bcedb91bd6dfc71502",
12
12
  "publishable": true,
13
13
  "sections": [
14
14
  "core/privacy/010-introduction-and-scope",
@@ -360,5 +360,5 @@
360
360
  }
361
361
  ],
362
362
  "path": "content/privacy/ever-demand/en.html",
363
- "markdown": "# Privacy Policy\n\n**Ever Demand** — [everdemand.co](https://everdemand.co)\n\nVersion 1.0.2 · In force from 2026-08-02\n\nThis notice explains what we do with personal data when you use Ever Demand and the websites,\napplications and application programming interfaces we make available at [everdemand.co](https://everdemand.co)\n(together, the \"**Service**\"). It tells you what we collect, why, who else sees it, how long we keep it,\nand what you can ask us to do about it.\n\nWe have written it to be read rather than to be defended. Where something is uncomfortable — data we hold\nthat you never gave us, or data your employer decides to collect through our software — we say so plainly\ninstead of burying it in a list.\n\n## What this notice covers\n\n- The website at [everdemand.co](https://everdemand.co) and the pages served from it.\n- The Ever Demand web application, together with any desktop application, mobile application or\n browser extension we publish for it.\n- The application programming interfaces and integrations we operate for it.\n- The emails, notifications and support conversations that go with it.\n\nA product-specific annex appears later in this notice. It adds detail for Ever Demand — what it\nactually collects, what is switched off by default, and which controls exist. It sits on top of this\nnotice rather than instead of it, and where it is more specific about Ever Demand, the annex governs.\n\n## What this notice does not cover\n\n**Other companies' products.** Other companies operate their own websites, products and services, and\npublish their own privacy notices. This notice covers only what is listed above. If a service is not on\nthat list, this notice does not apply to it — whatever it looks like, and whoever links to it.\n\n**Software you run yourself.** Some of our software is published as open source and can be installed on\nyour own infrastructure. **If you run your own deployment, you are the controller of the personal data in\nit — not us.** You choose its hosting, its storage, its email provider and every other component. We have\nno access to that data, we do not process it, we are not your processor for it, and nothing in this notice\ndescribes it. Telling your own users what happens in your deployment is your job, not ours.\n\n**Sites we link to.** The Service links out to third-party websites and services. Once you follow a link\naway from us, the operator of that site decides what happens to your data. We do not control those sites,\nwe do not receive what you do on them, and we are not responsible for them. Read their notices, not this\none.\n\n**Your organisation's own systems.** Where your employer or another organisation uses the Service, it also\nruns systems of its own. This notice covers our part. Its notice covers its part.\n\n## Who we are\n\nThe controller of the personal data described in this notice is **Ever Technologies LTD**, a company\nregistered in Bulgaria under company number 204599535, with its registered office\nat Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria.\n\n\"Controller\" is the legal term for the organisation that decides why personal data is used and how.\nWherever this notice says we make that decision, **Ever Technologies LTD is the organisation accountable to\nyou** — and to the Commission for Personal Data Protection (Комисия за защита на личните данни) (CPDP), which\nis our lead supervisory authority.\n\nEver Technologies LTD operates Ever Demand and is the company you contract with for it. There\nis no other operator behind us and no second company you have to chase to get an answer.\n\nYou can reach us about anything in this notice at privacy@ever.co, or by post at the registered office\nabove.\n\nThere are parts of this notice where we are deliberately **not** the controller: where a customer puts\npersonal data about its own people into the Service, that customer decides, and we act on its instructions.\nThat split matters, so it has its own section below.\n\n## Other companies in our group\n\nThere is one other company in our group, and its role is narrow enough to state in a sentence.\n\n**Ever Co. LTD**, a company registered in Israel under company number\n515241842, with its registered office at HaAtsmaut 32/3, Ashdod 77452, Israel, owns the intellectual\nproperty in the software. Ever Technologies LTD operates the Service under licence from it.\n\nThat is the entire relationship. Its consequences are worth stating positively rather than leaving you to\nwork them out:\n\n- **Ever Co. LTD does not access personal data held in the Service.** No administration console,\n no production database, no support tooling, no backups, no error reports.\n- It is **not a controller** of that data, **not a processor** of it, and **not a sub-processor**. It does\n not appear on our sub-processor list, because there is nothing for it to appear against.\n- **No personal data is transferred to it.** No international transfer to Israel arises out of\n your use of the Service, because none happens.\n\nOwning software is not the same as having access to the data that software holds, and we have kept the two\napart on purpose.\n\nIf that ever changes — if Ever Co. LTD were to take on any role involving personal data from the\nService — we would update this notice before it happened, name the role, disclose the transfer and the\nsafeguard we relied on, and add it to our sub-processor list. **Until you read that here, none of it is\nhappening.**\n\n## Data protection contact\n\n**We have not designated a Data Protection Officer.** Article 13(1)(b) of the GDPR asks a controller to\npublish a Data Protection Officer's contact details where one has been designated. None has been designated\nat Ever Technologies LTD, so there are none to publish. We would rather tell you that outright than let a\nmailbox name imply otherwise. We keep the question under review, and if it changes we will publish the\ndetails here.\n\nWhat we do publish is a contact route that is monitored and acted on. **Privacy questions and requests to\nexercise your rights are handled through these addresses:**\n\n- **privacy@ever.co** — use this for anything about this notice, about the personal data we hold, or to\n make a request under any of your rights.\n- **dpo@ever.co** — an alias that reaches the same people. It exists because procurement forms,\n security questionnaires and privacy tooling routinely expect an address in that form. **It is a routing\n alias, not an office. Nothing about it means a Data Protection Officer has been designated.**\n\nYou can also write to us by post at the registered office given above.\n\nWe will acknowledge your message, and we will answer a request to exercise your rights within one month —\nthe deadline the GDPR sets. Where a request is genuinely complex, or where you have made several, we may\nextend that by up to two further months. If we do, we will tell you inside the first month and explain\nwhy.\n\n## Who decides what: controller and processor\n\nData protection law splits responsibility in two. The **controller** decides why personal data is used and\nhow. The **processor** only acts on the controller's instructions. Which of the two we are is not a\nformality — it decides who you go to, who has to answer you, and who is accountable when something goes\nwrong.\n\nOur position depends on whose data it is. There are three cases. We set them out here, in the privacy\nnotice, rather than leaving them to a data processing agreement, because the person most affected by the\nsecond case is usually the person least likely to read a contract.\n\n### 1. Our own relationship with you — we are the controller\n\nWhere we decide, we are accountable. **We are the controller** for:\n\n- registration and account identity — the name, email address and credentials used to create and hold an\n account;\n- billing, payments, invoices, tax records and collections;\n- support conversations, including the tickets, emails, chats and attachments themselves;\n- security, fraud prevention, abuse handling and audit logging;\n- our own websites and their analytics, our newsletters, and our marketing to prospective customers; and\n- running our business — accounting, insurance, professional advice, and defending claims.\n\nEverything in this notice about purposes, legal bases, retention, transfers and your rights applies to this\nfirst case directly, and you exercise those rights against us.\n\n### 2. Personal data a customer puts into the Service about its own people — the customer is the controller\n\nWhen an organisation subscribes to the Service and uses it to run its business, the personal data it puts\nin is **its** data. It decides what to collect, which features to switch on, why, and for how long to keep\nit. **We process that data only on that organisation's instructions.** For it, the organisation is the\ncontroller and we are the processor.\n\nThis covers the ordinary contents of a workspace — employee and contractor records, contact details,\nprojects, tasks, documents and messages. It also covers the parts that matter most, where a product\nprovides them and the customer has enabled them:\n\n- **time-tracking data** — timers, timesheets, time entries and the records behind them;\n- **activity data** — how much keyboard and mouse activity occurred in a period, idle time, and which\n applications and websites were in use;\n- **screen and media capture** — periodic screenshots and, where separately switched on, webcam stills,\n audio recordings and screen recordings.\n\n**We do not decide to collect any of this. The customer does.** We build the features, we document what\neach one captures and what each control does, and we run them exactly as the customer configures them. We\ndo not use that data for our own purposes, we do not use it to train models, and we do not look at it\nexcept where we must in order to run, secure or support the Service.\n\nWhat Ever Demand can capture, what is off by default, and which controls exist is set out in the annex\nlater in this notice.\n\n### 3. Data a customer holds about its own clients and end users — the customer is the controller\n\nWhere a customer uses the Service to serve its own clients, members, applicants, patients or website\nvisitors, that data sits in the same arrangement as case 2. The customer is the controller, we are the\nprocessor, and the customer owes those people the notice and the answers. If you have dealt with an\norganisation and want to know what it holds about you, ask that organisation.\n\n### If you are monitored at work, this part is for you\n\nWe would rather tell you directly than make you work it out from a contract you have never seen.\n\n**Your employer decides what is captured. We do not.** Screenshots, activity rates, application and website\nusage, webcam stills, audio, screen recordings — each of these is a setting your employer switches on or\nleaves off, for the organisation and, where the product allows it, for individual people. We cannot switch\nthem on for your employer, and we do not switch them on for ourselves.\n\n**Your employer is the controller of that data.** That means your employer, not us:\n\n- must have a lawful basis for monitoring you, under the GDPR and under its own national employment law,\n which differs sharply from country to country;\n- must tell you, before it starts, what is captured, how often, why, and how long it is kept;\n- must carry out a data protection impact assessment where one is required, and act on what it finds;\n- must consult a works council, employee representatives or a trade union where its national law requires\n that; and\n- must answer your requests about that data.\n\n**We make no claim that monitoring employees is lawful across the European Union, because it is not.** Some\ncountries restrict it tightly, some require consultation before it starts, and some prohibit particular\nforms of it outright. Whether your employer's use of these features is lawful where you work is your\nemployer's responsibility. We require every customer to confirm to us that it has dealt with each of the\npoints above before it uses these features.\n\n**How to exercise your rights over monitoring data.** Send your request to your employer — it holds the\ndata and it has to answer you. If you send it to us instead, we will not ignore it:\n\n- we will forward it promptly to the customer whose workspace holds the data;\n- we will tell you that we have done so, and to whom, so you are not left waiting on silence; and\n- we will help that customer find, correct, export or delete the data, which is what our contract with it\n requires of us.\n\n**What we will not do is release one organisation's data to someone else on request.** We cannot verify an\nemployment relationship from the outside, and handing over a workspace's contents to a person the customer\nhas not authorised would be a breach in its own right. That restraint protects you as much as it\nconstrains you.\n\nIf you think your employer is monitoring you unlawfully, you can complain to the data protection authority\nin your own country, and to your national labour authority. You do not need our permission, and you do not\nneed to come through us first.\n\n## Personal data we collect\n\nWe group this by where the data comes from, because that is what determines what we know about you and what\nwe owe you.\n\nNot every category applies to every product, plan or user. This section describes the shape of what we\ncollect; the annex later in this notice lists what Ever Demand actually collects.\n\n### What you give us\n\n- **Account identity** — your name, username, email address, password (held only as a hash), profile\n picture, job title, preferred language and time zone.\n- **Organisation details** — the organisation you belong to, your team, your role and permissions within\n it, and who invited you.\n- **Contact details** — email address, telephone number and postal address, where you provide them.\n- **Billing details** — billing name and address, VAT or tax identification number, the plan you are on,\n invoices and payment history. **We do not receive or hold your full card number** — that goes straight to\n our payment processor.\n- **Support correspondence** — the tickets, emails, chat messages, screenshots and files you send when you\n ask for help, and our replies.\n- **Content you submit** — everything you or your organisation puts into the Service: documents, tasks,\n projects, records, messages and uploads. Where that content belongs to your organisation, we hold it as\n processor, not as controller.\n- **Anything else you volunteer** — survey answers, feedback, event registrations, newsletter sign-ups, and\n whatever you choose to write to us.\n\n### What we collect automatically when you use the Service\n\n- **Device and browser data** — device type, operating system, browser and version, screen size, language,\n and the version of our application you are running.\n- **Connection data** — your IP address, and the approximate location it indicates. **That is\n city-or-region level, derived from the IP address**, and it is not satellite positioning. Where a\n specific feature collects precise location, it says so.\n- **Usage data** — pages and screens viewed, features used, actions taken, navigation paths, timestamps and\n the page that referred you.\n- **Logs** — server and application logs of requests, errors, response times, sign-ins, failed sign-ins and\n administrative actions, with the identifiers needed to tie an entry to an account.\n- **Diagnostics** — crash reports, stack traces and performance traces. These can incidentally contain\n whatever was in the request that failed.\n- **Cookies and similar technologies** — cookies, local storage, pixels, software development kit\n identifiers and comparable device storage. What each is for, and which ones need your consent, is in our\n [Cookie Policy](https://everdemand.co/cookies).\n\n### What we receive from other people\n\n- **Identity providers** — if you sign in with a third-party account, we receive that account's identifier,\n your email address, your display name and usually your profile picture, plus confirmation that the\n sign-in succeeded. **We never receive your password for it.**\n- **Payment processors** — whether a payment succeeded or failed, the payment method type, the last four\n digits and expiry of a card, the billing country, and any dispute or chargeback.\n- **Integrations you or your administrator connect** — whatever the connected service returns within the\n permissions granted. That varies by integration and is shown to you when you authorise it.\n- **Your organisation** — where an administrator creates your account, invites you, sets your role or\n imports records about you.\n- **Other sources**, where a particular product uses them. Those are set out in the next section and in the\n annex.\n\n### What you have to give us\n\nSome of it is unavoidable. Without account identity we cannot create an account for you; without billing\ndetails we cannot take payment for a paid plan; without certain records we cannot meet our own legal\nobligations. Where data is necessary in that sense, **not providing it means we cannot provide that part of\nthe Service** — but nothing worse follows.\n\nEverything else — an optional profile field, a newsletter subscription, an integration you could simply not\nconnect — is genuinely optional, and declining it costs you nothing.\n\n## Data we do not collect\n\nShorter than the previous section, and just as binding. These are commitments about how the Service is\nbuilt, not aspirations.\n\n- **We do not sell personal data.** Not to data brokers, not to advertisers, not to anyone — and not under\n the broader definitions of \"sell\" or \"share\" used outside the European Union.\n- **We do not buy marketing lists.** If we contact you about our products it is because you gave us your\n details, or because you are already a customer. We do not purchase your name from someone else in order\n to email you.\n- **We do not use your content to train machine-learning models** — not for our own purposes, and not for\n the benefit of other customers. Where a product has an AI feature, it processes your content to produce\n your result, and that is the end of it. If we ever want that to change, it will be an opt-in you actively\n choose, described before you choose it.\n- **We do not run advertising inside the Service.** No third-party advertising, no behavioural ad\n targeting, no cross-site advertising identifiers in the product.\n- **We do not record what you type.** Where a product measures keyboard and mouse activity, it counts\n events over a period. **There is no keylogger in our software. The content of your keystrokes is never\n captured, stored or transmitted.**\n- **We do not ask for special-category data** — health, racial or ethnic origin, religious or philosophical\n beliefs, political opinions, trade union membership, sex life or sexual orientation, genetic or biometric\n data. There are no fields for it, we do not infer it, and we do not want it. The one honest caveat is\n about what can end up inside a screenshot, and it has its own section below.\n- **We do not store full card numbers or card security codes.** Those are entered on our payment\n processor's systems and never reach ours.\n- **We do not collect precise location by default.** Where a product uses location at all, it is because a\n specific feature needs it, and that feature says so.\n\nIf you find any of this to be untrue of something we ship, tell us at privacy@ever.co. We will treat it\nas a defect in the product, not as a disagreement about wording.\n\n## Where data comes from when it does not come from you\n\nNot all of the personal data we hold came from you. Article 14 of the GDPR requires us to tell you where it\ncame from, and this section does that.\n\n- **Your employer, or the administrator of your workspace.** Where an organisation subscribes to the\n Service, an administrator creates accounts, invites people, sets roles and imports records. That supplies\n your name, work email address, job title, team, role and permissions, and whatever else the organisation\n chooses to hold about you in its workspace. **For that data the organisation is the controller**, as set\n out above.\n- **Identity providers.** If you sign in with a third-party account, that provider supplies the account\n identifier, your email address, your display name and usually a profile picture, and confirms the sign-in\n succeeded. It supplies nothing else, and never a password.\n- **Integrations you or your administrator connect.** A connected service supplies whatever the permissions\n you granted allow — for example issues and repositories from a code host, messages and channel names from\n a chat tool, calendar entries, contacts, or records from another business system. The scope is shown when\n the connection is authorised, and it can be revoked in the same place.\n- **Payment processors and resellers.** They supply the outcome of a payment, the payment method type, the\n last four digits and expiry of a card, the billing country, and any dispute or chargeback. They do not\n pass us the card itself.\n- **Publicly available sources, where a product builds profiles from them.** Some products work with\n information people have published themselves — a public code-hosting profile, a public company page, a\n public professional listing. Where a product does this, the annex names the categories taken and the\n sources they came from, explains the basis we rely on, and says how to object. **If we hold a profile\n about you that you never gave us, you can object to it and we will act on that.**\n- **Service providers acting for us.** Fraud and abuse signals, delivery and bounce information from the\n systems that send our email, and security intelligence about addresses and networks.\n\nWhere we are the controller of personal data that did not come from you, we will tell you within a\nreasonable period and at the latest within one month of obtaining it — or, if we use it to contact you, at\nthat first contact. Where informing every individual separately would take disproportionate effort, this\nnotice and its annex are the public information we provide instead, which is what Article 14(5)(b) allows.\n\n## Why we use personal data, and on what legal basis\n\nArticle 6 of the GDPR requires a lawful basis for each purpose. So this is one row per purpose, rather than\na general list of all six bases — you can check us against each line.\n\n| Purpose | Personal data used | Lawful basis |\n|---|---|---|\n| Providing Ever Demand: creating and running your account, signing you in, delivering the features you use, and keeping your data available to you | Account identity, organisation and role, credentials, content you submit, device and connection data | **Contract** — Art 6(1)(b). Necessary to perform our agreement with you |\n| Taking payment: invoicing, collecting fees, applying refunds, chasing non-payment | Billing details, plan and subscription data, invoices, payment outcomes | **Contract** — Art 6(1)(b) |\n| Keeping accounting, tax and invoicing records | Invoices, payment records, billing identity | **Legal obligation** — Art 6(1)(c), under tax and accounting law |\n| Support: answering your questions, investigating faults and reproducing problems you report | Support correspondence, account identity, logs and diagnostics, and whatever you point us at | **Contract** — Art 6(1)(b) where you are a customer. **Legitimate interests** — Art 6(1)(f) where you are not, so that we can answer anyone who writes to us |\n| Security and abuse prevention: authentication, rate limiting, bot and fraud detection, investigating misuse, protecting accounts and infrastructure | Account identity, IP address, device data, request logs, sign-in and failed sign-in records | **Legitimate interests** — Art 6(1)(f) in keeping the Service and the people who use it safe |\n| Keeping the Service running: monitoring, error tracking, debugging, capacity planning and backups | Logs, diagnostics, usage data, account identifiers | **Legitimate interests** — Art 6(1)(f) in operating a reliable service |\n| Understanding how the Service is used, so we can improve it | Usage events, feature interactions, device and browser data, aggregated statistics | **Legitimate interests** — Art 6(1)(f). **Consent** — Art 6(1)(a) wherever cookies or similar device storage are involved, as set out in our [Cookie Policy](https://everdemand.co/cookies) |\n| Marketing to people who are not yet customers: newsletters, product announcements and events | Contact details, marketing preferences, whether you opened or clicked a message | **Consent** — Art 6(1)(a), which you can withdraw at any time |\n| Marketing our own similar products to an existing customer who gave us their address during a sale, with an opt-out in every message | Contact details, the products you already have | **Legitimate interests** — Art 6(1)(f), relying on the narrow existing-customer exception in the ePrivacy rules |\n| Meeting legal obligations: responding to lawful requests from authorities, sanctions and export-control checks, statutory record-keeping, and our own data protection duties | Whatever the specific obligation requires, and no more | **Legal obligation** — Art 6(1)(c) |\n| Establishing, exercising or defending legal claims, and handling complaints, disputes, audits, insurance and corporate transactions | Account and billing records, correspondence, and the logs relevant to the matter | **Legitimate interests** — Art 6(1)(f) in protecting our legal position |\n\nTwo things this table deliberately does not cover.\n\n**Where we act as processor**, the lawful basis is not ours to pick. The customer that put the data into\nthe Service decides the purpose and must have its own basis for it. See the controller and processor\nsection above.\n\n**Where we rely on your consent**, you can withdraw it at any time, and withdrawing it is as easy as giving\nit. Withdrawing consent does not make earlier processing unlawful — it stops the processing from that point\non.\n\n## The legitimate interests we rely on\n\nWhere the table above says \"legitimate interests\", the law requires us to tell you what that interest\nactually is — not simply to name the basis and move on. For each one we have asked three questions: what is\nthe interest, is the processing genuinely necessary for it, and is it fair to you. That last question is\nthe balancing test, and we keep a written record of it.\n\n### Keeping the Service and its users secure\n\n- **The interest:** preventing unauthorised access, account takeover, fraud, spam, denial-of-service and\n abuse of the Service.\n- **Why the processing is necessary:** you cannot see an attack without looking at the traffic. Sign-in\n records, IP addresses, device data and request logs are what make an intrusion visible at all.\n- **Why it does not override your rights:** the data is limited to what security work needs, it is kept for\n a bounded period, and the benefit goes to the same accounts and the same people whose data is used. Nobody\n reasonably expects a service to be run without security logging.\n\n### Keeping the Service running\n\n- **The interest:** operating a reliable service — monitoring, error tracking, debugging, capacity planning\n and backups.\n- **Why the processing is necessary:** faults surface in logs, and a crash report is only useful if it\n records what was happening when the crash occurred.\n- **Why it does not override your rights:** it is operational data, kept for short periods, used to fix\n software rather than to form views about people, and reachable only by the staff who need it.\n\n### Understanding how the Service is used\n\n- **The interest:** knowing which features are used, where people get stuck, and what to build or fix next.\n- **Why the processing is necessary:** the alternative is guessing. Aggregate usage data is the only\n practical way to see this without interrogating every user.\n- **Why it does not override your rights:** we analyse it in aggregate rather than to make decisions about\n you individually, and wherever cookies or similar device storage are involved we ask for your consent\n instead of relying on this interest at all.\n\n### Answering people who write to us without an account\n\n- **The interest:** replying to a question from someone who is not a customer.\n- **Why the processing is necessary:** we cannot answer you without keeping your message and your address.\n- **Why it does not override your rights:** you chose to contact us, we use it only to answer, and we keep\n it no longer than the matter and any follow-up require.\n\n### Telling existing customers about our own similar products\n\n- **The interest:** letting people who already buy from us know about the products next to the one they\n bought.\n- **Why the processing is necessary:** it uses the address they gave us during that sale, and there is no\n less intrusive way to reach them.\n- **Why it does not override your rights:** it is confined to our own similar products, every message\n carries a one-click opt-out, and an opt-out is acted on immediately and permanently.\n\n### Running and protecting our business\n\n- **The interest:** accounting, audit, insurance, professional advice, complaints, disputes, enforcing our\n terms, and evaluating or completing a corporate transaction.\n- **Why the processing is necessary:** these are ordinary obligations of operating a company, and each one\n needs the records that relate to it.\n- **Why it does not override your rights:** the data is confined to the matter in hand, access is narrow,\n and a great deal of it we are required to keep in any event.\n\n### Your right to object\n\n**You can object to any processing we base on legitimate interests, at any time, by writing to\nprivacy@ever.co.** Tell us which processing, and where you can, why — your particular situation is part\nof the balance. We will stop unless we can show compelling legitimate grounds that override your interests,\nrights and freedoms, or unless we need the data to establish, exercise or defend legal claims.\n\n**If you object to direct marketing there is no balancing at all. We stop.** That right is absolute.\n\nYou can also ask us for a summary of the balancing test behind any interest listed above, and we will give\nyou one.\n\n## Special categories of data\n\nSome personal data carries extra protection under Article 9 of the GDPR: data revealing racial or ethnic\norigin, political opinions, religious or philosophical beliefs or trade union membership, and genetic data,\nbiometric data used to identify someone, data concerning health, and data about a person's sex life or\nsexual orientation. Data about criminal convictions and offences is restricted separately, under Article 10.\n\n**We do not seek any of it.** We do not ask for it at sign-up, in billing or in support. There are no\nfields for it, we do not infer it, and we do not enrich profiles with it. Please do not send it to us in a\nsupport ticket either — if you need to show us something sensitive to get help, redact it first.\n\n### The honest caveat: incidental capture\n\nWhere a customer switches on screen capture, webcam capture or audio capture, **what gets captured is\nwhatever is there**. A screenshot taken while someone has a hospital appointment email open captures health\ndata. A webcam still can show a religious head covering. An audio recording can pick up a background\nconversation that has nothing to do with work.\n\nThat is not a theoretical risk and we will not present it as one. It is a direct consequence of capturing a\nscreen or a room on a timer, and it is true of every product that does it, ours included.\n\n### Whose responsibility it is\n\n**The customer that switches these features on is the controller of what they capture**, including anything\nspecial-category that comes with it. So the customer, not us:\n\n- decides whether to enable capture at all, and has to judge whether the benefit justifies the intrusion;\n- must carry out a data protection impact assessment before starting, and act on what it finds — capture of\n this kind will normally require one;\n- must have a lawful basis, and where special-category data is realistically in scope must also satisfy\n Article 9(2), which an employee's consent rarely does on its own, because of the imbalance between\n employer and employee;\n- must configure the product to reduce that risk rather than accept it; and\n- must deal with what has been captured, including deleting a capture that should never have been taken.\n\nWe are the processor for it. We do not decide to capture anything, we do not review captures for our own\npurposes, and we act on the customer's configuration and instructions.\n\n### The levers, and using them\n\nWhere a product offers screen or media capture, it also offers controls that materially reduce this risk.\nDepending on the product, those include:\n\n- switching capture off entirely, for the whole organisation or for an individual person;\n- switching off the more intrusive capture types — webcam stills, audio and screen recording — while\n keeping the rest;\n- reducing how often captures are taken;\n- blurring captured images;\n- shortening how long captures are kept, and deleting them automatically at the end of that period;\n- letting people see what has been captured about them; and\n- deleting an individual capture.\n\n**If you are a customer, these are yours to set, and the defaults are not a recommendation.** Choose the\nleast intrusive configuration that meets the purpose you actually have, and write down why you chose it.\nThat record is what a supervisory authority will ask for.\n\n**If you are being monitored and something sensitive has been captured, ask your employer to delete it.**\nYour employer can do that in the product. If you tell us instead, we will forward your request and help\nyour employer act on it, as described in the controller and processor section above.\n\nWhich of these controls Ever Demand provides, and what its defaults are, is set out in the annex later\nin this notice.\n\n## Annex: Ever Demand\n\nThis annex describes what the Ever Demand software actually holds and what we actually do with it. It\nis written from the code, not from the product page, and where the software falls short of what a privacy\nnotice would like to promise, it says so.\n\n### Which of three situations you are in\n\nEverything else in this annex depends on this, and getting it wrong in either direction would be the single\nworst mistake in the document. **There is no hosted Ever Demand platform today.** What we operate under this\nname is a website, a documentation site and the content management system behind them.\n\n**1. Somebody runs the software themselves — the ordinary case.**\nThe business that deployed it is the controller. It chose the hosting, the database, the payment account,\nthe mapping key and every other component. **No personal data from that deployment reaches us. We are not\nits processor, we have no access to it, and nothing in this notice describes it.** If you are a shopper, a\ncourier or a merchant on a deployment somebody else runs, the business behind it is the organisation that\nowes you answers, and it is the one to ask.\n\n**2. We host an instance for you.**\nUnder the free-hosting offer in our [Terms of Service](https://everdemand.co/tos), or under an Enterprise\nengagement. Then **you are the controller** of the shopper, courier, merchant and order data, and **we are\nyour processor** for it. We are separately the controller of the narrow set of records described in the\ncontroller-and-processor section above — your administrator contacts, our correspondence with you, and our\nown security and audit logs.\n\n**3. You are visiting [everdemand.co](https://everdemand.co) or the documentation site.**\n**We are the controller.** Contact form submissions, the pricing-notification form, newsletter sign-ups,\nthe support chat, bot protection on those forms, and — after you consent — analytics. What is set on your\ndevice is in our [Cookie Policy](https://everdemand.co/cookies).\n\n### The people the platform holds data about\n\nNamed individually rather than swept into \"users\", because their positions are genuinely different:\n\n- **shoppers** — people with an account who order;\n- **prospective shoppers who have no account** — someone who submitted an invite request and is waiting for\n a store to approve it;\n- **couriers** — enrolled by an administrator, never by self-registration;\n- **merchant and warehouse staff** — likewise enrolled by an administrator;\n- **platform administrators** — who can see every shopper, courier, merchant and order, and the live map;\n- **delivery recipients who did not place the order** — the person at the address, where a shopper has\n ordered to somebody else's home.\n\n### What the platform holds\n\n| Category | What is in it |\n|---|---|\n| Identity | First and last name, and a profile or logo image address |\n| Contact | Email address and telephone number, for shoppers, couriers and merchant contacts, including a merchant's separate orders mailbox and orders telephone number |\n| Credentials | A hashed password, session and access tokens |\n| Social identity | The account identifier returned by Google or Facebook, where the operator has enabled social sign-in |\n| Delivery location | Country, city, street, house, apartment, postcode, a free-text notes field, and a precise geographic point held for map and proximity searching |\n| Courier position | The courier's current device position while on duty — see the next section, which is the important one |\n| Courier work data | Online or offline status, lifetime deliveries, deliveries today, distance travelled today, orders skipped, and an administrator-controlled flag that switches an account off |\n| Orders | Basket contents, prices, order number, whether it is delivery or collection, and the full timestamp chain from placement through to completion, plus which courier and which warehouse handled it |\n| The order snapshot | A copy of the ordering shopper written into the order itself — see the limitations section below |\n| Payment identifiers | The payment provider's customer and charge identifiers, and card metadata such as brand, last four digits and expiry. Full card numbers go to the payment provider and are not held by the platform |\n| Devices | Device identifier, platform, language, and the push notification channel identifier |\n| Merchant gateway credentials | The payment keys a merchant configures for its own store, held in the platform database — see the limitations section |\n| Logs | Application and service logs, which contain identifiers and can contain fragments of a request |\n\nThe free-text delivery **notes** field deserves a separate mention: it is unstructured and unvalidated, and\npeople write whatever helps a courier find them. Some of what ends up there is far more personal than the\naddress itself.\n\n### Courier location — exactly what happens\n\nVagueness here reads as concealment, so this is precise.\n\n- **While the courier's own status is set to Online, the courier application reads the device's position\n approximately every three seconds and sends it to the server.**\n- **While the courier's status is Offline, nothing is read.** The application does not sample position, and\n there is no background collection when the courier is off duty. That gate is in the courier's own hands\n and it is the strongest design fact in this product.\n- **The stored value is the current position, overwritten by the next reading.** The platform does not build\n a location history table.\n- **The position is shown to platform administrators, to the merchant, and to the shopper who placed the\n order**, inside the shopping application, while the delivery is running.\n\nThat last point is the one that matters most and the one operators most often fail to disclose. **A\ncourier's live position being visible to a member of the public is a materially different thing from a\ndispatcher watching a fleet map**, and a courier is entitled to be told about it before it starts, not\nafter.\n\nWhere we host an instance, **we do not decide any of this**. The operator decides whether to run the\ncourier application at all, who may see the map, and whether the ordering shopper sees the courier. Our\n[Data Processing Addendum](https://everdemand.co/dpa) treats courier position and courier work data as monitoring\ndata and puts the corresponding obligations on the operator in binding terms.\n\n### Courier work data\n\nAlongside position, the platform accumulates counters about the person doing the work: **lifetime\ndeliveries, deliveries completed today, distance travelled today, orders skipped, and the record of going\nonline and offline.** There is also an administrator-controlled flag that switches a courier's account off\nentirely.\n\nThese are performance measures. They are not a by-product of dispatch — an employer can read them as a\nproductivity score, and some will.\n\n**Our position on them is deliberate rather than accidental.** Where we host an instance, we compute and\nstore these counters on the operator's instruction and for no purpose of our own. We do not benchmark\ncouriers, we do not compare them across operators, we do not build or sell an industry dataset from them,\nand we do not use them to train anything. **If we ever derived anything from them for a purpose of our own,\nwe would become a controller of that, and we would say so here before we did it.**\n\n### If you are a courier\n\nYou will not have signed up for this, so it is worth reading.\n\n- Your position is read only while **you** have set your status to Online. Setting it to Offline stops it.\n Nothing is read from your device when you are off duty.\n- While you are on a delivery, **the customer waiting for it can see where you are**, as well as your\n dispatcher and the store.\n- The application also counts your deliveries, the distance you have covered today and the orders you have\n skipped, and the business that gave you the account can see all of it.\n- **The business that gave you the account decides all of this, and holds the data.** Ask them what they\n collect, why, how long they keep it, and who sees it. If we host their instance, we will help them answer\n you — the section on your rights above explains how we route a request that comes to us instead.\n\n### People who never signed up\n\nThree groups end up in the platform without ever agreeing to anything, and **the obligation to tell them\nsits with the operator of the deployment, not with us**:\n\n- **Invite requesters.** A person with no account submits a street address, house, apartment, postcode and a\n device identifier, and that record waits in a store's console for approval. That is a residential address\n held about somebody with no account and no relationship with anyone but the store.\n- **Couriers and merchant staff.** The account is created by an administrator before the worker's first\n contact with the software.\n- **Delivery recipients who did not order.** A shopper can send an order to somebody else's home, and the\n address, apartment number and delivery notes are then visible to the store, the courier and the\n administrators.\n\nWhere we host an instance, our [Data Processing Addendum](https://everdemand.co/dpa) requires the operator to give\nthose people the notice the law requires. **We cannot give it for them: we do not know who these people are,\nand in most cases we have no way to reach them.**\n\n### Three limitations we are not going to hide\n\nOverstating what our software can do would be its own misrepresentation, so here is what it cannot.\n\n- **Records are marked deleted, not erased.** Every record carries a deleted flag, and there is no hard\n erasure path anywhere in the service layer. Marking something deleted removes it from the application; it\n does not remove it from the database.\n- **Every order carries a copy of the shopper.** When an order is created, the shopper's name, email\n address, image, delivery location and apartment are copied into the order document — and in the published\n code, so is the stored password hash. **Deleting or changing the shopper's own record does not reach those\n copies.** Anyone running a deployment should treat the order snapshot as containing authentication\n material and remove it.\n- **Payment material reaches the logs, and merchant keys sit in the database.** The payment-method handler\n writes the payment provider's token and card object into the application log at information level, and the\n payment keys a merchant configures for its own store — including the secret one — are held in the platform\n database and are readable from the administration console.\n\n**We will not host an instance for anyone until the credential copy and the payment logging are fixed in the\ncode we would be running.** For a deployment you run, all three are yours to deal with, and the\n[Security page](https://everdemand.co/security) sets out what to do about them.\n\n### How long data is kept\n\n**The platform ships no automatic retention or deletion routine.** Records persist until somebody removes\nthem. There is one genuine exception, and it works in your favour: **courier position is a single current\nvalue that the next reading overwrites**, so no position history accumulates.\n\nIn a deployment you run, retention is something you have to implement and describe — it is not something the\nsoftware does for you, and saying otherwise in your own privacy notice would be inaccurate. Where we host an\ninstance, you set the periods, we apply them, and we will tell you honestly which records our tooling can\nreach and which it cannot.\n\nThe retention section above covers what we hold as controller for our own website and our own\ncorrespondence, which is a different and much smaller set of data.\n\n### Automated decisions inside the platform\n\nThree mechanisms are worth naming: orders are allocated to couriers, a courier can skip an order and that is\nrecorded, and a store owner approves or refuses an invite request. **All three are the operator's\nconfiguration and the operator's decision-making, not ours.** We do not rank or score couriers, and we do\nnot operate any allocation logic of our own.\n\nIf an operator uses the work counters to make a decision about a courier that produces legal effects or\nsimilarly significantly affects them, that is the operator's processing to justify, and the courier's rights\nin relation to it run against the operator.\n\n### If a deployment shows you a privacy page\n\nThe software bundles its own privacy and terms pages, which a deployment serves to its own users. **Those\npages describe that deployment, and the business running it is responsible for their content.** If a page\nserved by a deployment we do not run names any Ever company as the controller of that deployment, it is\nwrong — the controller is the business that deployed the software, and that is who you should contact.\n\n### Our website\n\nOn [everdemand.co](https://everdemand.co) and the documentation site we hold what you send us through the\ncontact form, the pricing-notification form, the newsletter sign-up and the support chat — a name, an email\naddress, an organisation and whatever you write — together with the ordinary connection and usage data\ndescribed above. **We are the controller for all of it.** What is stored on your device, what waits for your\nconsent, and who the providers are is in our [Cookie Policy](https://everdemand.co/cookies).\n\n## Cookies and similar technologies\n\nCookies, local storage, pixels, software development kits and similar technologies get their own document,\nbecause they need more detail than a summary can carry. What each one is, what it does, how long it lasts,\nwho operates it and how to refuse it is set out in our [Cookie Policy](https://everdemand.co/cookies).\n\nIn short, we sort them into four categories:\n\n- **Strictly necessary** — needed to deliver what you asked for: signing you in, holding your session,\n routing traffic, remembering your cookie choice itself, and protecting forms and sign-in against\n automated abuse. These are not optional, and we do not ask for consent to them.\n- **Preferences** — remember choices you have made, such as language, region and interface settings.\n- **Analytics** — help us understand how the Service is used so we can improve it.\n- **Marketing** — measure our campaigns and help us understand which organisations take an interest in us.\n\n**Nothing in the preferences, analytics or marketing categories is placed or read on your device until you\nagree to it.** You can accept everything, refuse everything, or choose category by category, and refusing\ntakes exactly as few clicks as accepting.\n\n### Changing your mind\n\nYour choices are not permanent. A **Cookie preferences** link sits in the footer of every page on\n[everdemand.co](https://everdemand.co) and reopens the same panel you saw the first time. Change a category\nthere and it takes effect immediately, for the future. Withdrawing is as easy as agreeing, and nothing\nabout the Service is withheld from you for refusing.\n\nOne analytics tool runs without consent, because it is configured so that it stores and reads nothing on\nyour device and never builds a persistent identifier for you. That is a conditional position, not a\npermanent one: the [Cookie Policy](https://everdemand.co/cookies) names the tool, describes the exact\nconfiguration we rely on, and says what happens if any part of that configuration ever changes.\n\n## Who receives your personal data\n\nWe disclose personal data only to the categories of recipient below, and only as much as each one needs to\ndo the job it is there for.\n\n- **Service providers acting as our processors** — hosting and infrastructure, storage, content delivery,\n email delivery, error monitoring, product analytics, customer support tooling and similar. They act on\n our documented instructions under a written contract that meets Article 28 GDPR, they are bound to\n confidentiality and appropriate security, and **they may not use your data for their own purposes**.\n- **Payment processors** — to take payment, issue invoices and handle refunds and disputes. For their own\n regulated obligations — fraud prevention, anti-money-laundering, card-scheme rules — they act as\n controllers in their own right, and their own privacy notice governs that part.\n- **Professional advisers** — lawyers, accountants, auditors and insurers, bound by professional\n confidentiality, where we need advice or have to evidence that we have complied with something.\n- **Public authorities, courts and regulators** — where the law requires us to disclose, or where we need\n to establish, exercise or defend a legal claim. We check that a request has a proper legal basis and is\n no wider than it needs to be, we push back where it is not, and we tell you about it unless we are\n legally prohibited from doing so.\n- **An acquirer or successor** — if we are reorganised, merged or sold, or if part of the business changes\n hands, personal data may pass to the acquirer as part of that transaction. The acquirer is bound by this\n policy or by a notice at least as protective, and we will tell you before anything about the handling of\n your data changes.\n\n### The sub-processors we engage for the hosted Service\n\nThese providers are engaged for the hosted Service as it is delivered to everyone. They are the ones your\ndata is most likely to reach.\n\n| Sub-processor | Purpose | Location | Personal data |\n|---|---|---|---|\n| Cloudflare, Inc. | Authoritative DNS, TLS termination, reverse proxy and bot filtering in front of everdemand.co, docs.everdemand.co and the content management system behind the website, and the tunnel that carries requests to our own servers. | United States, with the connection terminated at the edge location nearest to the visitor | IP address, request URL, headers and TLS metadata, cookies in transit |\n| Functional Software, Inc. d/b/a Sentry | Error and performance monitoring for the website, the documentation site and the content management system, so that a failure is visible to us with enough context to fix it. | United States | IP address, browser and device, page or route being viewed, request context and breadcrumbs, which can contain fragments of what was submitted |\n| iubenda s.r.l. | Cookie banner and consent record on everdemand.co — it displays the choice, applies it, and stores the proof of what you chose. | Italy | IP address, consent choices and the record of them, timestamp and user agent |\n| Google LLC (reCAPTCHA) | Bot protection on the public forms — contact, pricing notification and newsletter sign-up. It loads only on a page carrying a protected form. | United States | IP address, browser and device signals, mouse and interaction telemetry |\n| GitHub, Inc. | Source hosting, build pipeline and container registry for the website, the documentation site and the published source code. This is how the site is built and shipped, not where visitor data lives. | United States | contributor account names and public profile data, developer identity in build logs |\n\nThe full and current list, including everything below, is published at\n[https://everdemand.co/subprocessors](https://everdemand.co/subprocessors), together with the notice period and\nobjection procedure that apply when we add or replace one.\n\n### Three tiers, and why the difference matters\n\nA single flat list of every vendor that appears anywhere in our software would be both inaccurate and\nmisleading, so the sub-processor page is split into three tiers. They mean genuinely different things.\n\n- **Always engaged.** The providers above. If you use the hosted Service, these are in the path.\n- **Engaged only if you turn something on.** Optional integrations, connectors and features. A provider in\n this tier is engaged only when you or your workspace administrator enables the specific feature or\n connects the specific account it belongs to. Enable nothing and it is never involved. The list says which\n feature or setting activates each one.\n- **Self-hosted deployments only.** Several of our products are published as open source and can be run on\n your own infrastructure. In that case **you** choose the database, object storage, email relay, AI\n provider and everything else, using your own credentials. Those providers appear in the list so you can\n see what the software can be pointed at — but they are **your** providers, not ours. **We process nothing\n in a deployment you run, we are not your processor for it, and the commitments in this policy do not\n describe it.**\n\n### We do not sell your personal data\n\nWe do not sell personal data, and we do not share it for cross-context behavioural advertising. We do not\nsupply it to data brokers, we do not trade it for services, and we do not permit any provider we engage to\nuse it to build advertising or interest profiles, on our sites or anywhere else.\n\n## Sending personal data outside the EEA\n\nMost of the personal data we hold stays inside the European Economic Area, on infrastructure we operate\nourselves. Some of it does not: a number of the providers we engage are established outside the EEA —\nprincipally in the United States — and some of them route, cache or store data on servers outside it.\n\nWhere that happens, the transfer needs a lawful mechanism under Chapter V GDPR. We use one of the\nfollowing for every transfer, and the sub-processor page names the destination country and the mechanism\nprovider by provider.\n\n### Adequacy\n\nWhere the European Commission has decided that a country provides an adequate level of protection, the\ntransfer relies on that decision and needs nothing further. Adequacy decisions are kept under review by\nthe Commission and can be amended, suspended or repealed, so we monitor them rather than treat them as\npermanent.\n\n### Providers in the United States\n\nFor a US provider we rely on one of two things.\n\n- **The EU–US Data Privacy Framework**, but only where that provider is *actively self-certified* under it\n for the type of data concerned. We check the official Data Privacy Framework list when we engage a\n provider and re-check it periodically. **We do not claim the Framework for a provider that has not\n certified, or whose certification has lapsed.**\n- **Standard Contractual Clauses** — the clauses approved by the European Commission in Implementing\n Decision (EU) 2021/914, with the modules that match the relationship, together with a transfer impact\n assessment and supplementary measures: encryption in transit and at rest, minimising what is sent in the\n first place, contractual limits on onward disclosure, and a commitment from the provider to notify and\n where possible challenge a government access request.\n\n**We keep Standard Contractual Clauses in place as the standing mechanism**, including for providers that\nare also certified under the Framework. That is deliberate, and here is the honest reason.\n\nThe Commission's adequacy decision for the Framework, adopted on 10 July 2023, is currently valid. It was\nchallenged, and on 3 September 2025 the General Court of the European Union dismissed that challenge in\n*Latombe* (Case T-553/23). **That is not the end of it** — an appeal is pending before the Court of\nJustice as Case C-703/25 P, and the two arrangements that preceded this one were each struck down by the\nsame court. So we treat the Framework as a mechanism under review rather than a settled answer, and we\nkeep a second mechanism standing behind it so that a change in the law is a paperwork event for us and not\nan interruption for you.\n\n### Other countries\n\nFor a transfer to any other country without an adequacy decision, we use Standard Contractual Clauses with\nthe same assessment and supplementary measures. Where a transfer is to the United Kingdom or Switzerland,\nthe corresponding UK and Swiss additions are applied to those clauses.\n\nWe rely on an Article 49 derogation — for example, a transfer that is strictly necessary to perform a\ncontract you have asked us to perform — only in a specific, occasional case where no other mechanism fits.\nIt is not a routine mechanism for us, and we do not use it to run a regular data flow.\n\n### Getting a copy of the safeguards\n\nYou are entitled to see the safeguards we rely on. Write to privacy@ever.co naming the provider or the\ntransfer you are asking about, and we will send you a copy of the relevant clauses and tell you which\nmodules apply. We may redact commercial terms such as pricing and service levels; we do not redact the\ndata protection terms, which are the part that concerns you.\n\n## How long we keep personal data\n\n\"As long as necessary\" is not an answer, so here are the actual periods. Each one runs from the event in\nthe middle column, and at the end of it we delete the data or irreversibly anonymise it.\n\n| What we hold | How long we keep it | Why that period |\n|---|---|---|\n| Account and profile data — name, email address, workspace membership, settings | For as long as the account is open, then deleted within **30 days** of closure | We need it to give you the account; after that we do not |\n| Content and files you put into the Service | For as long as the account is open; after it ends, available for export for **30 days**, then deleted | You decide what is in it — see below |\n| Invoices, payment records and the tax data attached to them | **10 years** from the end of the accounting year in which the transaction fell | Accounting and tax law in Bulgaria requires it, and we cannot shorten it at your request |\n| Record that you accepted our terms — version, date, method | **5 years** after the agreement ends | The general limitation period for a claim under the contract |\n| Support correspondence and tickets | **24 months** from the last message in the thread | Long enough to handle a recurring problem and a follow-up; not longer |\n| Security, access and audit logs | **12 months** | Investigating unauthorised access, and evidencing that we did |\n| Application and error logs, crash reports, diagnostics | **90 days** | Fixing what broke; they lose value quickly |\n| Marketing contact records and the evidence of your consent | Until you object or withdraw. We then remove you from the lists and keep only a suppression record — your email address and the date — so that we do not contact you again | An unsubscribe that forgets you is not an unsubscribe |\n| Cookie and consent choices | As stated in the [Cookie Policy](https://everdemand.co/cookies), which gives the lifetime of each entry | It belongs with the technology it describes |\n| Backups | Each backup ages out on its own rolling cycle, within **30 days** | Recovering from failure and ransomware, without becoming a second archive |\n| Anything we are required to preserve for a legal claim, investigation or regulatory request | Until the claim, investigation or request ends, including any appeal period | We are not allowed to delete evidence, and neither are you |\n\n### Data that belongs to one of our customers\n\nFor personal data held inside a customer's workspace — including anything the Service captures about that\ncustomer's own personnel — **the customer sets the retention period, not us**. We are their processor for\nit. The defaults and the limits of what they can configure are described in the product annex to this\npolicy.\n\nWe delete that data when the customer instructs us to, or at the end of the export window after their\nagreement ends, whichever comes first. If you are one of their people and you want their data about you\ndeleted sooner, ask them — see the section on your rights, which explains how we route that.\n\n### What \"delete\" means here\n\nDeletion is applied to live systems straight away. Backup copies are not individually edited — doing so\nwould defeat what a backup is for — so a deleted record persists in backups until that backup ages out on\nthe cycle above, at most 30 days. During that window the data is not used for anything, and **we do not\nrestore a backup to bring back data someone asked us to delete**; a backup is restored only to recover a\nwhole system after a failure.\n\nWhere we can keep something useful without keeping you identifiable, we anonymise instead of deleting —\naggregate usage counts, for example. Once anonymised the data is no longer personal data, and it is not\npossible for us to re-identify you from it.\n\n## How we protect personal data\n\nWe take the measures Article 32 GDPR requires: technical and organisational safeguards appropriate to the\nrisk, reviewed as the risk changes. In practice that means the following.\n\n- **Encryption in transit.** Traffic to and from the Service travels over TLS. HTTPS is enforced, and\n plain HTTP requests are redirected rather than served.\n- **Encryption at rest.** The storage holding customer content, databases and backups is encrypted at\n rest, and particularly sensitive values — credentials, tokens and keys — are additionally encrypted at\n the application layer rather than stored in readable form.\n- **Access control and least privilege.** Access to production systems is limited to the people whose job\n needs it, granted by named individual accounts rather than shared logins, protected by multi-factor\n authentication, scoped to the narrowest role that works, and reviewed and revoked when a role changes or\n someone leaves.\n- **Network segmentation.** Databases, storage and internal services sit on segmented internal networks\n and are not exposed to the public internet. Administrative interfaces are not publicly reachable.\n- **Logging.** Administrative and security-relevant events are logged, retained for the period in the\n retention section, and monitored so that unusual activity raises an alert rather than sitting unread.\n- **Backups.** Data is backed up regularly, held on separate infrastructure from the live systems, and\n restores are tested — an untested backup is a guess, not a control.\n- **Vulnerability management.** Dependencies are scanned, code is analysed automatically before it ships,\n security patches are applied on a defined schedule with a faster path for serious issues, and we operate\n a responsible disclosure route so that anyone who finds a problem can tell us.\n- **Personnel.** Everyone with access is bound by written confidentiality obligations that outlast their\n engagement, works on a need-to-know basis, and has access removed when it is no longer needed.\n- **Providers.** We assess a provider before we engage it, contract with it under Article 28 GDPR, and\n hold it to security obligations at least as strict as our own.\n\nOur [Security page](https://everdemand.co/security) sets out the detail, including which measure applies to\nwhich part of the Service, our incident response process, and the shared responsibility split between what\nwe secure and what you secure.\n\n### What we do not claim\n\n**We do not hold a SOC 2 report and we are not certified to ISO/IEC 27001, and we do not claim either.**\nIf anything you read or are told suggests otherwise, it is wrong, and we would like to know where it came\nfrom. Where we describe a practice on this page or on the Security page, we describe something we actually\ndo; where we adopt a framework as a reference without being audited against it, we say so plainly rather\nthan implying a certification.\n\n### No system is perfectly secure\n\n**No service, ours included, can be made completely secure, and anyone who tells you otherwise is\nselling something.** What we can honestly promise is that we take the measures above seriously, that we\nkeep them under review, and that if a personal data breach affects you we will act on it: we notify the\nCPDP where the law requires it, within the deadline it sets, and we\ntell affected people directly without undue delay where the breach is likely to result in a high risk to\nthem.\n\nYour part matters too. Use a strong and unique password, turn on multi-factor authentication where it is\noffered, keep your devices patched, and do not share credentials or access tokens. If you think an account\nhas been compromised, tell us at privacy@ever.co immediately.\n\n## Your rights over your personal data\n\nWhere we are the controller, the GDPR gives you the rights below. They are yours to use, you do not have\nto explain why you are using them, and using one costs you nothing.\n\n- **Access** — ask whether we hold personal data about you and, if we do, get a copy of it together with\n the information in this policy about how it is used. (Article 15)\n- **Rectification** — have inaccurate data corrected and incomplete data completed. Much of this you can\n do yourself in your account settings, which is faster than asking us. (Article 16)\n- **Erasure** — have data deleted where we no longer need it for the purpose we collected it for, where\n you withdraw the consent it rested on, or where we have processed it unlawfully. (Article 17)\n- **Restriction** — have us pause processing while a dispute is sorted out: while we check an accuracy\n challenge, for example, or while we consider an objection. We keep the data but stop using it.\n (Article 18)\n- **Portability** — receive the data you gave us, in a structured, commonly used, machine-readable format,\n and have it sent to another provider where that is technically feasible. This applies to data processed\n by automated means on the basis of your consent or a contract with you. (Article 20)\n- **Objection** — object to processing we base on our legitimate interests. We then stop unless we can\n demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or unless\n we need the data for a legal claim. (Article 21(1))\n- **Objection to direct marketing** — **absolute, and there is nothing to weigh.** If you tell us to stop\n using your data for direct marketing, including any profiling connected to it, we stop. No balancing\n test, no grace period, no exceptions. (Article 21(2))\n\nYou also have the right to withdraw consent where consent is what we rely on, which has its own section\nbelow, and the right to complain to a supervisory authority, which has the section after that.\n\nSome of these rights have limits written into the law itself. Erasure does not override an obligation to\nkeep invoices for the statutory accounting period, and portability does not extend to data we inferred or\ngenerated rather than received from you. **Where we cannot do all of what you ask, we will tell you which\npart we cannot do and why**, rather than declining as a whole.\n\n### How to make a request\n\nWrite to privacy@ever.co. Tell us which right you are using and enough about yourself for us to find\nthe right records — the email address on the account is usually enough. You can also write to us by post\nat the address at the end of this policy.\n\n- **It is free.** We charge nothing for a request. If a request is manifestly unfounded or excessive,\n particularly because it repeats one we have already answered, the law lets us charge a reasonable fee\n based on our administrative cost or refuse it. If we ever do either, we will explain why and tell you\n how to challenge that decision.\n- **We answer within one month** of receiving the request. Where a request is complex, or where you have\n made several, we may extend that by up to two further months — and if we do, **we will tell you within\n the first month, and tell you why**.\n- **We check who you are** before we hand over personal data, because the alternative is handing your data\n to someone who claims to be you. We ask for the least that makes us confident, usually a reply from the\n email address already on the account. We ask for an identity document only where nothing lighter works,\n and anything you send us for verification is used for that and nothing else, then deleted.\n\n### If your data sits in a customer's workspace\n\n**This is the most important paragraph on this page for many of the people who read it.**\n\nA large part of the personal data in the Service was put there by one of our customers — your employer,\nthe organisation whose workspace you belong to, or the operator of a site built on our platform. Where the\nService captures data about how an organisation's own personnel work, that data belongs to that\norganisation's workspace.\n\n**For that data the customer is the controller and we are only their processor.** We process it on their\ndocumented instructions and for no purpose of our own, so the law directs your request to them, not to us.\nPractically:\n\n- **Send your request to that organisation.** They decide it, and they are the ones who have to answer you\n within the deadline.\n- **If you send it to us instead, we will not ignore it.** We will forward it to the relevant customer\n promptly, tell you that we have done so, and assist them in answering it as our Data Processing Addendum\n requires.\n- **We will not decide the request ourselves, and we will not delete, correct or hand over data from a\n customer's workspace without their instruction** — unless a law that applies to us requires it. That is\n not us being unhelpful: acting on a workspace's data without the controller's instruction is precisely\n what a processor is not allowed to do.\n\nIf you are not sure which of the two situations you are in, ask us at privacy@ever.co and we will tell\nyou, and point you to the right organisation if it is not us.\n\n## Withdrawing your consent\n\nWhere we rely on your consent for something, **you can withdraw it at any time, and withdrawing is as easy\nas giving it**. You do not have to give a reason, and we do not ask you to justify it.\n\nWithdrawing consent stops the processing from that point onwards. **It does not make what we did before\nunlawful** — processing carried out while your consent was in force stays lawful, and withdrawal does not\nundo it. What it does mean is that we stop, and that we do not start again unless you tell us to.\n\n### How to withdraw, purpose by purpose\n\n- **Cookies and similar technologies** — open the **Cookie preferences** link in the footer of any page on\n [everdemand.co](https://everdemand.co), turn off the categories you no longer want, and save. The change\n takes effect immediately. Details are in our [Cookie Policy](https://everdemand.co/cookies).\n- **Marketing emails** — use the unsubscribe link at the bottom of any message we send you, or write to\n privacy@ever.co and ask us to stop. Either route works, and the unsubscribe link does not require\n you to sign in or find your password first.\n- **Optional features and integrations you switched on** — turn the feature off, or disconnect the\n connected account, in your settings. If you cannot find the switch, ask us at privacy@ever.co and we\n will turn it off for you.\n\nIf you have consented to something not listed here, write to privacy@ever.co naming it, and we will\nact on it the same way.\n\n### What happens next\n\nWe stop the processing, and we remove you from the relevant list or turn the relevant feature off. We keep\nthe minimum record needed to show that you consented and that you withdrew, because being able to evidence\nconsent is itself a legal requirement — for how long, see the retention section.\n\n**We will not quietly move the same processing onto a different legal basis to keep it running.** If some\npart of what you asked us to stop genuinely rests on another basis as well — an invoice we are required to\nkeep, for example — we will tell you which part and why, rather than leaving you to discover it.\n\nMost of what we do is not based on consent at all. It rests on performing our contract with you, on legal\nobligations, or on legitimate interests. **Withdrawing consent therefore does not close your account or\nswitch off the Service** — it affects only the things you consented to.\n\n## Complaining to a supervisory authority\n\nIf you think we have handled your personal data badly or unlawfully, **you have the right to complain to a\ndata protection supervisory authority**. That right is yours regardless of anything else in this policy.\n\nWe would like the chance to put it right first. Write to privacy@ever.co, tell us what went wrong, and\nwe will look into it and come back to you. In most cases that is the quickest way to get the outcome you\nactually want. **You are not required to do this, and it is not a condition of complaining** — you can go\nstraight to an authority, and you can do it at any point, including while we are still dealing with your\ncomplaint.\n\n### Our lead supervisory authority\n\nWe are established in Bulgaria, so our lead authority is the\n**Commission for Personal Data Protection (Комисия за защита на личните данни)** — the CPDP. Its website,\nincluding its complaint form and current contact details, is at\n[https://www.cpdp.bg/](https://www.cpdp.bg/).\n\n### You can also complain closer to home\n\nUnder Article 77 GDPR you may lodge your complaint with the supervisory authority in the EU or EEA country:\n\n- where you live;\n- where you work; or\n- where the thing you are complaining about took place.\n\nYou do not have to use ours, and you do not need our agreement to use another one. If you complain to your\nlocal authority, it will co-operate with ours through the mechanism the GDPR sets up for exactly this\nsituation, so nothing is lost by choosing whichever is easiest for you.\n\nYou also have the right to an effective judicial remedy — against a supervisory authority's decision, and\nagainst us directly — in the courts of the country where you live or where we are established. Complaining\nto an authority does not use up that right.\n\n## Automated decision-making and profiling\n\n**We do not make decisions about you that produce legal effects concerning you, or that similarly\nsignificantly affect you, based solely on automated processing.** No algorithm of ours decides whether you\nare hired, paid, promoted, disciplined, dismissed, given credit, or charged a different price. Where a\ndecision of that kind is made about you by an organisation using the Service, a person at that\norganisation makes it.\n\nWe do use automated rules to detect fraud, spam, abuse and attacks against the Service — rate limits,\nanomaly detection, and similar. Those rules can block a request or temporarily restrict an account. If one\nof them affects you, write to privacy@ever.co and a person will review it.\n\n### Where a customer turns on AI features, be aware of this\n\nThis is the part worth reading carefully, because it is easy to misunderstand.\n\nSome of our products capture activity data on behalf of a customer — an employer, typically — and some of\nthem offer optional AI features on top of it. **Where a customer enables those features, the Service can\ngenerate automated assessments of the activity it captures.** The clearest example: classifying whether\nthe content of a captured screen appears to be work-related. Other examples include scoring or summarising\ncaptured activity and grouping it into categories.\n\nFour things follow, and we would rather state them plainly than let them be discovered later.\n\n- **The output goes to the customer, not to us.** It is presented to the organisation whose workspace the\n data belongs to. **That organisation is the controller of it, and we are only its processor.**\n- **The customer decides what, if anything, to do with it.** We do not act on these assessments, we do not\n use them for any purpose of our own, and we do not share them with anyone else.\n- **These outputs are not decisions, and must not be used as if they were.** An automated assessment is an\n input to a human judgement. **Our terms require the customer not to treat an output of the Service as an\n automated decision about a person, and to apply meaningful human review before acting on one.** Whether\n any particular use is lawful where that customer operates — including the lawful basis for it, the\n notices it has to give, any impact assessment it has to carry out, and any consultation with employee\n representatives it has to run — is that customer's responsibility to determine, not ours.\n- **They can be wrong.** A classifier reading a screen has no idea what your job is. It can label genuine\n work as unrelated, and it can miss the opposite. Anyone relying on one of these outputs should treat it\n as a rough signal, and we say so to our customers as well as to you.\n\n### If an assessment about you has been generated\n\nAsk the organisation whose workspace holds the data — normally your employer. You can ask them for human\ninvolvement, for an explanation of how the assessment was reached, to express your point of view, and to\ncontest the result. They are the controller, so they are the ones who have to answer.\n\nIf you send that request to us, we will forward it to them promptly, tell you we have done so, and assist\nthem in answering it. See the routing paragraph in the section on your rights, which explains why we\ncannot decide it ourselves.\n\n## Children\n\n**The Service is not directed at children, and we do not knowingly collect personal data from them.** It\nis a business product, bought by organisations and used by the people who work in them. We do not design\nit for children, we do not market it to them, and we do not offer accounts to them.\n\nWhere consent is the basis for an online service offered directly to a child, the GDPR sets the age at\nwhich the child can consent alone. **In Bulgaria that age is 14.** Other EU and EEA countries set\nit anywhere between 13 and 16, and the age in the country where the child lives is the one that applies.\nBelow that age, consent has to come from — or be authorised by — a holder of parental responsibility.\nBecause we do not offer the Service to children, we do not operate a parental consent mechanism, and a\nchild under the applicable age should not create an account or submit personal data to us.\n\n### If a child's data has reached us\n\nTell us. Write to privacy@ever.co with enough detail for us to find the record — an email address, an\naccount name, or the page where the data was submitted. You do not need to prove anything first, and you\ndo not need to be the child's parent to report it.\n\nWe will check, and where we confirm that we hold personal data collected from a child without proper\nauthorisation, **we will delete it without undue delay**, keeping only what a law that applies to us\nrequires us to keep.\n\nIf the data sits inside one of our customers' workspaces rather than in our own records, the customer is\nthe controller of it. Tell them as well, and tell us — we will forward your report to them and press for\nit to be dealt with, as the routing paragraph in the section on your rights describes.\n\n## Links and content from other sites\n\nOur websites and the Service link to services we do not run, and some pages embed content that other\npeople host — videos, maps, code repositories, documentation and similar.\n\nFollowing a link takes you somewhere this policy does not reach. Loading embedded content means the\nprovider hosting it receives data directly from your browser, typically your IP address, your device and\nbrowser details, and the page you were on, and it may set its own cookies.\n\n**We do not control those services, and this policy does not apply to them.** What they collect and what\nthey do with it is governed by their own privacy notice, which is the one to read before you use them.\nWhere embedded content is not strictly necessary to deliver a page, we load it only once you have agreed\nto the relevant cookie category — see our [Cookie Policy](https://everdemand.co/cookies).\n\nA link is not an endorsement. If a link from our site takes you somewhere that mishandles your data, we\nwould like to know at privacy@ever.co so we can reconsider carrying it.\n\n## Changes to this policy\n\nThis policy changes when the Service changes, when we engage or replace a provider, or when the law moves.\nWe would rather update it than let it drift out of date and quietly stop being true.\n\nEvery version carries a version number and the date it takes effect, shown at the top of the page. **This\nis version 1.0.2, in force from 2026-08-02.**\n\n### How we tell you\n\n- **Minor changes** — clarifying wording, correcting a mistake, adding a provider of a kind already\n described — are published with a new version number and a new effective date. We do not send a separate\n notice for these.\n- **Material changes** — a new purpose, a new category of personal data, a new category of recipient, a\n longer retention period, a change to how you exercise your rights, or a change to the legal basis we\n rely on — are notified **at least 30 days before they take effect**, by email to account holders and by\n a notice on the site. That gives you time to read them and to act before they apply.\n- **Changes that need your consent** are not made by publishing a new version. We ask you, and we treat\n silence as a no.\n\nThis policy is a notice, not a contract. **We do not ask you to accept it**, and continuing to use the\nService is not us collecting your agreement to it. Where we genuinely need your agreement to something, we\nask for it separately and record it.\n\n### Previous versions stay available\n\nWe do not overwrite the past. **Every version of this policy that we have published remains available**,\nwith the dates it was in force, from the version history linked at the foot of\n[https://everdemand.co/privacy](https://everdemand.co/privacy). If you want to know what we said about your data on a\nparticular date, that is where to look — and if you cannot find it, ask us at privacy@ever.co and we\nwill send it to you.\n\n## How to contact us\n\nThe controller for the personal data described in this policy is **Ever Technologies LTD**, registered in\nBulgaria under company number 204599535, with its registered office at\nMladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria.\n\n- **Privacy questions, and any request about your personal data** — privacy@ever.co\n- **Data protection correspondence** — dpo@ever.co\n\nBoth addresses are monitored by the same people, and either will reach us. By post, write to the registered\noffice above and mark the letter for the attention of the privacy team. We correspond in English.\n\n**We have not designated a Data Protection Officer under Article 37 GDPR.** The dpo@ever.co address is\na contact channel, not a designation, and we will not describe it as one. If that position changes, this\npolicy will say so and will give the designated office's contact details.\n\nIf your question is about personal data held inside one of our customers' workspaces, that customer is the\ncontroller and the request goes to them — see the routing paragraph in the section on your rights. Write to\nus anyway if you are unsure, and we will tell you who to ask.\n\nThis document is version 1.0.2 of the Privacy Policy for\n[everdemand.co](https://everdemand.co), in force from 2026-08-02. Earlier versions, with the\ndates they applied, are at [https://everdemand.co/privacy](https://everdemand.co/privacy)."
363
+ "markdown": "# Privacy Policy\n\n**Ever Demand** — [everdemand.co](https://everdemand.co)\n\nVersion 1.0.2 · In force from 2026-08-02\n\nThis notice explains what we do with personal data when you use Ever Demand and the websites,\napplications and application programming interfaces we make available at [everdemand.co](https://everdemand.co)\n(together, the \"**Service**\"). It tells you what we collect, why, who else sees it, how long we keep it,\nand what you can ask us to do about it.\n\nWe have written it to be read rather than to be defended. Where something is uncomfortable — data we hold\nthat you never gave us, or data your employer decides to collect through our software — we say so plainly\ninstead of burying it in a list.\n\n## What this notice covers\n\n- The website at [everdemand.co](https://everdemand.co) and the pages served from it.\n- The Ever Demand web application, together with any desktop application, mobile application or\n browser extension we publish for it.\n- The application programming interfaces and integrations we operate for it.\n- The emails, notifications and support conversations that go with it.\n\nA product-specific annex appears later in this notice. It adds detail for Ever Demand — what it\nactually collects, what is switched off by default, and which controls exist. It sits on top of this\nnotice rather than instead of it, and where it is more specific about Ever Demand, the annex governs.\n\n## What this notice does not cover\n\n**Other companies' products.** Other companies operate their own websites, products and services, and\npublish their own privacy notices. This notice covers only what is listed above. If a service is not on\nthat list, this notice does not apply to it — whatever it looks like, and whoever links to it.\n\n**Software you run yourself.** Some of our software is published as open source and can be installed on\nyour own infrastructure. **If you run your own deployment, you are the controller of the personal data in\nit — not us.** You choose its hosting, its storage, its email provider and every other component. We have\nno access to that data, we do not process it, we are not your processor for it, and nothing in this notice\ndescribes it. Telling your own users what happens in your deployment is your job, not ours.\n\n**Sites we link to.** The Service links out to third-party websites and services. Once you follow a link\naway from us, the operator of that site decides what happens to your data. We do not control those sites,\nwe do not receive what you do on them, and we are not responsible for them. Read their notices, not this\none.\n\n**Your organisation's own systems.** Where your employer or another organisation uses the Service, it also\nruns systems of its own. This notice covers our part. Its notice covers its part.\n\n## Who we are\n\nThe controller of the personal data described in this notice is **Ever Technologies LTD**, a company\nregistered in Bulgaria under company number 204599535, with its registered office\nat Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria.\n\n\"Controller\" is the legal term for the organisation that decides why personal data is used and how.\nWherever this notice says we make that decision, **Ever Technologies LTD is the organisation accountable to\nyou** — and to the Commission for Personal Data Protection (Комисия за защита на личните данни) (CPDP), which\nis our lead supervisory authority.\n\nEver Technologies LTD operates Ever Demand and is the company you contract with for it. There\nis no other operator behind us and no second company you have to chase to get an answer.\n\nYou can reach us about anything in this notice at privacy@ever.co, or by post at the registered office\nabove.\n\nThere are parts of this notice where we are deliberately **not** the controller: where a customer puts\npersonal data about its own people into the Service, that customer decides, and we act on its instructions.\nThat split matters, so it has its own section below.\n\n## Other companies in our group\n\nThere is one other company in our group, and its role is narrow enough to state in a sentence.\n\n**Ever Co. LTD**, a company registered in Israel under company number\n515241842, with its registered office at HaAtsmaut 32/3, Ashdod 77452, Israel, owns the intellectual\nproperty in the software. Ever Technologies LTD operates the Service under licence from it.\n\nThat is the entire relationship. Its consequences are worth stating positively rather than leaving you to\nwork them out:\n\n- **Ever Co. LTD does not access personal data held in the Service.** No administration console,\n no production database, no support tooling, no backups, no error reports.\n- It is **not a controller** of that data, **not a processor** of it, and **not a sub-processor**. It does\n not appear on our sub-processor list, because there is nothing for it to appear against.\n- **No personal data is transferred to it.** No international transfer to Israel arises out of\n your use of the Service, because none happens.\n\nOwning software is not the same as having access to the data that software holds, and we have kept the two\napart on purpose.\n\nIf that ever changes — if Ever Co. LTD were to take on any role involving personal data from the\nService — we would update this notice before it happened, name the role, disclose the transfer and the\nsafeguard we relied on, and add it to our sub-processor list. **Until you read that here, none of it is\nhappening.**\n\n## Data protection contact\n\n**We have not designated a Data Protection Officer.** Article 13(1)(b) of the GDPR asks a controller to\npublish a Data Protection Officer's contact details where one has been designated. None has been designated\nat Ever Technologies LTD, so there are none to publish. We would rather tell you that outright than let a\nmailbox name imply otherwise. We keep the question under review, and if it changes we will publish the\ndetails here.\n\nWhat we do publish is a contact route that is monitored and acted on. **Privacy questions and requests to\nexercise your rights are handled through these addresses:**\n\n- **privacy@ever.co** — use this for anything about this notice, about the personal data we hold, or to\n make a request under any of your rights.\n- **dpo@ever.co** — an alias that reaches the same people. It exists because procurement forms,\n security questionnaires and privacy tooling routinely expect an address in that form. **It is a routing\n alias, not an office. Nothing about it means a Data Protection Officer has been designated.**\n\nYou can also write to us by post at the registered office given above.\n\nWe will acknowledge your message, and we will answer a request to exercise your rights within one month —\nthe deadline the GDPR sets. Where a request is genuinely complex, or where you have made several, we may\nextend that by up to two further months. If we do, we will tell you inside the first month and explain\nwhy.\n\n## Who decides what: controller and processor\n\nData protection law splits responsibility in two. The **controller** decides why personal data is used and\nhow. The **processor** only acts on the controller's instructions. Which of the two we are is not a\nformality — it decides who you go to, who has to answer you, and who is accountable when something goes\nwrong.\n\nOur position depends on whose data it is. There are three cases. We set them out here, in the privacy\nnotice, rather than leaving them to a data processing agreement, because the person most affected by the\nsecond case is usually the person least likely to read a contract.\n\n### 1. Our own relationship with you — we are the controller\n\nWhere we decide, we are accountable. **We are the controller** for:\n\n- registration and account identity — the name, email address and credentials used to create and hold an\n account;\n- billing, payments, invoices, tax records and collections;\n- support conversations, including the tickets, emails, chats and attachments themselves;\n- security, fraud prevention, abuse handling and audit logging;\n- our own websites and their analytics, our newsletters, and our marketing to prospective customers; and\n- running our business — accounting, insurance, professional advice, and defending claims.\n\nEverything in this notice about purposes, legal bases, retention, transfers and your rights applies to this\nfirst case directly, and you exercise those rights against us.\n\n### 2. Personal data a customer puts into the Service about its own people — the customer is the controller\n\nWhen an organisation subscribes to the Service and uses it to run its business, the personal data it puts\nin is **its** data. It decides what to collect, which features to switch on, why, and for how long to keep\nit. **We process that data only on that organisation's instructions.** For it, the organisation is the\ncontroller and we are the processor.\n\nThis covers the ordinary contents of a workspace — employee and contractor records, contact details,\nprojects, tasks, documents and messages. It also covers the parts that matter most, where a product\nprovides them and the customer has enabled them:\n\n- **time-tracking data** — timers, timesheets, time entries and the records behind them;\n- **activity data** — how much keyboard and mouse activity occurred in a period, idle time, and which\n applications and websites were in use;\n- **screen and media capture** — periodic screenshots and, where separately switched on, webcam stills,\n audio recordings and screen recordings.\n\n**We do not decide to collect any of this. The customer does.** We build the features, we document what\neach one captures and what each control does, and we run them exactly as the customer configures them. We\ndo not use that data for our own purposes, we do not use it to train models, and we do not look at it\nexcept where we must in order to run, secure or support the Service.\n\nWhat Ever Demand can capture, what is off by default, and which controls exist is set out in the annex\nlater in this notice.\n\n### 3. Data a customer holds about its own clients and end users — the customer is the controller\n\nWhere a customer uses the Service to serve its own clients, members, applicants, patients or website\nvisitors, that data sits in the same arrangement as case 2. The customer is the controller, we are the\nprocessor, and the customer owes those people the notice and the answers. If you have dealt with an\norganisation and want to know what it holds about you, ask that organisation.\n\n### If you are monitored at work, this part is for you\n\nWe would rather tell you directly than make you work it out from a contract you have never seen.\n\n**Your employer decides what is captured. We do not.** Screenshots, activity rates, application and website\nusage, webcam stills, audio, screen recordings — each of these is a setting your employer switches on or\nleaves off, for the organisation and, where the product allows it, for individual people. We cannot switch\nthem on for your employer, and we do not switch them on for ourselves.\n\n**Your employer is the controller of that data.** That means your employer, not us:\n\n- must have a lawful basis for monitoring you, under the GDPR and under its own national employment law,\n which differs sharply from country to country;\n- must tell you, before it starts, what is captured, how often, why, and how long it is kept;\n- must carry out a data protection impact assessment where one is required, and act on what it finds;\n- must consult a works council, employee representatives or a trade union where its national law requires\n that; and\n- must answer your requests about that data.\n\n**We make no claim that monitoring employees is lawful across the European Union, because it is not.** Some\ncountries restrict it tightly, some require consultation before it starts, and some prohibit particular\nforms of it outright. Whether your employer's use of these features is lawful where you work is your\nemployer's responsibility. We require every customer to confirm to us that it has dealt with each of the\npoints above before it uses these features.\n\n**How to exercise your rights over monitoring data.** Send your request to your employer — it holds the\ndata and it has to answer you. If you send it to us instead, we will not ignore it:\n\n- we will forward it promptly to the customer whose workspace holds the data;\n- we will tell you that we have done so, and to whom, so you are not left waiting on silence; and\n- we will help that customer find, correct, export or delete the data, which is what our contract with it\n requires of us.\n\n**What we will not do is release one organisation's data to someone else on request.** We cannot verify an\nemployment relationship from the outside, and handing over a workspace's contents to a person the customer\nhas not authorised would be a breach in its own right. That restraint protects you as much as it\nconstrains you.\n\nIf you think your employer is monitoring you unlawfully, you can complain to the data protection authority\nin your own country, and to your national labour authority. You do not need our permission, and you do not\nneed to come through us first.\n\n## Personal data we collect\n\nWe group this by where the data comes from, because that is what determines what we know about you and what\nwe owe you.\n\nNot every category applies to every product, plan or user. This section describes the shape of what we\ncollect; the annex later in this notice lists what Ever Demand actually collects.\n\n### What you give us\n\n- **Account identity** — your name, username, email address, password (held only as a hash), profile\n picture, job title, preferred language and time zone.\n- **Organisation details** — the organisation you belong to, your team, your role and permissions within\n it, and who invited you.\n- **Contact details** — email address, telephone number and postal address, where you provide them.\n- **Billing details** — billing name and address, VAT or tax identification number, the plan you are on,\n invoices and payment history. **We do not receive or hold your full card number** — that goes straight to\n our payment processor.\n- **Support correspondence** — the tickets, emails, chat messages, screenshots and files you send when you\n ask for help, and our replies.\n- **Content you submit** — everything you or your organisation puts into the Service: documents, tasks,\n projects, records, messages and uploads. Where that content belongs to your organisation, we hold it as\n processor, not as controller.\n- **Anything else you volunteer** — survey answers, feedback, event registrations, newsletter sign-ups, and\n whatever you choose to write to us.\n\n### What we collect automatically when you use the Service\n\n- **Device and browser data** — device type, operating system, browser and version, screen size, language,\n and the version of our application you are running.\n- **Connection data** — your IP address, and the approximate location it indicates. **That is\n city-or-region level, derived from the IP address**, and it is not satellite positioning. Where a\n specific feature collects precise location, it says so.\n- **Usage data** — pages and screens viewed, features used, actions taken, navigation paths, timestamps and\n the page that referred you.\n- **Logs** — server and application logs of requests, errors, response times, sign-ins, failed sign-ins and\n administrative actions, with the identifiers needed to tie an entry to an account.\n- **Diagnostics** — crash reports, stack traces and performance traces. These can incidentally contain\n whatever was in the request that failed.\n- **Cookies and similar technologies** — cookies, local storage, pixels, software development kit\n identifiers and comparable device storage. What each is for, and which ones need your consent, is in our\n [Cookie Policy](https://everdemand.co/cookies).\n\n### What we receive from other people\n\n- **Identity providers** — if you sign in with a third-party account, we receive that account's identifier,\n your email address, your display name and usually your profile picture, plus confirmation that the\n sign-in succeeded. **We never receive your password for it.**\n- **Payment processors** — whether a payment succeeded or failed, the payment method type, the last four\n digits and expiry of a card, the billing country, and any dispute or chargeback.\n- **Integrations you or your administrator connect** — whatever the connected service returns within the\n permissions granted. That varies by integration and is shown to you when you authorise it.\n- **Your organisation** — where an administrator creates your account, invites you, sets your role or\n imports records about you.\n- **Other sources**, where a particular product uses them. Those are set out in the next section and in the\n annex.\n\n### What you have to give us\n\nSome of it is unavoidable. Without account identity we cannot create an account for you; without billing\ndetails we cannot take payment for a paid plan; without certain records we cannot meet our own legal\nobligations. Where data is necessary in that sense, **not providing it means we cannot provide that part of\nthe Service** — but nothing worse follows.\n\nEverything else — an optional profile field, a newsletter subscription, an integration you could simply not\nconnect — is genuinely optional, and declining it costs you nothing.\n\n## Data we do not collect\n\nShorter than the previous section, and just as binding. These are commitments about how the Service is\nbuilt, not aspirations.\n\n- **We do not sell personal data.** Not to data brokers, not to advertisers, not to anyone — and not under\n the broader definitions of \"sell\" or \"share\" used outside the European Union.\n- **We do not buy marketing lists.** If we contact you about our products it is because you gave us your\n details, or because you are already a customer. We do not purchase your name from someone else in order\n to email you.\n- **We do not use your content to train machine-learning models** — not for our own purposes, and not for\n the benefit of other customers. Where a product has an AI feature, it processes your content to produce\n your result, and that is the end of it. If we ever want that to change, it will be an opt-in you actively\n choose, described before you choose it.\n- **We do not run advertising inside the Service.** No third-party advertising, no behavioural ad\n targeting, no cross-site advertising identifiers in the product.\n- **We do not record what you type.** Where a product measures keyboard and mouse activity, it counts\n events over a period. **There is no keylogger in our software. The content of your keystrokes is never\n captured, stored or transmitted.**\n- **We do not ask for special-category data** — health, racial or ethnic origin, religious or philosophical\n beliefs, political opinions, trade union membership, sex life or sexual orientation, genetic or biometric\n data. There are no fields for it, we do not infer it, and we do not want it. The one honest caveat is\n about what can end up inside a screenshot, and it has its own section below.\n- **We do not store full card numbers or card security codes.** Those are entered on our payment\n processor's systems and never reach ours.\n- **We do not collect precise location by default.** Where a product uses location at all, it is because a\n specific feature needs it, and that feature says so.\n\nIf you find any of this to be untrue of something we ship, tell us at privacy@ever.co. We will treat it\nas a defect in the product, not as a disagreement about wording.\n\n## Where data comes from when it does not come from you\n\nNot all of the personal data we hold came from you. Article 14 of the GDPR requires us to tell you where it\ncame from, and this section does that.\n\n- **Your employer, or the administrator of your workspace.** Where an organisation subscribes to the\n Service, an administrator creates accounts, invites people, sets roles and imports records. That supplies\n your name, work email address, job title, team, role and permissions, and whatever else the organisation\n chooses to hold about you in its workspace. **For that data the organisation is the controller**, as set\n out above.\n- **Identity providers.** If you sign in with a third-party account, that provider supplies the account\n identifier, your email address, your display name and usually a profile picture, and confirms the sign-in\n succeeded. It supplies nothing else, and never a password.\n- **Integrations you or your administrator connect.** A connected service supplies whatever the permissions\n you granted allow — for example issues and repositories from a code host, messages and channel names from\n a chat tool, calendar entries, contacts, or records from another business system. The scope is shown when\n the connection is authorised, and it can be revoked in the same place.\n- **Payment processors and resellers.** They supply the outcome of a payment, the payment method type, the\n last four digits and expiry of a card, the billing country, and any dispute or chargeback. They do not\n pass us the card itself.\n- **Publicly available sources, where a product builds profiles from them.** Some products work with\n information people have published themselves — a public code-hosting profile, a public company page, a\n public professional listing. Where a product does this, the annex names the categories taken and the\n sources they came from, explains the basis we rely on, and says how to object. **If we hold a profile\n about you that you never gave us, you can object to it and we will act on that.**\n- **Service providers acting for us.** Fraud and abuse signals, delivery and bounce information from the\n systems that send our email, and security intelligence about addresses and networks.\n\nWhere we are the controller of personal data that did not come from you, we will tell you within a\nreasonable period and at the latest within one month of obtaining it — or, if we use it to contact you, at\nthat first contact. Where informing every individual separately would take disproportionate effort, this\nnotice and its annex are the public information we provide instead, which is what Article 14(5)(b) allows.\n\n## Why we use personal data, and on what legal basis\n\nArticle 6 of the GDPR requires a lawful basis for each purpose. So this is one row per purpose, rather than\na general list of all six bases — you can check us against each line.\n\n| Purpose | Personal data used | Lawful basis |\n|---|---|---|\n| Providing Ever Demand: creating and running your account, signing you in, delivering the features you use, and keeping your data available to you | Account identity, organisation and role, credentials, content you submit, device and connection data | **Contract** — Art 6(1)(b). Necessary to perform our agreement with you |\n| Taking payment: invoicing, collecting fees, applying refunds, chasing non-payment | Billing details, plan and subscription data, invoices, payment outcomes | **Contract** — Art 6(1)(b) |\n| Keeping accounting, tax and invoicing records | Invoices, payment records, billing identity | **Legal obligation** — Art 6(1)(c), under tax and accounting law |\n| Support: answering your questions, investigating faults and reproducing problems you report | Support correspondence, account identity, logs and diagnostics, and whatever you point us at | **Contract** — Art 6(1)(b) where you are a customer. **Legitimate interests** — Art 6(1)(f) where you are not, so that we can answer anyone who writes to us |\n| Security and abuse prevention: authentication, rate limiting, bot and fraud detection, investigating misuse, protecting accounts and infrastructure | Account identity, IP address, device data, request logs, sign-in and failed sign-in records | **Legitimate interests** — Art 6(1)(f) in keeping the Service and the people who use it safe |\n| Keeping the Service running: monitoring, error tracking, debugging, capacity planning and backups | Logs, diagnostics, usage data, account identifiers | **Legitimate interests** — Art 6(1)(f) in operating a reliable service |\n| Understanding how the Service is used, so we can improve it | Usage events, feature interactions, device and browser data, aggregated statistics | **Legitimate interests** — Art 6(1)(f). **Consent** — Art 6(1)(a) wherever cookies or similar device storage are involved, as set out in our [Cookie Policy](https://everdemand.co/cookies) |\n| Marketing to people who are not yet customers: newsletters, product announcements and events | Contact details, marketing preferences, whether you opened or clicked a message | **Consent** — Art 6(1)(a), which you can withdraw at any time |\n| Marketing our own similar products to an existing customer who gave us their address during a sale, with an opt-out in every message | Contact details, the products you already have | **Legitimate interests** — Art 6(1)(f), relying on the narrow existing-customer exception in the ePrivacy rules |\n| Meeting legal obligations: responding to lawful requests from authorities, sanctions and export-control checks, statutory record-keeping, and our own data protection duties | Whatever the specific obligation requires, and no more | **Legal obligation** — Art 6(1)(c) |\n| Establishing, exercising or defending legal claims, and handling complaints, disputes, audits, insurance and corporate transactions | Account and billing records, correspondence, and the logs relevant to the matter | **Legitimate interests** — Art 6(1)(f) in protecting our legal position |\n\nTwo things this table deliberately does not cover.\n\n**Where we act as processor**, the lawful basis is not ours to pick. The customer that put the data into\nthe Service decides the purpose and must have its own basis for it. See the controller and processor\nsection above.\n\n**Where we rely on your consent**, you can withdraw it at any time, and withdrawing it is as easy as giving\nit. Withdrawing consent does not make earlier processing unlawful — it stops the processing from that point\non.\n\n## The legitimate interests we rely on\n\nWhere the table above says \"legitimate interests\", the law requires us to tell you what that interest\nactually is — not simply to name the basis and move on. For each one we have asked three questions: what is\nthe interest, is the processing genuinely necessary for it, and is it fair to you. That last question is\nthe balancing test, and we keep a written record of it.\n\n### Keeping the Service and its users secure\n\n- **The interest:** preventing unauthorised access, account takeover, fraud, spam, denial-of-service and\n abuse of the Service.\n- **Why the processing is necessary:** you cannot see an attack without looking at the traffic. Sign-in\n records, IP addresses, device data and request logs are what make an intrusion visible at all.\n- **Why it does not override your rights:** the data is limited to what security work needs, it is kept for\n a bounded period, and the benefit goes to the same accounts and the same people whose data is used. Nobody\n reasonably expects a service to be run without security logging.\n\n### Keeping the Service running\n\n- **The interest:** operating a reliable service — monitoring, error tracking, debugging, capacity planning\n and backups.\n- **Why the processing is necessary:** faults surface in logs, and a crash report is only useful if it\n records what was happening when the crash occurred.\n- **Why it does not override your rights:** it is operational data, kept for short periods, used to fix\n software rather than to form views about people, and reachable only by the staff who need it.\n\n### Understanding how the Service is used\n\n- **The interest:** knowing which features are used, where people get stuck, and what to build or fix next.\n- **Why the processing is necessary:** the alternative is guessing. Aggregate usage data is the only\n practical way to see this without interrogating every user.\n- **Why it does not override your rights:** we analyse it in aggregate rather than to make decisions about\n you individually, and wherever cookies or similar device storage are involved we ask for your consent\n instead of relying on this interest at all.\n\n### Answering people who write to us without an account\n\n- **The interest:** replying to a question from someone who is not a customer.\n- **Why the processing is necessary:** we cannot answer you without keeping your message and your address.\n- **Why it does not override your rights:** you chose to contact us, we use it only to answer, and we keep\n it no longer than the matter and any follow-up require.\n\n### Telling existing customers about our own similar products\n\n- **The interest:** letting people who already buy from us know about the products next to the one they\n bought.\n- **Why the processing is necessary:** it uses the address they gave us during that sale, and there is no\n less intrusive way to reach them.\n- **Why it does not override your rights:** it is confined to our own similar products, every message\n carries a one-click opt-out, and an opt-out is acted on immediately and permanently.\n\n### Running and protecting our business\n\n- **The interest:** accounting, audit, insurance, professional advice, complaints, disputes, enforcing our\n terms, and evaluating or completing a corporate transaction.\n- **Why the processing is necessary:** these are ordinary obligations of operating a company, and each one\n needs the records that relate to it.\n- **Why it does not override your rights:** the data is confined to the matter in hand, access is narrow,\n and a great deal of it we are required to keep in any event.\n\n### Your right to object\n\n**You can object to any processing we base on legitimate interests, at any time, by writing to\nprivacy@ever.co.** Tell us which processing, and where you can, why — your particular situation is part\nof the balance. We will stop unless we can show compelling legitimate grounds that override your interests,\nrights and freedoms, or unless we need the data to establish, exercise or defend legal claims.\n\n**If you object to direct marketing there is no balancing at all. We stop.** That right is absolute.\n\nYou can also ask us for a summary of the balancing test behind any interest listed above, and we will give\nyou one.\n\n## Special categories of data\n\nSome personal data carries extra protection under Article 9 of the GDPR: data revealing racial or ethnic\norigin, political opinions, religious or philosophical beliefs or trade union membership, and genetic data,\nbiometric data used to identify someone, data concerning health, and data about a person's sex life or\nsexual orientation. Data about criminal convictions and offences is restricted separately, under Article 10.\n\n**We do not seek any of it.** We do not ask for it at sign-up, in billing or in support. There are no\nfields for it, we do not infer it, and we do not enrich profiles with it. Please do not send it to us in a\nsupport ticket either — if you need to show us something sensitive to get help, redact it first.\n\n### The honest caveat: incidental capture\n\nWhere a customer switches on screen capture, webcam capture or audio capture, **what gets captured is\nwhatever is there**. A screenshot taken while someone has a hospital appointment email open captures health\ndata. A webcam still can show a religious head covering. An audio recording can pick up a background\nconversation that has nothing to do with work.\n\nThat is not a theoretical risk and we will not present it as one. It is a direct consequence of capturing a\nscreen or a room on a timer, and it is true of every product that does it, ours included.\n\n### Whose responsibility it is\n\n**The customer that switches these features on is the controller of what they capture**, including anything\nspecial-category that comes with it. So the customer, not us:\n\n- decides whether to enable capture at all, and has to judge whether the benefit justifies the intrusion;\n- must carry out a data protection impact assessment before starting, and act on what it finds — capture of\n this kind will normally require one;\n- must have a lawful basis, and where special-category data is realistically in scope must also satisfy\n Article 9(2), which an employee's consent rarely does on its own, because of the imbalance between\n employer and employee;\n- must configure the product to reduce that risk rather than accept it; and\n- must deal with what has been captured, including deleting a capture that should never have been taken.\n\nWe are the processor for it. We do not decide to capture anything, we do not review captures for our own\npurposes, and we act on the customer's configuration and instructions.\n\n### The levers, and using them\n\nWhere a product offers screen or media capture, it also offers controls that materially reduce this risk.\nDepending on the product, those include:\n\n- switching capture off entirely, for the whole organisation or for an individual person;\n- switching off the more intrusive capture types — webcam stills, audio and screen recording — while\n keeping the rest;\n- reducing how often captures are taken;\n- blurring captured images;\n- shortening how long captures are kept, and deleting them automatically at the end of that period;\n- letting people see what has been captured about them; and\n- deleting an individual capture.\n\n**If you are a customer, these are yours to set, and the defaults are not a recommendation.** Choose the\nleast intrusive configuration that meets the purpose you actually have, and write down why you chose it.\nThat record is what a supervisory authority will ask for.\n\n**If you are being monitored and something sensitive has been captured, ask your employer to delete it.**\nYour employer can do that in the product. If you tell us instead, we will forward your request and help\nyour employer act on it, as described in the controller and processor section above.\n\nWhich of these controls Ever Demand provides, and what its defaults are, is set out in the annex later\nin this notice.\n\n## Annex: Ever Demand\n\nThis annex describes what the Ever Demand software actually holds and what we actually do with it. It\nis written from the code, not from the product page, and where the software falls short of what a privacy\nnotice would like to promise, it says so.\n\n### Which of three situations you are in\n\nEverything else in this annex depends on this, and getting it wrong in either direction would be the single\nworst mistake in the document. **There is no hosted Ever Demand platform today.** What we operate under this\nname is a website, a documentation site and the content management system behind them.\n\n**1. Somebody runs the software themselves — the ordinary case.**\nThe business that deployed it is the controller. It chose the hosting, the database, the payment account,\nthe mapping key and every other component. **No personal data from that deployment reaches us. We are not\nits processor, we have no access to it, and nothing in this notice describes it.** If you are a shopper, a\ncourier or a merchant on a deployment somebody else runs, the business behind it is the organisation that\nowes you answers, and it is the one to ask.\n\n**2. We host an instance for you.**\nUnder the free-hosting offer in our [Terms of Service](https://everdemand.co/tos), or under an Enterprise\nengagement. Then **you are the controller** of the shopper, courier, merchant and order data, and **we are\nyour processor** for it. We are separately the controller of the narrow set of records described in the\ncontroller-and-processor section above — your administrator contacts, our correspondence with you, and our\nown security and audit logs.\n\n**3. You are visiting [everdemand.co](https://everdemand.co) or the documentation site.**\n**We are the controller.** Contact form submissions, the pricing-notification form, newsletter sign-ups,\nthe support chat, bot protection on those forms, and — after you consent — analytics. What is set on your\ndevice is in our [Cookie Policy](https://everdemand.co/cookies).\n\n### The people the platform holds data about\n\nNamed individually rather than swept into \"users\", because their positions are genuinely different:\n\n- **shoppers** — people with an account who order;\n- **prospective shoppers who have no account** — someone who submitted an invite request and is waiting for\n a store to approve it;\n- **couriers** — enrolled by an administrator, never by self-registration;\n- **merchant and warehouse staff** — likewise enrolled by an administrator;\n- **platform administrators** — who can see every shopper, courier, merchant and order, and the live map;\n- **delivery recipients who did not place the order** — the person at the address, where a shopper has\n ordered to somebody else's home.\n\n### What the platform holds\n\n| Category | What is in it |\n|---|---|\n| Identity | First and last name, and a profile or logo image address |\n| Contact | Email address and telephone number, for shoppers, couriers and merchant contacts, including a merchant's separate orders mailbox and orders telephone number |\n| Credentials | A hashed password, session and access tokens |\n| Social identity | The account identifier returned by Google or Facebook, where the operator has enabled social sign-in |\n| Delivery location | Country, city, street, house, apartment, postcode, a free-text notes field, and a precise geographic point held for map and proximity searching |\n| Courier position | The courier's current device position while on duty — see the next section, which is the important one |\n| Courier work data | Online or offline status, lifetime deliveries, deliveries today, distance travelled today, orders skipped, and an administrator-controlled flag that switches an account off |\n| Orders | Basket contents, prices, order number, whether it is delivery or collection, and the full timestamp chain from placement through to completion, plus which courier and which warehouse handled it |\n| The order snapshot | A copy of the ordering shopper written into the order itself — see the limitations section below |\n| Payment identifiers | The payment provider's customer and charge identifiers, and card metadata such as brand, last four digits and expiry. Full card numbers go to the payment provider and are not held by the platform |\n| Devices | Device identifier, platform, language, and the push notification channel identifier |\n| Merchant gateway credentials | The payment keys a merchant configures for its own store, held in the platform database — see the limitations section |\n| Logs | Application and service logs, which contain identifiers and can contain fragments of a request |\n\nThe free-text delivery **notes** field deserves a separate mention: it is unstructured and unvalidated, and\npeople write whatever helps a courier find them. Some of what ends up there is far more personal than the\naddress itself.\n\n### Courier location — exactly what happens\n\nVagueness here reads as concealment, so this is precise.\n\n- **While the courier's own status is set to Online, the courier application reads the device's position\n approximately every three seconds and sends it to the server.**\n- **While the courier's status is Offline, nothing is read.** The application does not sample position, and\n there is no background collection when the courier is off duty. That gate is in the courier's own hands\n and it is the strongest design fact in this product.\n- **The stored value is the current position, overwritten by the next reading.** The platform does not build\n a location history table.\n- **The position is shown to platform administrators, to the merchant, and to the shopper who placed the\n order**, inside the shopping application, while the delivery is running.\n\nThat last point is the one that matters most and the one operators most often fail to disclose. **A\ncourier's live position being visible to a member of the public is a materially different thing from a\ndispatcher watching a fleet map**, and a courier is entitled to be told about it before it starts, not\nafter.\n\nWhere we host an instance, **we do not decide any of this**. The operator decides whether to run the\ncourier application at all, who may see the map, and whether the ordering shopper sees the courier. Our\n[Data Processing Addendum](https://everdemand.co/dpa) treats courier position and courier work data as monitoring\ndata and puts the corresponding obligations on the operator in binding terms.\n\n### Courier work data\n\nAlongside position, the platform accumulates counters about the person doing the work: **lifetime\ndeliveries, deliveries completed today, distance travelled today, orders skipped, and the record of going\nonline and offline.** There is also an administrator-controlled flag that switches a courier's account off\nentirely.\n\nThese are performance measures. They are not a by-product of dispatch — an employer can read them as a\nproductivity score, and some will.\n\n**Our position on them is deliberate rather than accidental.** Where we host an instance, we compute and\nstore these counters on the operator's instruction and for no purpose of our own. We do not benchmark\ncouriers, we do not compare them across operators, we do not build or sell an industry dataset from them,\nand we do not use them to train anything. **If we ever derived anything from them for a purpose of our own,\nwe would become a controller of that, and we would say so here before we did it.**\n\n### If you are a courier\n\nYou will not have signed up for this, so it is worth reading.\n\n- Your position is read only while **you** have set your status to Online. Setting it to Offline stops it.\n Nothing is read from your device when you are off duty.\n- While you are on a delivery, **the customer waiting for it can see where you are**, as well as your\n dispatcher and the store.\n- The application also counts your deliveries, the distance you have covered today and the orders you have\n skipped, and the business that gave you the account can see all of it.\n- **The business that gave you the account decides all of this, and holds the data.** Ask them what they\n collect, why, how long they keep it, and who sees it. If we host their instance, we will help them answer\n you — the section on your rights above explains how we route a request that comes to us instead.\n\n### People who never signed up\n\nThree groups end up in the platform without ever agreeing to anything, and **the obligation to tell them\nsits with the operator of the deployment, not with us**:\n\n- **Invite requesters.** A person with no account submits a street address, house, apartment, postcode and a\n device identifier, and that record waits in a store's console for approval. That is a residential address\n held about somebody with no account and no relationship with anyone but the store.\n- **Couriers and merchant staff.** The account is created by an administrator before the worker's first\n contact with the software.\n- **Delivery recipients who did not order.** A shopper can send an order to somebody else's home, and the\n address, apartment number and delivery notes are then visible to the store, the courier and the\n administrators.\n\nWhere we host an instance, our [Data Processing Addendum](https://everdemand.co/dpa) requires the operator to give\nthose people the notice the law requires. **We cannot give it for them: we do not know who these people are,\nand in most cases we have no way to reach them.**\n\n### Three limitations we are not going to hide\n\nOverstating what our software can do would be its own misrepresentation, so here is what it cannot.\n\n- **Records are marked deleted, not erased.** Every record carries a deleted flag, and there is no hard\n erasure path anywhere in the service layer. Marking something deleted removes it from the application; it\n does not remove it from the database.\n- **Every order carries a copy of the shopper.** When an order is created, the shopper's name, email\n address, image, delivery location and apartment are copied into the order document — and in the published\n code, so is the stored password hash. **Deleting or changing the shopper's own record does not reach those\n copies.** Anyone running a deployment should treat the order snapshot as containing authentication\n material and remove it.\n- **Payment material reaches the logs, and merchant keys sit in the database.** The payment-method handler\n writes the payment provider's token and card object into the application log at information level, and the\n payment keys a merchant configures for its own store — including the secret one — are held in the platform\n database and are readable from the administration console.\n\n**We will not host an instance for anyone until the credential copy and the payment logging are fixed in the\ncode we would be running.** For a deployment you run, all three are yours to deal with, and the\n[Security page](https://everdemand.co/security) sets out what to do about them.\n\n### How long data is kept\n\n**The platform ships no automatic retention or deletion routine.** Records persist until somebody removes\nthem. There is one genuine exception, and it works in your favour: **courier position is a single current\nvalue that the next reading overwrites**, so no position history accumulates.\n\nIn a deployment you run, retention is something you have to implement and describe — it is not something the\nsoftware does for you, and saying otherwise in your own privacy notice would be inaccurate. Where we host an\ninstance, you set the periods, we apply them, and we will tell you honestly which records our tooling can\nreach and which it cannot.\n\nThe retention section above covers what we hold as controller for our own website and our own\ncorrespondence, which is a different and much smaller set of data.\n\n### Automated decisions inside the platform\n\nThree mechanisms are worth naming: orders are allocated to couriers, a courier can skip an order and that is\nrecorded, and a store owner approves or refuses an invite request. **All three are the operator's\nconfiguration and the operator's decision-making, not ours.** We do not rank or score couriers, and we do\nnot operate any allocation logic of our own.\n\nIf an operator uses the work counters to make a decision about a courier that produces legal effects or\nsimilarly significantly affects them, that is the operator's processing to justify, and the courier's rights\nin relation to it run against the operator.\n\n### If a deployment shows you a privacy page\n\nThe software bundles its own privacy and terms pages, which a deployment serves to its own users. **Those\npages describe that deployment, and the business running it is responsible for their content.** If a page\nserved by a deployment we do not run names any Ever company as the controller of that deployment, it is\nwrong — the controller is the business that deployed the software, and that is who you should contact.\n\n### Our website\n\nOn [everdemand.co](https://everdemand.co) and the documentation site we hold what you send us through the\ncontact form, the pricing-notification form, the newsletter sign-up and the support chat — a name, an email\naddress, an organisation and whatever you write — together with the ordinary connection and usage data\ndescribed above. **We are the controller for all of it.** What is stored on your device, what waits for your\nconsent, and who the providers are is in our [Cookie Policy](https://everdemand.co/cookies).\n\n## Cookies and similar technologies\n\nCookies, local storage, pixels, software development kits and similar technologies get their own document,\nbecause they need more detail than a summary can carry. What each one is, what it does, how long it lasts,\nwho operates it and how to refuse it is set out in our [Cookie Policy](https://everdemand.co/cookies).\n\nIn short, we sort them into four categories:\n\n- **Strictly necessary** — needed to deliver what you asked for: signing you in, holding your session,\n routing traffic, remembering your cookie choice itself, and protecting forms and sign-in against\n automated abuse. These are not optional, and we do not ask for consent to them.\n- **Preferences** — remember choices you have made, such as language, region and interface settings.\n- **Analytics** — help us understand how the Service is used so we can improve it.\n- **Marketing** — measure our campaigns and help us understand which organisations take an interest in us.\n\n**Nothing in the preferences, analytics or marketing categories is placed or read on your device until you\nagree to it.** You can accept everything, refuse everything, or choose category by category, and refusing\ntakes exactly as few clicks as accepting.\n\n### Changing your mind\n\nYour choices are not permanent. A **Cookie preferences** link sits in the footer of every page on\n[everdemand.co](https://everdemand.co) and reopens the same panel you saw the first time. Change a category\nthere and it takes effect immediately, for the future. Withdrawing is as easy as agreeing, and nothing\nabout the Service is withheld from you for refusing.\n\nOne analytics tool runs without consent, because it is configured so that it stores and reads nothing on\nyour device and never builds a persistent identifier for you. That is a conditional position, not a\npermanent one: the [Cookie Policy](https://everdemand.co/cookies) names the tool, describes the exact\nconfiguration we rely on, and says what happens if any part of that configuration ever changes.\n\n## Who receives your personal data\n\nWe disclose personal data only to the categories of recipient below, and only as much as each one needs to\ndo the job it is there for.\n\n- **Service providers acting as our processors** — hosting and infrastructure, storage, content delivery,\n email delivery, error monitoring, product analytics, customer support tooling and similar. They act on\n our documented instructions under a written contract that meets Article 28 GDPR, they are bound to\n confidentiality and appropriate security, and **they may not use your data for their own purposes**.\n- **Payment processors** — to take payment, issue invoices and handle refunds and disputes. For their own\n regulated obligations — fraud prevention, anti-money-laundering, card-scheme rules — they act as\n controllers in their own right, and their own privacy notice governs that part.\n- **Professional advisers** — lawyers, accountants, auditors and insurers, bound by professional\n confidentiality, where we need advice or have to evidence that we have complied with something.\n- **Public authorities, courts and regulators** — where the law requires us to disclose, or where we need\n to establish, exercise or defend a legal claim. We check that a request has a proper legal basis and is\n no wider than it needs to be, we push back where it is not, and we tell you about it unless we are\n legally prohibited from doing so.\n- **An acquirer or successor** — if we are reorganised, merged or sold, or if part of the business changes\n hands, personal data may pass to the acquirer as part of that transaction. The acquirer is bound by this\n policy or by a notice at least as protective, and we will tell you before anything about the handling of\n your data changes.\n\n### The sub-processors we engage for the hosted Service\n\nThese providers are engaged for the hosted Service as it is delivered to everyone. They are the ones your\ndata is most likely to reach.\n\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| Cloudflare, Inc. | Authoritative DNS, TLS termination, reverse proxy and bot filtering in front of everdemand.co, docs.everdemand.co and the content management system behind the website, and the tunnel that carries requests to our own servers. | United States, with the connection terminated at the edge location nearest to the visitor | Standard Contractual Clauses (EU 2021/914) | IP address, request URL, headers and TLS metadata, cookies in transit |\n| Functional Software, Inc. d/b/a Sentry | Error and performance monitoring for the website, the documentation site and the content management system, so that a failure is visible to us with enough context to fix it. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, browser and device, page or route being viewed, request context and breadcrumbs, which can contain fragments of what was submitted |\n| iubenda s.r.l. | Cookie banner and consent record on everdemand.co — it displays the choice, applies it, and stores the proof of what you chose. | Italy | None needed — established in the EEA | IP address, consent choices and the record of them, timestamp and user agent |\n| Google Ireland Limited (reCAPTCHA) | Bot protection on the public forms — contact, pricing notification and newsletter sign-up. It loads only on a page carrying a protected form. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, browser and device signals, mouse and interaction telemetry |\n| GitHub, Inc. (a Microsoft Corporation company) | Source hosting, build pipeline and container registry for the website, the documentation site and the published source code. This is how the site is built and shipped, not where visitor data lives. | United States | Standard Contractual Clauses (EU 2021/914) | contributor account names and public profile data, developer identity in build logs |\n| Cloudflare, Inc. (R2 object storage) | Holds the encrypted off-site copy of our backups - Postgres WAL and dumps, Velero, etcd, Proxmox configuration and MinIO mirrors - as the third tier of the backup chain (node8 NVMe, then Ceph RGW, then Cloudflare R2). Encrypted by us before it leaves our network. | United States | Standard Contractual Clauses (EU 2021/914) | client-side encrypted backup archives only - no plaintext is ever readable by the provider, the archives themselves derive from every category of data the products hold |\n| Google Ireland Limited (Google Workspace) | Hosts the corporate mailboxes that receive every support, privacy and rights request our own documents tell data subjects to write to, plus the recruitment mailbox that holds candidate CVs. | Ireland (contracting) / United States and global (Google LLC) | Standard Contractual Clauses (EU 2021/914) | all inbound and outbound company email, support, DSAR and privacy correspondence with data subjects, candidate CVs and application correspondence (ever-tech careers), customer and supplier correspondence and attachments |\n| Cloudflare, Inc. (Turnstile) | Checks that the person completing registration, onboarding or an anonymous flow is not a bot; on ever-works the API refuses the anonymous flow when no CAPTCHA provider is configured, which is why it is unconditional there. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, user agent and device signals, mouse, touch and timing interaction signals, Turnstile challenge cookie |\n| Clerk, Inc. | Holds the account identity for the hosted cloc platform - name, email address, avatar, password or federated identity, sessions and multi-factor settings - so that our own database does not, and brokers the short-lived source-control credential used when the Service acts in a user's name. | United States | Standard Contractual Clauses (EU 2021/914) | name, email address and avatar, password hash or federated identity, session, device and sign-in records, organisation membership and role, social-connection claims where a user signs in that way, the short-lived source-control credential brokered for a single request and not stored |\n| Tavily | The default provider for public web search and page extraction, used by agents researching a topic and by the automated research that runs when an account is created, where the queries are built from the new account holder's name and email domain. | United States | To be confirmed — we do not yet evidence a mechanism | search queries, including a person's name and their employer's email domain, the addresses of pages retrieved and the extracted page content, our API key and request metadata |\n| ui-avatars.com | Generates placeholder avatars where a person has no avatar of their own. The person's name or GitHub username is placed in the image URL, so it is disclosed to this provider every time the image is rendered in a customer's browser. | UNKNOWN - not published by the provider | To be confirmed — we do not yet evidence a mechanism | the developer's name or GitHub username, in the request URL, the viewing user's IP address and user agent |\n| Prospect One sp. z o.o. (jsDelivr) | Serves the Lottie animation runtime hard-coded into the ever-works login and register pages, so every person who opens the login page hands their IP to it before authenticating. | Poland (operator); delivery worldwide | Standard Contractual Clauses (EU 2021/914) | IP address, user agent, referring page URL |\n| UNKNOWN - community-run npm CDN; no obtainable DPA counterparty identified | Second permitted origin for the Lottie animation runtime on the ever-works login and register pages. | United States (unverified) | To be confirmed — we do not yet evidence a mechanism | IP address, user agent, referring page URL |\n| Resend, Inc. | Sends transactional mail for the products and domains configured against it, relaying onward through Amazon SES. | United States | Standard Contractual Clauses (EU 2021/914) | recipient name and email address, message subject and body, delivery and bounce metadata |\n| Langfuse GmbH | Stores the full prompts and completions of AI features together with model, latency and cost metadata, so that agent behaviour can be traced and scored. | Germany | None needed — established in the EEA | full prompt and completion text, which can contain user-authored content and personal data, user and session identifiers, model, latency, token and cost metadata, developer scoring outputs |\n| OpenRouter, Inc. | Is the model provider behind the default 'Ever Works AI' option and the hard-coded default for AI Chat on every provisioned tenant site, receiving the raw prompt and forwarding it to whichever upstream model the selected model id resolves to. | United States | To be confirmed — we do not yet evidence a mechanism | full prompt text, including any customer or end-user content pasted into an agent - repo text, CVs, job descriptions, chat messages, generated completions, agent tool-call arguments, API key metadata and usage accounting |\n| Chargebee, Inc. - VERIFY; Chargebee Europe BV (Netherlands) is the EEA entity if it is the one contracting. | Handles subscription billing and invoicing for the hosted Gauzy service. | United States / Netherlands | To be confirmed — we do not yet evidence a mechanism | billing identity and address, plan, invoice and payment history |\n| Shopify International Limited | Runs the storefront and order pipeline for the shop product, holding customer, order and payment-status records. | Ireland (contracting) / Canada and United States (Shopify group) | Standard Contractual Clauses (EU 2021/914) | customer name, email address and shipping address, order and payment status, browsing and cart events on the storefront, cookies set by the storefront |\n\nThe full and current list, including everything below, is published at\n[https://everdemand.co/subprocessors](https://everdemand.co/subprocessors), together with the notice period and\nobjection procedure that apply when we add or replace one.\n\n### Three tiers, and why the difference matters\n\nA single flat list of every vendor that appears anywhere in our software would be both inaccurate and\nmisleading, so the sub-processor page is split into three tiers. They mean genuinely different things.\n\n- **Always engaged.** The providers above. If you use the hosted Service, these are in the path.\n- **Engaged only if you turn something on.** Optional integrations, connectors and features. A provider in\n this tier is engaged only when you or your workspace administrator enables the specific feature or\n connects the specific account it belongs to. Enable nothing and it is never involved. The list says which\n feature or setting activates each one.\n- **Self-hosted deployments only.** Several of our products are published as open source and can be run on\n your own infrastructure. In that case **you** choose the database, object storage, email relay, AI\n provider and everything else, using your own credentials. Those providers appear in the list so you can\n see what the software can be pointed at — but they are **your** providers, not ours. **We process nothing\n in a deployment you run, we are not your processor for it, and the commitments in this policy do not\n describe it.**\n\n### We do not sell your personal data\n\nWe do not sell personal data, and we do not share it for cross-context behavioural advertising. We do not\nsupply it to data brokers, we do not trade it for services, and we do not permit any provider we engage to\nuse it to build advertising or interest profiles, on our sites or anywhere else.\n\n## Sending personal data outside the EEA\n\nMost of the personal data we hold stays inside the European Economic Area, on infrastructure we operate\nourselves. Some of it does not: a number of the providers we engage are established outside the EEA —\nprincipally in the United States — and some of them route, cache or store data on servers outside it.\n\nWhere that happens, the transfer needs a lawful mechanism under Chapter V GDPR. We use one of the\nfollowing for every transfer, and the sub-processor page names the destination country and the mechanism\nprovider by provider.\n\n### Adequacy\n\nWhere the European Commission has decided that a country provides an adequate level of protection, the\ntransfer relies on that decision and needs nothing further. Adequacy decisions are kept under review by\nthe Commission and can be amended, suspended or repealed, so we monitor them rather than treat them as\npermanent.\n\n### Providers in the United States\n\nFor a US provider we rely on one of two things.\n\n- **The EU–US Data Privacy Framework**, but only where that provider is *actively self-certified* under it\n for the type of data concerned. We check the official Data Privacy Framework list when we engage a\n provider and re-check it periodically. **We do not claim the Framework for a provider that has not\n certified, or whose certification has lapsed.**\n- **Standard Contractual Clauses** — the clauses approved by the European Commission in Implementing\n Decision (EU) 2021/914, with the modules that match the relationship, together with a transfer impact\n assessment and supplementary measures: encryption in transit and at rest, minimising what is sent in the\n first place, contractual limits on onward disclosure, and a commitment from the provider to notify and\n where possible challenge a government access request.\n\n**We keep Standard Contractual Clauses in place as the standing mechanism**, including for providers that\nare also certified under the Framework. That is deliberate, and here is the honest reason.\n\nThe Commission's adequacy decision for the Framework, adopted on 10 July 2023, is currently valid. It was\nchallenged, and on 3 September 2025 the General Court of the European Union dismissed that challenge in\n*Latombe* (Case T-553/23). **That is not the end of it** — an appeal is pending before the Court of\nJustice as Case C-703/25 P, and the two arrangements that preceded this one were each struck down by the\nsame court. So we treat the Framework as a mechanism under review rather than a settled answer, and we\nkeep a second mechanism standing behind it so that a change in the law is a paperwork event for us and not\nan interruption for you.\n\n### Other countries\n\nFor a transfer to any other country without an adequacy decision, we use Standard Contractual Clauses with\nthe same assessment and supplementary measures. Where a transfer is to the United Kingdom or Switzerland,\nthe corresponding UK and Swiss additions are applied to those clauses.\n\nWe rely on an Article 49 derogation — for example, a transfer that is strictly necessary to perform a\ncontract you have asked us to perform — only in a specific, occasional case where no other mechanism fits.\nIt is not a routine mechanism for us, and we do not use it to run a regular data flow.\n\n### Getting a copy of the safeguards\n\nYou are entitled to see the safeguards we rely on. Write to privacy@ever.co naming the provider or the\ntransfer you are asking about, and we will send you a copy of the relevant clauses and tell you which\nmodules apply. We may redact commercial terms such as pricing and service levels; we do not redact the\ndata protection terms, which are the part that concerns you.\n\n## How long we keep personal data\n\n\"As long as necessary\" is not an answer, so here are the actual periods. Each one runs from the event in\nthe middle column, and at the end of it we delete the data or irreversibly anonymise it.\n\n| What we hold | How long we keep it | Why that period |\n|---|---|---|\n| Account and profile data — name, email address, workspace membership, settings | For as long as the account is open, then deleted within **30 days** of closure | We need it to give you the account; after that we do not |\n| Content and files you put into the Service | For as long as the account is open; after it ends, available for export for **30 days**, then deleted | You decide what is in it — see below |\n| Invoices, payment records and the tax data attached to them | **10 years** from the end of the accounting year in which the transaction fell | Accounting and tax law in Bulgaria requires it, and we cannot shorten it at your request |\n| Record that you accepted our terms — version, date, method | **5 years** after the agreement ends | The general limitation period for a claim under the contract |\n| Support correspondence and tickets | **24 months** from the last message in the thread | Long enough to handle a recurring problem and a follow-up; not longer |\n| Security, access and audit logs | **12 months** | Investigating unauthorised access, and evidencing that we did |\n| Application and error logs, crash reports, diagnostics | **90 days** | Fixing what broke; they lose value quickly |\n| Marketing contact records and the evidence of your consent | Until you object or withdraw. We then remove you from the lists and keep only a suppression record — your email address and the date — so that we do not contact you again | An unsubscribe that forgets you is not an unsubscribe |\n| Cookie and consent choices | As stated in the [Cookie Policy](https://everdemand.co/cookies), which gives the lifetime of each entry | It belongs with the technology it describes |\n| Backups | Each backup ages out on its own rolling cycle, within **30 days** | Recovering from failure and ransomware, without becoming a second archive |\n| Anything we are required to preserve for a legal claim, investigation or regulatory request | Until the claim, investigation or request ends, including any appeal period | We are not allowed to delete evidence, and neither are you |\n\n### Data that belongs to one of our customers\n\nFor personal data held inside a customer's workspace — including anything the Service captures about that\ncustomer's own personnel — **the customer sets the retention period, not us**. We are their processor for\nit. The defaults and the limits of what they can configure are described in the product annex to this\npolicy.\n\nWe delete that data when the customer instructs us to, or at the end of the export window after their\nagreement ends, whichever comes first. If you are one of their people and you want their data about you\ndeleted sooner, ask them — see the section on your rights, which explains how we route that.\n\n### What \"delete\" means here\n\nDeletion is applied to live systems straight away. Backup copies are not individually edited — doing so\nwould defeat what a backup is for — so a deleted record persists in backups until that backup ages out on\nthe cycle above, at most 30 days. During that window the data is not used for anything, and **we do not\nrestore a backup to bring back data someone asked us to delete**; a backup is restored only to recover a\nwhole system after a failure.\n\nWhere we can keep something useful without keeping you identifiable, we anonymise instead of deleting —\naggregate usage counts, for example. Once anonymised the data is no longer personal data, and it is not\npossible for us to re-identify you from it.\n\n## How we protect personal data\n\nWe take the measures Article 32 GDPR requires: technical and organisational safeguards appropriate to the\nrisk, reviewed as the risk changes. In practice that means the following.\n\n- **Encryption in transit.** Traffic to and from the Service travels over TLS. HTTPS is enforced, and\n plain HTTP requests are redirected rather than served.\n- **Encryption at rest.** The storage holding customer content, databases and backups is encrypted at\n rest, and particularly sensitive values — credentials, tokens and keys — are additionally encrypted at\n the application layer rather than stored in readable form.\n- **Access control and least privilege.** Access to production systems is limited to the people whose job\n needs it, granted by named individual accounts rather than shared logins, protected by multi-factor\n authentication, scoped to the narrowest role that works, and reviewed and revoked when a role changes or\n someone leaves.\n- **Network segmentation.** Databases, storage and internal services sit on segmented internal networks\n and are not exposed to the public internet. Administrative interfaces are not publicly reachable.\n- **Logging.** Administrative and security-relevant events are logged, retained for the period in the\n retention section, and monitored so that unusual activity raises an alert rather than sitting unread.\n- **Backups.** Data is backed up regularly, held on separate infrastructure from the live systems, and\n restores are tested — an untested backup is a guess, not a control.\n- **Vulnerability management.** Dependencies are scanned, code is analysed automatically before it ships,\n security patches are applied on a defined schedule with a faster path for serious issues, and we operate\n a responsible disclosure route so that anyone who finds a problem can tell us.\n- **Personnel.** Everyone with access is bound by written confidentiality obligations that outlast their\n engagement, works on a need-to-know basis, and has access removed when it is no longer needed.\n- **Providers.** We assess a provider before we engage it, contract with it under Article 28 GDPR, and\n hold it to security obligations at least as strict as our own.\n\nOur [Security page](https://everdemand.co/security) sets out the detail, including which measure applies to\nwhich part of the Service, our incident response process, and the shared responsibility split between what\nwe secure and what you secure.\n\n### What we do not claim\n\n**We do not hold a SOC 2 report and we are not certified to ISO/IEC 27001, and we do not claim either.**\nIf anything you read or are told suggests otherwise, it is wrong, and we would like to know where it came\nfrom. Where we describe a practice on this page or on the Security page, we describe something we actually\ndo; where we adopt a framework as a reference without being audited against it, we say so plainly rather\nthan implying a certification.\n\n### No system is perfectly secure\n\n**No service, ours included, can be made completely secure, and anyone who tells you otherwise is\nselling something.** What we can honestly promise is that we take the measures above seriously, that we\nkeep them under review, and that if a personal data breach affects you we will act on it: we notify the\nCPDP where the law requires it, within the deadline it sets, and we\ntell affected people directly without undue delay where the breach is likely to result in a high risk to\nthem.\n\nYour part matters too. Use a strong and unique password, turn on multi-factor authentication where it is\noffered, keep your devices patched, and do not share credentials or access tokens. If you think an account\nhas been compromised, tell us at privacy@ever.co immediately.\n\n## Your rights over your personal data\n\nWhere we are the controller, the GDPR gives you the rights below. They are yours to use, you do not have\nto explain why you are using them, and using one costs you nothing.\n\n- **Access** — ask whether we hold personal data about you and, if we do, get a copy of it together with\n the information in this policy about how it is used. (Article 15)\n- **Rectification** — have inaccurate data corrected and incomplete data completed. Much of this you can\n do yourself in your account settings, which is faster than asking us. (Article 16)\n- **Erasure** — have data deleted where we no longer need it for the purpose we collected it for, where\n you withdraw the consent it rested on, or where we have processed it unlawfully. (Article 17)\n- **Restriction** — have us pause processing while a dispute is sorted out: while we check an accuracy\n challenge, for example, or while we consider an objection. We keep the data but stop using it.\n (Article 18)\n- **Portability** — receive the data you gave us, in a structured, commonly used, machine-readable format,\n and have it sent to another provider where that is technically feasible. This applies to data processed\n by automated means on the basis of your consent or a contract with you. (Article 20)\n- **Objection** — object to processing we base on our legitimate interests. We then stop unless we can\n demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or unless\n we need the data for a legal claim. (Article 21(1))\n- **Objection to direct marketing** — **absolute, and there is nothing to weigh.** If you tell us to stop\n using your data for direct marketing, including any profiling connected to it, we stop. No balancing\n test, no grace period, no exceptions. (Article 21(2))\n\nYou also have the right to withdraw consent where consent is what we rely on, which has its own section\nbelow, and the right to complain to a supervisory authority, which has the section after that.\n\nSome of these rights have limits written into the law itself. Erasure does not override an obligation to\nkeep invoices for the statutory accounting period, and portability does not extend to data we inferred or\ngenerated rather than received from you. **Where we cannot do all of what you ask, we will tell you which\npart we cannot do and why**, rather than declining as a whole.\n\n### How to make a request\n\nWrite to privacy@ever.co. Tell us which right you are using and enough about yourself for us to find\nthe right records — the email address on the account is usually enough. You can also write to us by post\nat the address at the end of this policy.\n\n- **It is free.** We charge nothing for a request. If a request is manifestly unfounded or excessive,\n particularly because it repeats one we have already answered, the law lets us charge a reasonable fee\n based on our administrative cost or refuse it. If we ever do either, we will explain why and tell you\n how to challenge that decision.\n- **We answer within one month** of receiving the request. Where a request is complex, or where you have\n made several, we may extend that by up to two further months — and if we do, **we will tell you within\n the first month, and tell you why**.\n- **We check who you are** before we hand over personal data, because the alternative is handing your data\n to someone who claims to be you. We ask for the least that makes us confident, usually a reply from the\n email address already on the account. We ask for an identity document only where nothing lighter works,\n and anything you send us for verification is used for that and nothing else, then deleted.\n\n### If your data sits in a customer's workspace\n\n**This is the most important paragraph on this page for many of the people who read it.**\n\nA large part of the personal data in the Service was put there by one of our customers — your employer,\nthe organisation whose workspace you belong to, or the operator of a site built on our platform. Where the\nService captures data about how an organisation's own personnel work, that data belongs to that\norganisation's workspace.\n\n**For that data the customer is the controller and we are only their processor.** We process it on their\ndocumented instructions and for no purpose of our own, so the law directs your request to them, not to us.\nPractically:\n\n- **Send your request to that organisation.** They decide it, and they are the ones who have to answer you\n within the deadline.\n- **If you send it to us instead, we will not ignore it.** We will forward it to the relevant customer\n promptly, tell you that we have done so, and assist them in answering it as our Data Processing Addendum\n requires.\n- **We will not decide the request ourselves, and we will not delete, correct or hand over data from a\n customer's workspace without their instruction** — unless a law that applies to us requires it. That is\n not us being unhelpful: acting on a workspace's data without the controller's instruction is precisely\n what a processor is not allowed to do.\n\nIf you are not sure which of the two situations you are in, ask us at privacy@ever.co and we will tell\nyou, and point you to the right organisation if it is not us.\n\n## Withdrawing your consent\n\nWhere we rely on your consent for something, **you can withdraw it at any time, and withdrawing is as easy\nas giving it**. You do not have to give a reason, and we do not ask you to justify it.\n\nWithdrawing consent stops the processing from that point onwards. **It does not make what we did before\nunlawful** — processing carried out while your consent was in force stays lawful, and withdrawal does not\nundo it. What it does mean is that we stop, and that we do not start again unless you tell us to.\n\n### How to withdraw, purpose by purpose\n\n- **Cookies and similar technologies** — open the **Cookie preferences** link in the footer of any page on\n [everdemand.co](https://everdemand.co), turn off the categories you no longer want, and save. The change\n takes effect immediately. Details are in our [Cookie Policy](https://everdemand.co/cookies).\n- **Marketing emails** — use the unsubscribe link at the bottom of any message we send you, or write to\n privacy@ever.co and ask us to stop. Either route works, and the unsubscribe link does not require\n you to sign in or find your password first.\n- **Optional features and integrations you switched on** — turn the feature off, or disconnect the\n connected account, in your settings. If you cannot find the switch, ask us at privacy@ever.co and we\n will turn it off for you.\n\nIf you have consented to something not listed here, write to privacy@ever.co naming it, and we will\nact on it the same way.\n\n### What happens next\n\nWe stop the processing, and we remove you from the relevant list or turn the relevant feature off. We keep\nthe minimum record needed to show that you consented and that you withdrew, because being able to evidence\nconsent is itself a legal requirement — for how long, see the retention section.\n\n**We will not quietly move the same processing onto a different legal basis to keep it running.** If some\npart of what you asked us to stop genuinely rests on another basis as well — an invoice we are required to\nkeep, for example — we will tell you which part and why, rather than leaving you to discover it.\n\nMost of what we do is not based on consent at all. It rests on performing our contract with you, on legal\nobligations, or on legitimate interests. **Withdrawing consent therefore does not close your account or\nswitch off the Service** — it affects only the things you consented to.\n\n## Complaining to a supervisory authority\n\nIf you think we have handled your personal data badly or unlawfully, **you have the right to complain to a\ndata protection supervisory authority**. That right is yours regardless of anything else in this policy.\n\nWe would like the chance to put it right first. Write to privacy@ever.co, tell us what went wrong, and\nwe will look into it and come back to you. In most cases that is the quickest way to get the outcome you\nactually want. **You are not required to do this, and it is not a condition of complaining** — you can go\nstraight to an authority, and you can do it at any point, including while we are still dealing with your\ncomplaint.\n\n### Our lead supervisory authority\n\nWe are established in Bulgaria, so our lead authority is the\n**Commission for Personal Data Protection (Комисия за защита на личните данни)** — the CPDP. Its website,\nincluding its complaint form and current contact details, is at\n[https://www.cpdp.bg/](https://www.cpdp.bg/).\n\n### You can also complain closer to home\n\nUnder Article 77 GDPR you may lodge your complaint with the supervisory authority in the EU or EEA country:\n\n- where you live;\n- where you work; or\n- where the thing you are complaining about took place.\n\nYou do not have to use ours, and you do not need our agreement to use another one. If you complain to your\nlocal authority, it will co-operate with ours through the mechanism the GDPR sets up for exactly this\nsituation, so nothing is lost by choosing whichever is easiest for you.\n\nYou also have the right to an effective judicial remedy — against a supervisory authority's decision, and\nagainst us directly — in the courts of the country where you live or where we are established. Complaining\nto an authority does not use up that right.\n\n## Automated decision-making and profiling\n\n**We do not make decisions about you that produce legal effects concerning you, or that similarly\nsignificantly affect you, based solely on automated processing.** No algorithm of ours decides whether you\nare hired, paid, promoted, disciplined, dismissed, given credit, or charged a different price. Where a\ndecision of that kind is made about you by an organisation using the Service, a person at that\norganisation makes it.\n\nWe do use automated rules to detect fraud, spam, abuse and attacks against the Service — rate limits,\nanomaly detection, and similar. Those rules can block a request or temporarily restrict an account. If one\nof them affects you, write to privacy@ever.co and a person will review it.\n\n### Where a customer turns on AI features, be aware of this\n\nThis is the part worth reading carefully, because it is easy to misunderstand.\n\nSome of our products capture activity data on behalf of a customer — an employer, typically — and some of\nthem offer optional AI features on top of it. **Where a customer enables those features, the Service can\ngenerate automated assessments of the activity it captures.** The clearest example: classifying whether\nthe content of a captured screen appears to be work-related. Other examples include scoring or summarising\ncaptured activity and grouping it into categories.\n\nFour things follow, and we would rather state them plainly than let them be discovered later.\n\n- **The output goes to the customer, not to us.** It is presented to the organisation whose workspace the\n data belongs to. **That organisation is the controller of it, and we are only its processor.**\n- **The customer decides what, if anything, to do with it.** We do not act on these assessments, we do not\n use them for any purpose of our own, and we do not share them with anyone else.\n- **These outputs are not decisions, and must not be used as if they were.** An automated assessment is an\n input to a human judgement. **Our terms require the customer not to treat an output of the Service as an\n automated decision about a person, and to apply meaningful human review before acting on one.** Whether\n any particular use is lawful where that customer operates — including the lawful basis for it, the\n notices it has to give, any impact assessment it has to carry out, and any consultation with employee\n representatives it has to run — is that customer's responsibility to determine, not ours.\n- **They can be wrong.** A classifier reading a screen has no idea what your job is. It can label genuine\n work as unrelated, and it can miss the opposite. Anyone relying on one of these outputs should treat it\n as a rough signal, and we say so to our customers as well as to you.\n\n### If an assessment about you has been generated\n\nAsk the organisation whose workspace holds the data — normally your employer. You can ask them for human\ninvolvement, for an explanation of how the assessment was reached, to express your point of view, and to\ncontest the result. They are the controller, so they are the ones who have to answer.\n\nIf you send that request to us, we will forward it to them promptly, tell you we have done so, and assist\nthem in answering it. See the routing paragraph in the section on your rights, which explains why we\ncannot decide it ourselves.\n\n## Children\n\n**The Service is not directed at children, and we do not knowingly collect personal data from them.** It\nis a business product, bought by organisations and used by the people who work in them. We do not design\nit for children, we do not market it to them, and we do not offer accounts to them.\n\nWhere consent is the basis for an online service offered directly to a child, the GDPR sets the age at\nwhich the child can consent alone. **In Bulgaria that age is 14.** Other EU and EEA countries set\nit anywhere between 13 and 16, and the age in the country where the child lives is the one that applies.\nBelow that age, consent has to come from — or be authorised by — a holder of parental responsibility.\nBecause we do not offer the Service to children, we do not operate a parental consent mechanism, and a\nchild under the applicable age should not create an account or submit personal data to us.\n\n### If a child's data has reached us\n\nTell us. Write to privacy@ever.co with enough detail for us to find the record — an email address, an\naccount name, or the page where the data was submitted. You do not need to prove anything first, and you\ndo not need to be the child's parent to report it.\n\nWe will check, and where we confirm that we hold personal data collected from a child without proper\nauthorisation, **we will delete it without undue delay**, keeping only what a law that applies to us\nrequires us to keep.\n\nIf the data sits inside one of our customers' workspaces rather than in our own records, the customer is\nthe controller of it. Tell them as well, and tell us — we will forward your report to them and press for\nit to be dealt with, as the routing paragraph in the section on your rights describes.\n\n## Links and content from other sites\n\nOur websites and the Service link to services we do not run, and some pages embed content that other\npeople host — videos, maps, code repositories, documentation and similar.\n\nFollowing a link takes you somewhere this policy does not reach. Loading embedded content means the\nprovider hosting it receives data directly from your browser, typically your IP address, your device and\nbrowser details, and the page you were on, and it may set its own cookies.\n\n**We do not control those services, and this policy does not apply to them.** What they collect and what\nthey do with it is governed by their own privacy notice, which is the one to read before you use them.\nWhere embedded content is not strictly necessary to deliver a page, we load it only once you have agreed\nto the relevant cookie category — see our [Cookie Policy](https://everdemand.co/cookies).\n\nA link is not an endorsement. If a link from our site takes you somewhere that mishandles your data, we\nwould like to know at privacy@ever.co so we can reconsider carrying it.\n\n## Changes to this policy\n\nThis policy changes when the Service changes, when we engage or replace a provider, or when the law moves.\nWe would rather update it than let it drift out of date and quietly stop being true.\n\nEvery version carries a version number and the date it takes effect, shown at the top of the page. **This\nis version 1.0.2, in force from 2026-08-02.**\n\n### How we tell you\n\n- **Minor changes** — clarifying wording, correcting a mistake, adding a provider of a kind already\n described — are published with a new version number and a new effective date. We do not send a separate\n notice for these.\n- **Material changes** — a new purpose, a new category of personal data, a new category of recipient, a\n longer retention period, a change to how you exercise your rights, or a change to the legal basis we\n rely on — are notified **at least 30 days before they take effect**, by email to account holders and by\n a notice on the site. That gives you time to read them and to act before they apply.\n- **Changes that need your consent** are not made by publishing a new version. We ask you, and we treat\n silence as a no.\n\nThis policy is a notice, not a contract. **We do not ask you to accept it**, and continuing to use the\nService is not us collecting your agreement to it. Where we genuinely need your agreement to something, we\nask for it separately and record it.\n\n### Previous versions stay available\n\nWe do not overwrite the past. **Every version of this policy that we have published remains available**,\nwith the dates it was in force, from the version history linked at the foot of\n[https://everdemand.co/privacy](https://everdemand.co/privacy). If you want to know what we said about your data on a\nparticular date, that is where to look — and if you cannot find it, ask us at privacy@ever.co and we\nwill send it to you.\n\n## How to contact us\n\nThe controller for the personal data described in this policy is **Ever Technologies LTD**, registered in\nBulgaria under company number 204599535, with its registered office at\nMladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria.\n\n- **Privacy questions, and any request about your personal data** — privacy@ever.co\n- **Data protection correspondence** — dpo@ever.co\n\nBoth addresses are monitored by the same people, and either will reach us. By post, write to the registered\noffice above and mark the letter for the attention of the privacy team. We correspond in English.\n\n**We have not designated a Data Protection Officer under Article 37 GDPR.** The dpo@ever.co address is\na contact channel, not a designation, and we will not describe it as one. If that position changes, this\npolicy will say so and will give the designated office's contact details.\n\nIf your question is about personal data held inside one of our customers' workspaces, that customer is the\ncontroller and the request goes to them — see the routing paragraph in the section on your rights. Write to\nus anyway if you are unsure, and we will tell you who to ask.\n\nThis document is version 1.0.2 of the Privacy Policy for\n[everdemand.co](https://everdemand.co), in force from 2026-08-02. Earlier versions, with the\ndates they applied, are at [https://everdemand.co/privacy](https://everdemand.co/privacy)."
364
364
  }