@ever-co/legal 0.5.0 → 0.6.0

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 (103) hide show
  1. package/dist/content/aup/ever-async/en.json +2 -2
  2. package/dist/content/aup/ever-corporate/en.json +2 -2
  3. package/dist/content/aup/ever-demand/en.json +2 -2
  4. package/dist/content/aup/ever-rec/en.json +2 -2
  5. package/dist/content/aup/ever-teams/en.json +2 -2
  6. package/dist/content/aup/ever-works/en.json +2 -2
  7. package/dist/content/aup/everiq/en.json +2 -2
  8. package/dist/content/aup/gauzy/en.json +2 -2
  9. package/dist/content/aup/githands/en.json +2 -2
  10. package/dist/content/aup/hust/en.json +2 -2
  11. package/dist/content/aup/traduora/en.json +2 -2
  12. package/dist/content/cookies/ever-async/en.json +2 -2
  13. package/dist/content/cookies/ever-corporate/en.json +2 -2
  14. package/dist/content/cookies/ever-demand/en.json +2 -2
  15. package/dist/content/cookies/ever-rec/en.json +2 -2
  16. package/dist/content/cookies/ever-teams/en.json +2 -2
  17. package/dist/content/cookies/ever-tech/en.html +11 -3
  18. package/dist/content/cookies/ever-tech/en.json +4 -4
  19. package/dist/content/cookies/ever-works/en.json +2 -2
  20. package/dist/content/cookies/everiq/en.json +2 -2
  21. package/dist/content/cookies/gauzy/en.json +2 -2
  22. package/dist/content/cookies/githands/en.json +2 -2
  23. package/dist/content/cookies/hust/en.json +2 -2
  24. package/dist/content/cookies/traduora/en.json +2 -2
  25. package/dist/content/dpa/ever-async/en.json +2 -2
  26. package/dist/content/dpa/ever-demand/en.json +2 -2
  27. package/dist/content/dpa/ever-rec/en.json +2 -2
  28. package/dist/content/dpa/ever-teams/en.json +2 -2
  29. package/dist/content/dpa/ever-tech-services/en.html +1847 -0
  30. package/dist/content/dpa/ever-tech-services/en.json +624 -0
  31. package/dist/content/dpa/ever-works/en.json +2 -2
  32. package/dist/content/dpa/gauzy/en.html +5 -10
  33. package/dist/content/dpa/gauzy/en.json +3 -3
  34. package/dist/content/dpa/githands/en.json +2 -2
  35. package/dist/content/dpa/hust/en.json +2 -2
  36. package/dist/content/dpia/gauzy/en.json +2 -2
  37. package/dist/content/privacy/ever-async/en.json +2 -2
  38. package/dist/content/privacy/ever-corporate/en.json +2 -2
  39. package/dist/content/privacy/ever-demand/en.json +2 -2
  40. package/dist/content/privacy/ever-rec/en.json +2 -2
  41. package/dist/content/privacy/ever-teams/en.json +2 -2
  42. package/dist/content/privacy/ever-tech/en.html +55 -12
  43. package/dist/content/privacy/ever-tech/en.json +12 -4
  44. package/dist/content/privacy/ever-works/en.json +2 -2
  45. package/dist/content/privacy/everiq/en.json +2 -2
  46. package/dist/content/privacy/gauzy/en.json +2 -2
  47. package/dist/content/privacy/githands/en.json +2 -2
  48. package/dist/content/privacy/hust/en.json +2 -2
  49. package/dist/content/privacy/traduora/en.json +2 -2
  50. package/dist/content/refund/ever-corporate/en.json +2 -2
  51. package/dist/content/refund/ever-demand/en.json +2 -2
  52. package/dist/content/refund/ever-rec/en.json +2 -2
  53. package/dist/content/refund/ever-teams/en.json +2 -2
  54. package/dist/content/refund/ever-tech-services/en.html +270 -0
  55. package/dist/content/refund/ever-tech-services/en.json +178 -0
  56. package/dist/content/refund/ever-works/en.json +2 -2
  57. package/dist/content/refund/gauzy/en.json +2 -2
  58. package/dist/content/refund/githands/en.json +2 -2
  59. package/dist/content/refund/hust/en.json +2 -2
  60. package/dist/content/refund/traduora/en.json +2 -2
  61. package/dist/content/security/ever-async/en.json +2 -2
  62. package/dist/content/security/ever-corporate/en.json +2 -2
  63. package/dist/content/security/ever-demand/en.json +2 -2
  64. package/dist/content/security/ever-rec/en.json +2 -2
  65. package/dist/content/security/ever-teams/en.json +2 -2
  66. package/dist/content/security/ever-tech/en.json +2 -2
  67. package/dist/content/security/ever-works/en.json +2 -2
  68. package/dist/content/security/gauzy/en.json +2 -2
  69. package/dist/content/security/githands/en.json +2 -2
  70. package/dist/content/security/hust/en.json +2 -2
  71. package/dist/content/security/traduora/en.json +2 -2
  72. package/dist/content/subprocessors/ever-async/en.json +2 -2
  73. package/dist/content/subprocessors/ever-corporate/en.json +2 -2
  74. package/dist/content/subprocessors/ever-demand/en.json +2 -2
  75. package/dist/content/subprocessors/ever-rec/en.json +2 -2
  76. package/dist/content/subprocessors/ever-teams/en.json +2 -2
  77. package/dist/content/subprocessors/ever-tech/en.html +16 -2
  78. package/dist/content/subprocessors/ever-tech/en.json +4 -4
  79. package/dist/content/subprocessors/ever-tech-services/en.html +357 -0
  80. package/dist/content/subprocessors/ever-tech-services/en.json +158 -0
  81. package/dist/content/subprocessors/ever-works/en.json +2 -2
  82. package/dist/content/subprocessors/everiq/en.json +2 -2
  83. package/dist/content/subprocessors/gauzy/en.json +2 -2
  84. package/dist/content/subprocessors/githands/en.json +2 -2
  85. package/dist/content/subprocessors/hust/en.json +2 -2
  86. package/dist/content/subprocessors/traduora/en.json +2 -2
  87. package/dist/content/tos/ever-async/en.json +2 -2
  88. package/dist/content/tos/ever-corporate/en.json +2 -2
  89. package/dist/content/tos/ever-demand/en.json +2 -2
  90. package/dist/content/tos/ever-rec/en.json +2 -2
  91. package/dist/content/tos/ever-teams/en.json +2 -2
  92. package/dist/content/tos/ever-tech/en.html +46 -11
  93. package/dist/content/tos/ever-tech/en.json +12 -4
  94. package/dist/content/tos/ever-tech-services/en.html +937 -0
  95. package/dist/content/tos/ever-tech-services/en.json +473 -0
  96. package/dist/content/tos/ever-works/en.json +2 -2
  97. package/dist/content/tos/everiq/en.json +2 -2
  98. package/dist/content/tos/gauzy/en.json +2 -2
  99. package/dist/content/tos/githands/en.json +2 -2
  100. package/dist/content/tos/hust/en.json +2 -2
  101. package/dist/content/tos/traduora/en.json +2 -2
  102. package/dist/index.json +1788 -343
  103. package/package.json +52 -52
@@ -8,7 +8,7 @@
8
8
  "locale": "en",
9
9
  "version": "1.0.0",
10
10
  "effectiveDate": "2026-10-24",
11
- "sha256": "20b37e6a3140a5c11cf3c82230930f0ece5b42f422b3771fda3a787558a01abf",
11
+ "sha256": "3637cead7db3d0ce882c398c1437eb522aadc2eadb8795f4bfae80dcad5d0d23",
12
12
  "publishable": true,
13
13
  "sections": [
14
14
  "core/dpia/010-purpose-and-status",
@@ -93,5 +93,5 @@
93
93
  }
94
94
  ],
95
95
  "path": "content/dpia/gauzy/en.html",
96
- "markdown": "# Data Protection Impact Assessment (DPIA) Support Pack\n\n**Ever Gauzy** — [gauzy.co](https://gauzy.co)\n\nVersion 1.0.0 · In force from 2026-10-24\n\nThis support pack describes the processing that Ever Gauzy Cloud carries out when a customer uses it\nto record working time and to monitor work. It is published by **Ever Technologies LTD** for the customers who\nuse the Service as the controller of their own people's personal data, and it is written to be copied into\ntheir data protection impact assessment, put in front of their data protection officer or works council, and\nchecked by an auditor.\n\n## Whose assessment this is\n\n**The impact assessment is yours, not ours.** Article 35 GDPR puts it on the controller, and for the data the\nService captures about your personnel the controller is you.\n\nArticle 28(3)(f) puts a different obligation on us as your processor: to assist you with Articles 35 and 36,\ntaking into account the nature of the processing and the information available to us. This pack is the main\nform that assistance takes. What we commit to beyond it — answering your questionnaire, supporting a prior\nconsultation, telling you about changes — is set out in the impact-assessment section of our\n[Data Processing Addendum](https://gauzy.co/dpa). That section also explains why an assessment is very\nprobably required before you switch monitoring on.\n\n## What this pack is, and what it is not\n\n- **It describes the Service as it stands on the date above** — the software, its settings and their\n defaults, and how we operate the hosted Service. Where we do not know an answer, it says \"to be confirmed\"\n instead of guessing. Where a control is **not** available in Ever Gauzy today, it says so: in an\n assessment, an accurate negative is worth more than a reassuring sentence.\n- **It is not legal advice.** It does not tell you whether your processing is lawful. That depends on your\n purposes, your workforce, the employment law of your country and your own balancing of interests — none of\n which we can see.\n- **It does not amend the Data Processing Addendum.** The Addendum and its Schedules remain the contract\n between us. If you find this pack and the Addendum describing the same thing differently, tell us at\n privacy@ever.co and we will correct whichever of them is wrong.\n- **It covers Ever Gauzy Cloud, the hosted Service we operate.** If you run Ever Gauzy on your\n own infrastructure we are not your processor for that deployment. The descriptions of the software below\n still apply to it; everything about hosting, storage, sub-processors, backups and our own operations does\n not, and those are yours to describe.\n\n## How to use this pack\n\nImpact-assessment templates, including those published by supervisory authorities, ask broadly the same\nquestions: what is processed and about whom, how often and in what volume, for how long, where and by whom,\nhow it is secured, which risks it creates, and what reduces them. The sections that follow answer those\nquestions for Ever Gauzy:\n\n- **where capture happens** — which software captures, and which does not;\n- **what each feature records** — feature by feature, with its default and what it does not record;\n- **how often, and how much** — the capture intervals, and what they mean in records per person per day;\n- **how long data is kept, and how it is deleted** — including what the product does not do automatically;\n- **where the data is stored, and who else receives it** — storage, sub-processors and transfers;\n- **how it is secured** — the measures that matter for monitoring data; and\n- **the controls, and the risk each one addresses** — every privacy control the product offers, the risk it\n reduces, and the risk it leaves behind.\n\n**Record the version and date of this pack in your assessment.** The Service changes, and an assessment\nshould say which description it relied on. When a change could affect an assessment you have already done — a\nnew data category, a new capture feature, a change to a default, a new sub-processor, a change of storage\nregion or of a retention ceiling — we tell you, as the Data Processing Addendum provides, and we publish a new\nversion of this pack.\n\n## Ever Gauzy: what is captured, how often, for how long, and what each control does\n\nEverything in this part is specific to Ever Gauzy. It describes the software as it behaves on the date\nof this pack, including where that behaviour is less protective than you might assume. **Where a default is\n\"on\", it is on for a new organisation until an administrator changes it.**\n\n### Where capture happens\n\nCapture is done by software running on a person's device, not by the platform.\n\n- **The web application** at app.gauzy.co has no screen, camera or audio capture for monitoring. Entering\n time, managing tasks or reading reports in a browser produces no screenshot and no activity record.\n- **The desktop timer** captures while the person's timer is running and stops when they stop it.\n- **The background agent** has no timer window. It starts tracking by itself when it starts and when the\n person signs in, registers itself to start when the person logs in to their computer, and shows its status\n (\"monitoring active\") in the system tray or menu bar, from where the person can stop and start tracking.\n **In the current version it also starts tracking again when the device wakes from sleep, even if the person\n had stopped tracking before the device slept.** Whether the person can quit or sign out of the agent is\n decided by two settings described in the controls below.\n- **Connected services can bring captured data with them.** Where an organisation connects Hubstaff or Upwork,\n screenshots and activity levels those platforms took are imported into the workspace. Where a person\n connects ActivityWatch or WakaTime, their events are added to the activity records.\n\n### What each feature records\n\n| Feature | What is recorded | Default | What is not recorded |\n|---|---|---|---|\n| Time entries | Start and stop times, duration, project, task and client, manual entries, idle time removed or kept, and approvals | Core to the product | — |\n| Screenshots | A full-resolution image of the screen and a thumbnail, linked to the time slot it belongs to. Either every connected display or the active display only. The background agent also takes one when tracking starts and when it stops or the device goes to sleep | **On.** Screenshot capture is on for a new organisation and for each person, and every connected display is captured | The image is not blurred, masked or redacted in any way: Ever Gauzy has no blurring feature today. Nothing is captured while the desktop timer is stopped or while the agent is not tracking |\n| Activity level, desktop timer | Whether the computer was idle, from the operating system's idle time. Keyboard and mouse percentages only where ActivityWatch is connected, taken from its away-from-keyboard data | On while the timer runs | The desktop timer does not listen to individual key presses and records no key identity |\n| Activity level, background agent | Per one-minute interval: the number of key presses, the number of left and right mouse clicks, the number of mouse movements, and the time away from the keyboard | **Off.** The keyboard and mouse tracking setting is off for a new organisation and for each person | With the setting off, the agent records no keyboard or mouse data |\n| Keystroke sequence and mouse movement, background agent | **When keyboard and mouse tracking is on, the agent also records the code of every key pressed, in the order pressed, and the start and end screen coordinates of each mouse movement**, and sends them to the Service, which stores them with the activity record. The API request log may keep a further copy (see retention) | Off, as above | Key codes identify physical keys, not the characters a keyboard layout produces. A sequence of them can nevertheless reveal what was typed, including passwords, so treat this as a record of keystrokes |\n| Application usage | The name of the application in use and the title of its window, with the time spent. The agent samples once a second; the desktop timer every ten seconds, or uses ActivityWatch's window data where it is connected | Recorded whenever tracking runs. **No organisation or per-person setting switches it off today** | — |\n| Website usage | The address and title of the page in the active browser window: natively on macOS, and on any operating system where ActivityWatch and its browser extension are in use | Recorded whenever tracking runs, as above | — |\n| Idle and inactivity handling, desktop timer | An inactivity limit after which the person is asked whether they were working, a window in which to answer, and an option to remove idle time from the timesheet | Inactivity tracking on; limit 10 minutes; answer window 1 minute; idle time kept | — |\n| Webcam stills | Images from the device camera, with a thumbnail, linked to the time slot | **Not captured** unless a separate camera plugin is installed on the device | The desktop applications themselves do not use the camera or the microphone |\n| Audio recordings | Audio files recorded from the device microphone, up to 100 MB each, with their duration, channel count and sample rate. These are recordings, not sound levels | **Not captured** unless a separate audio plugin is installed on the device | As above |\n| Screen recordings | Video files of the screen, with their duration, resolution, codec and frame rate | **Not captured** unless a separate video plugin is installed on the device | As above |\n| ActivityWatch ingest | Window events (application, title, address), away-from-keyboard status, and browser events including the page address and title, whether the tab was playing sound, the number of open tabs, and **whether the window was in private browsing mode** | Only where ActivityWatch is running on the device. The desktop timer's ActivityWatch option is on by default | Private-browsing activity is not filtered out |\n| WakaTime ingest | Coding activity: editor, language, project, branch, file path and line, and the machine name | Only where the person connects WakaTime | — |\n| AI screenshot analysis | For each screenshot, a generated description, the applications identified in it, and a verdict on whether the content appears to be work-related | **Off** unless the organisation enables the AI integration for this purpose | — |\n| Location | The Service does not capture a device's position during time tracking. Addresses and coordinates exist only where people enter them, on organisations, contacts and candidates | — | No GPS or device location. The API accepts a free-form location field on time slots that none of our applications fill in; an integration you build could |\n\nFor the camera, audio and video plugins, the capture behaviour on the device — interval, on-screen indicator,\nwhich camera or microphone is used — is set by the plugin, and its description in this pack is **to be\nconfirmed**. Until it is, treat any of the three as unassessed and keep them off.\n\n### How often, and how much\n\n**Screenshot intervals.** The available intervals are 1, 3, 5 and 10 minutes. There is no longer interval.\n\n- **Desktop timer.** The interval is a setting on the device, 10 minutes by default, which the person can\n change while the timer is stopped. The organisation's screenshot interval, randomised capture and\n capture-on-sleep settings are applied to the device **only when the organisation's timer policy is\n enforced**, which it is not by default.\n- **Background agent.** The interval comes from the agent's own settings on the device. **The agent does not\n read the organisation's screenshot interval.**\n\n**Randomised capture** is off by default. It works differently in the two applications:\n\n- in the desktop timer, each screenshot is taken at a random point that is never later than the configured\n interval, so gaps range from 1 minute up to the interval;\n- in the background agent, each next gap is chosen at random from 1, 3, 5 and 10 minutes **regardless of\n the configured interval**, an average of 4.75 minutes.\n\n**What that means per person.** For a person tracked for 8 hours, with one display:\n\n| Configuration | Screenshots in 8 hours |\n|---|---|\n| Fixed, every 10 minutes | 48 |\n| Fixed, every 5 minutes | 96 |\n| Fixed, every 3 minutes | 160 |\n| Fixed, every minute | 480 |\n| Randomised, desktop timer, 10-minute interval | about 80 on average, and up to 480 |\n| Randomised, background agent, any interval | about 100 on average, and up to 480 |\n\nMultiply by the number of displays where every display is captured, which is the default. The background agent\nadds one screenshot each time tracking starts and each time it stops or the device sleeps.\n\n**Activity records.** The background agent sends an activity record every minute while it tracks — 480 in an\n8-hour day — and samples the active window every second. The desktop timer samples the active window every ten\nseconds and sends its records at each capture interval.\n\n### How long it is kept, and how it is deleted\n\n**Ever Gauzy does not delete monitoring data automatically today.** It has no retention setting for\nscreenshots, other captured media, activity records or application and website records, and no scheduled job\nthat deletes them. They are kept until someone deletes them, or until your subscription ends and the deletion\ntimetable in the Data Processing Addendum runs. If your assessment sets a retention period, you implement it\nby deleting the data on that schedule, or by asking us to.\n\n**Deleting inside the application is a soft deletion by default.** Deleting a screenshot, a time slot or a\ntime entry in the web application marks the record as deleted and removes it from timesheets, galleries and\nreports. The database record stays, and so do the image and its thumbnail in object storage. Permanently\ndeleting a screenshot through the API removes its record and deletes the stored image and thumbnail. If you need\nsoft-deleted captures removed permanently and cannot do it yourself, write to privacy@ever.co and we will\ntreat it as a deletion instruction under the Data Processing Addendum.\n\n**A request log holds a further copy.** The API keeps a log of the time-tracking requests it receives — the\naddress, the IP address and user agent, and the request and response bodies, with passwords and tokens\nredacted — which therefore includes activity data sent by the desktop applications, keystroke sequences\nincluded where they are recorded. The log is on by default in the software and has no automatic expiry.\nWhether it is enabled on Ever Gauzy Cloud, and for how long its entries are kept, is **to be\nconfirmed**.\n\n**At the end of your subscription** you have 30 days to export your data, and deletion from our live systems\nthen completes within a further 30 days. **Backups** age out within 30 days of a deletion. Both are set out in\nthe Data Processing Addendum and the retention section of our [Privacy Policy](https://gauzy.co/privacy).\n\n### Where monitoring data is stored on Ever Gauzy Cloud\n\n- **Records** — time slots, activity records, screenshot metadata, settings — are held in the PostgreSQL\n database we operate.\n- **Captured files** — screenshots, thumbnails and any camera, audio or video files — are held in\n S3-compatible object storage that we operate, on our own infrastructure in the European Union. They are not\n public: the applications fetch them through signed links that expire after one hour.\n- **A workspace can be configured to use its own storage provider** instead. Where your organisation does\n that, captured files go to that provider under your own agreement with it.\n- **Where AI screenshot analysis is enabled**, each screenshot is sent to the Gauzy AI service for analysis.\n Where that service runs, and when content goes onward to a model provider, is described in the annex to our\n [Privacy Policy](https://gauzy.co/privacy).\n- **Customer separation** is logical. All workspaces share the application and the database; every record\n carries the tenant and organisation it belongs to, and the application uses them to scope queries to the\n workspace of the person asking.\n\n### The controls, and the risk each one addresses\n\n| Control | Default | Risk it reduces | What it leaves, and what you still need to do |\n|---|---|---|---|\n| Screenshots off, for the organisation or for one person | Screenshots on | Systematic visual monitoring, and incidental capture of special-category data, private messages and third parties on screen | While screenshots are on, everything visible is captured at full resolution. Switch them off for people and roles you have not assessed as needing them |\n| Active display only, instead of every display | Every display | Capture of screens the work is not on, and multiplied volume | The active display can still show anything |\n| Capture interval | 10 minutes | Volume of capture, under data minimisation | 10 minutes is the longest interval available. On the desktop timer the organisation's interval applies only when the timer policy is enforced; the agent does not read it |\n| Enforcing the organisation's timer policy | Not enforced | Inconsistent per-device settings | Enforcing also removes per-person exceptions. It does not reach the background agent's interval |\n| Randomised capture | Off | Predictable capture that people work around | Changes volume, in a direction that depends on the application and the interval. In the desktop timer it always increases it — about 80 screenshots in 8 hours at a 10-minute interval instead of 48. In the agent it gives about 100 in 8 hours whatever the interval: more than a fixed 5 or 10 minutes (96 or 48), fewer than a fixed 1 or 3 minutes (480 or 160) |\n| Keyboard and mouse tracking, background agent | Off | With it off, no keyboard or mouse data and no keystroke sequence is recorded | **With it on, the sequence of keys pressed and mouse coordinates are recorded.** We consider keeping it off load-bearing for a defensible configuration |\n| Inactivity limit and removal of idle time, desktop timer | Limit 10 minutes, answer window 1 minute, idle time kept | Time recorded while nobody is working | Idle detection is by input and operating-system idle time, not by what the person is doing |\n| Visibility of tracked data to the person tracked | On | People not knowing what is recorded about them; supports their right of access | The API enforces the setting. It does not replace the notice you owe your people |\n| Agent exit and sign-out | Allowed | Monitoring the person cannot stop | The API refuses to restrict either setting for a person or organisation whose country, locale or time zone on record is in the EEA or the UK. Elsewhere a restriction needs an explicit acknowledgement, which is recorded against the administrator's account. A person with no location or time zone on record is treated as outside the EEA and UK, and restrictions applied before this check existed are not lifted automatically |\n| Deleting a capture | — | A capture that caught something it should not have | In the web application deletion is soft: the stored image remains until it is permanently deleted |\n| Camera, audio and screen recording plugins | Not installed | The most intrusive capture types | Each needs a separate decision and its own assessment |\n| AI screenshot analysis | Off | — | When on, an automated verdict on whether content appears work-related is attached to each screenshot. It is an input for a person to weigh, not a decision |\n\n**Controls that Ever Gauzy does not offer today.** No blurring or masking of screenshots; no excluded\napplications or websites; no per-person pause other than stopping the timer or the agent's tracking; no\nretention period with automatic deletion; and no log of who viewed a capture — the activity log records\ncreation, changes and deletions, not viewing. If your assessment depends on any of these, it cannot rely on\nEver Gauzy to provide it today.\n\n### What we can tell you about your own account\n\nOn request at privacy@ever.co we will tell you, for your assessment: which capture features are enabled\nin your workspace and their current settings, where its captured files are stored, and which sub-processors\nare involved.\n\n## Hosting, sub-processors and transfers\n\nThis section summarises what our [sub-processor page](https://gauzy.co/subprocessors) and\n[Security page](https://gauzy.co/security) say in full. Where this summary and those pages differ, those pages\nare the current statement and this summary is the one to correct.\n\n### Where processing happens\n\n- **Primary processing is in the European Union, on infrastructure we operate.** The Service runs on physical\n servers we own, in facilities we control, inside the European Union. The database and the object storage\n that hold Customer Personal Data are components we run, not services bought from a third party.\n- **Requests pass through a content delivery and security network** that terminates traffic at the edge\n location nearest to whoever makes the request, which can be anywhere in the world, before carrying it to our\n infrastructure. That provider is in the always-engaged tier of the sub-processor list.\n- **Off-site backup copies are held by an external object storage provider**, encrypted by us before they\n leave our network. The provider holds ciphertext and no key.\n- **Our source code, build pipeline and container images are hosted by a third party.** That is how the\n Service is built and deployed, not where your data is stored.\n\nThis is not multi-region hosting, and we do not describe it as such. The continuity section of the Security\npage explains what a site-level failure would mean.\n\n### Sub-processors\n\nThe [sub-processor list](https://gauzy.co/subprocessors) for Ever Gauzy has three tiers, and the tier\nmatters as much as the name:\n\n- **Tier 1 — always engaged.** In the path for every customer, with no setting that removes them. This is the\n Article 28 list proper.\n- **Tier 2 — engaged only when something brings them in**: a feature an administrator enables, an\n integration someone connects, a provider configured for the workspace, or a cookie category a visitor\n accepts. Several of them are providers that you contract with directly, under your own account.\n- **Tier 3 — self-hosted deployments only.** Providers the software can be configured to use in a deployment\n you run. We are not a processor for anything in that tier.\n\nFor each provider the list gives the purpose, the location, the categories of personal data it receives and\nthe transfer mechanism relied on. For your assessment, read the categories of data column against the\nfeatures you actually enable: a tier 2 provider is not processing your data unless the condition next to it is\ntrue.\n\n### Transfers outside the European Economic Area\n\nWhere a provider processes personal data outside the European Economic Area, the transfer mechanism is stated\nagainst it on the sub-processor list, and Schedule 3 of the Data Processing Addendum describes the mechanism\nand the transfer impact assessment behind it. **Where we cannot yet evidence a mechanism for a provider, the\nlist says \"To be confirmed\" rather than naming one.** Read those rows as an open item, and ask us at\nprivacy@ever.co for the current position on any provider that matters to your assessment.\n\nIf you need a copy of the safeguards for a named provider — the Standard Contractual Clauses and the modules\nthat apply — write to privacy@ever.co and we will send them.\n\n## Security measures\n\nThe technical and organisational measures we operate are described on our\n[Security page](https://gauzy.co/security) and, contractually, in Schedule 2 of the Data Processing Addendum.\nThe points below are the ones an assessment of monitoring data usually turns on.\n\n- **Encryption.** Traffic between users and the Service travels over TLS, and plain HTTP is redirected rather\n than served. Storage holding customer content, databases and backups is encrypted at rest, and off-site\n backup copies are encrypted before they leave our network, with keys we hold. Encryption at rest protects\n against the loss or theft of physical media; it does not protect data from a running system that has\n already decrypted it.\n- **Access by our personnel.** Production access uses named individual accounts, is scoped to the narrowest\n role that lets the work happen, and is revoked when someone no longer needs it. We access the content of a\n workspace only where that is necessary to operate, secure or support the Service, and we do not browse or\n review captured data for purposes of our own. The access-control section of the Security page describes\n this, including its limits for a team of our size.\n- **Separation between customers is logical, not physical**, unless you have separately contracted for a\n dedicated deployment. The product-specific part of this pack states how that separation works in\n Ever Gauzy.\n- **Backups and continuity.** Backups are held in three tiers, the last of them off-site and encrypted, and\n each backup ages out on its own rolling cycle within the period stated in the retention section of our\n [Privacy Policy](https://gauzy.co/privacy).\n\n**We do not hold a SOC 2 report of any type, and we are not certified to ISO/IEC 27001.** If any document has\ntold you otherwise, it is wrong. What we offer instead — the Security page, Schedule 2, answers to a security\nquestionnaire and evidence on request — is described on the Security page.\n\n## Questions, and a version you can cite\n\n- **A question about anything in this pack, an impact-assessment questionnaire, or a request for the current\n settings of your own account** — privacy@ever.co\n- **A request for the Data Processing Addendum, a security questionnaire, or evidence of a restore test** —\n legal@ever.co\n- **Something you think has been compromised — tell us immediately** — abuse@ever.co\n\nBy post: **Ever Technologies LTD**, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — registered in Bulgaria under company number\n204599535. We correspond in English.\n\n**We have not designated a Data Protection Officer under Article 37 GDPR.** dpo@ever.co is a contact\nchannel, monitored by the same people as privacy@ever.co, and we will not describe it as a designation. If\na questionnaire asks for our data protection officer, that sentence is the honest answer.\n\nThis document is version 1.0.0 of the DPIA Support Pack for\n[gauzy.co](https://gauzy.co), in force from 2026-10-24. It describes the Service as it\nstood on that date. Cite the version and the date in your assessment, and check for a newer version before\nyou rely on it again."
96
+ "markdown": "# Data Protection Impact Assessment (DPIA) Support Pack\r\n\r\n**Ever Gauzy** — [gauzy.co](https://gauzy.co)\r\n\r\nVersion 1.0.0 · In force from 2026-10-24\r\n\r\nThis support pack describes the processing that Ever Gauzy Cloud carries out when a customer uses it\r\nto record working time and to monitor work. It is published by **Ever Technologies LTD** for the customers who\r\nuse the Service as the controller of their own people's personal data, and it is written to be copied into\r\ntheir data protection impact assessment, put in front of their data protection officer or works council, and\r\nchecked by an auditor.\r\n\r\n## Whose assessment this is\r\n\r\n**The impact assessment is yours, not ours.** Article 35 GDPR puts it on the controller, and for the data the\r\nService captures about your personnel the controller is you.\r\n\r\nArticle 28(3)(f) puts a different obligation on us as your processor: to assist you with Articles 35 and 36,\r\ntaking into account the nature of the processing and the information available to us. This pack is the main\r\nform that assistance takes. What we commit to beyond it — answering your questionnaire, supporting a prior\r\nconsultation, telling you about changes — is set out in the impact-assessment section of our\r\n[Data Processing Addendum](https://gauzy.co/dpa). That section also explains why an assessment is very\r\nprobably required before you switch monitoring on.\r\n\r\n## What this pack is, and what it is not\r\n\r\n- **It describes the Service as it stands on the date above** — the software, its settings and their\r\n defaults, and how we operate the hosted Service. Where we do not know an answer, it says \"to be confirmed\"\r\n instead of guessing. Where a control is **not** available in Ever Gauzy today, it says so: in an\r\n assessment, an accurate negative is worth more than a reassuring sentence.\r\n- **It is not legal advice.** It does not tell you whether your processing is lawful. That depends on your\r\n purposes, your workforce, the employment law of your country and your own balancing of interests — none of\r\n which we can see.\r\n- **It does not amend the Data Processing Addendum.** The Addendum and its Schedules remain the contract\r\n between us. If you find this pack and the Addendum describing the same thing differently, tell us at\r\n privacy@ever.co and we will correct whichever of them is wrong.\r\n- **It covers Ever Gauzy Cloud, the hosted Service we operate.** If you run Ever Gauzy on your\r\n own infrastructure we are not your processor for that deployment. The descriptions of the software below\r\n still apply to it; everything about hosting, storage, sub-processors, backups and our own operations does\r\n not, and those are yours to describe.\n\n## How to use this pack\r\n\r\nImpact-assessment templates, including those published by supervisory authorities, ask broadly the same\r\nquestions: what is processed and about whom, how often and in what volume, for how long, where and by whom,\r\nhow it is secured, which risks it creates, and what reduces them. The sections that follow answer those\r\nquestions for Ever Gauzy:\r\n\r\n- **where capture happens** — which software captures, and which does not;\r\n- **what each feature records** — feature by feature, with its default and what it does not record;\r\n- **how often, and how much** — the capture intervals, and what they mean in records per person per day;\r\n- **how long data is kept, and how it is deleted** — including what the product does not do automatically;\r\n- **where the data is stored, and who else receives it** — storage, sub-processors and transfers;\r\n- **how it is secured** — the measures that matter for monitoring data; and\r\n- **the controls, and the risk each one addresses** — every privacy control the product offers, the risk it\r\n reduces, and the risk it leaves behind.\r\n\r\n**Record the version and date of this pack in your assessment.** The Service changes, and an assessment\r\nshould say which description it relied on. When a change could affect an assessment you have already done — a\r\nnew data category, a new capture feature, a change to a default, a new sub-processor, a change of storage\r\nregion or of a retention ceiling — we tell you, as the Data Processing Addendum provides, and we publish a new\r\nversion of this pack.\n\n## Ever Gauzy: what is captured, how often, for how long, and what each control does\r\n\r\nEverything in this part is specific to Ever Gauzy. It describes the software as it behaves on the date\r\nof this pack, including where that behaviour is less protective than you might assume. **Where a default is\r\n\"on\", it is on for a new organisation until an administrator changes it.**\r\n\r\n### Where capture happens\r\n\r\nCapture is done by software running on a person's device, not by the platform.\r\n\r\n- **The web application** at app.gauzy.co has no screen, camera or audio capture for monitoring. Entering\r\n time, managing tasks or reading reports in a browser produces no screenshot and no activity record.\r\n- **The desktop timer** captures while the person's timer is running and stops when they stop it.\r\n- **The background agent** has no timer window. It starts tracking by itself when it starts and when the\r\n person signs in, registers itself to start when the person logs in to their computer, and shows its status\r\n (\"monitoring active\") in the system tray or menu bar, from where the person can stop and start tracking.\r\n **In the current version it also starts tracking again when the device wakes from sleep, even if the person\r\n had stopped tracking before the device slept.** Whether the person can quit or sign out of the agent is\r\n decided by two settings described in the controls below.\r\n- **Connected services can bring captured data with them.** Where an organisation connects Hubstaff or Upwork,\r\n screenshots and activity levels those platforms took are imported into the workspace. Where a person\r\n connects ActivityWatch or WakaTime, their events are added to the activity records.\r\n\r\n### What each feature records\r\n\r\n| Feature | What is recorded | Default | What is not recorded |\r\n|---|---|---|---|\r\n| Time entries | Start and stop times, duration, project, task and client, manual entries, idle time removed or kept, and approvals | Core to the product | — |\r\n| Screenshots | A full-resolution image of the screen and a thumbnail, linked to the time slot it belongs to. Either every connected display or the active display only. The background agent also takes one when tracking starts and when it stops or the device goes to sleep | **On.** Screenshot capture is on for a new organisation and for each person, and every connected display is captured | The image is not blurred, masked or redacted in any way: Ever Gauzy has no blurring feature today. Nothing is captured while the desktop timer is stopped or while the agent is not tracking |\r\n| Activity level, desktop timer | Whether the computer was idle, from the operating system's idle time. Keyboard and mouse percentages only where ActivityWatch is connected, taken from its away-from-keyboard data | On while the timer runs | The desktop timer does not listen to individual key presses and records no key identity |\r\n| Activity level, background agent | Per one-minute interval: the number of key presses, the number of left and right mouse clicks, the number of mouse movements, and the time away from the keyboard | **Off.** The keyboard and mouse tracking setting is off for a new organisation and for each person | With the setting off, the agent records no keyboard or mouse data |\r\n| Keystroke sequence and mouse movement, background agent | **When keyboard and mouse tracking is on, the agent also records the code of every key pressed, in the order pressed, and the start and end screen coordinates of each mouse movement**, and sends them to the Service, which stores them with the activity record. The API request log may keep a further copy (see retention) | Off, as above | Key codes identify physical keys, not the characters a keyboard layout produces. A sequence of them can nevertheless reveal what was typed, including passwords, so treat this as a record of keystrokes |\r\n| Application usage | The name of the application in use and the title of its window, with the time spent. The agent samples once a second; the desktop timer every ten seconds, or uses ActivityWatch's window data where it is connected | Recorded whenever tracking runs. **No organisation or per-person setting switches it off today** | — |\r\n| Website usage | The address and title of the page in the active browser window: natively on macOS, and on any operating system where ActivityWatch and its browser extension are in use | Recorded whenever tracking runs, as above | — |\r\n| Idle and inactivity handling, desktop timer | An inactivity limit after which the person is asked whether they were working, a window in which to answer, and an option to remove idle time from the timesheet | Inactivity tracking on; limit 10 minutes; answer window 1 minute; idle time kept | — |\r\n| Webcam stills | Images from the device camera, with a thumbnail, linked to the time slot | **Not captured** unless a separate camera plugin is installed on the device | The desktop applications themselves do not use the camera or the microphone |\r\n| Audio recordings | Audio files recorded from the device microphone, up to 100 MB each, with their duration, channel count and sample rate. These are recordings, not sound levels | **Not captured** unless a separate audio plugin is installed on the device | As above |\r\n| Screen recordings | Video files of the screen, with their duration, resolution, codec and frame rate | **Not captured** unless a separate video plugin is installed on the device | As above |\r\n| ActivityWatch ingest | Window events (application, title, address), away-from-keyboard status, and browser events including the page address and title, whether the tab was playing sound, the number of open tabs, and **whether the window was in private browsing mode** | Only where ActivityWatch is running on the device. The desktop timer's ActivityWatch option is on by default | Private-browsing activity is not filtered out |\r\n| WakaTime ingest | Coding activity: editor, language, project, branch, file path and line, and the machine name | Only where the person connects WakaTime | — |\r\n| AI screenshot analysis | For each screenshot, a generated description, the applications identified in it, and a verdict on whether the content appears to be work-related | **Off** unless the organisation enables the AI integration for this purpose | — |\r\n| Location | The Service does not capture a device's position during time tracking. Addresses and coordinates exist only where people enter them, on organisations, contacts and candidates | — | No GPS or device location. The API accepts a free-form location field on time slots that none of our applications fill in; an integration you build could |\r\n\r\nFor the camera, audio and video plugins, the capture behaviour on the device — interval, on-screen indicator,\r\nwhich camera or microphone is used — is set by the plugin, and its description in this pack is **to be\r\nconfirmed**. Until it is, treat any of the three as unassessed and keep them off.\r\n\r\n### How often, and how much\r\n\r\n**Screenshot intervals.** The available intervals are 1, 3, 5 and 10 minutes. There is no longer interval.\r\n\r\n- **Desktop timer.** The interval is a setting on the device, 10 minutes by default, which the person can\r\n change while the timer is stopped. The organisation's screenshot interval, randomised capture and\r\n capture-on-sleep settings are applied to the device **only when the organisation's timer policy is\r\n enforced**, which it is not by default.\r\n- **Background agent.** The interval comes from the agent's own settings on the device. **The agent does not\r\n read the organisation's screenshot interval.**\r\n\r\n**Randomised capture** is off by default. It works differently in the two applications:\r\n\r\n- in the desktop timer, each screenshot is taken at a random point that is never later than the configured\r\n interval, so gaps range from 1 minute up to the interval;\r\n- in the background agent, each next gap is chosen at random from 1, 3, 5 and 10 minutes **regardless of\r\n the configured interval**, an average of 4.75 minutes.\r\n\r\n**What that means per person.** For a person tracked for 8 hours, with one display:\r\n\r\n| Configuration | Screenshots in 8 hours |\r\n|---|---|\r\n| Fixed, every 10 minutes | 48 |\r\n| Fixed, every 5 minutes | 96 |\r\n| Fixed, every 3 minutes | 160 |\r\n| Fixed, every minute | 480 |\r\n| Randomised, desktop timer, 10-minute interval | about 80 on average, and up to 480 |\r\n| Randomised, background agent, any interval | about 100 on average, and up to 480 |\r\n\r\nMultiply by the number of displays where every display is captured, which is the default. The background agent\r\nadds one screenshot each time tracking starts and each time it stops or the device sleeps.\r\n\r\n**Activity records.** The background agent sends an activity record every minute while it tracks — 480 in an\r\n8-hour day — and samples the active window every second. The desktop timer samples the active window every ten\r\nseconds and sends its records at each capture interval.\r\n\r\n### How long it is kept, and how it is deleted\r\n\r\n**Ever Gauzy does not delete monitoring data automatically today.** It has no retention setting for\r\nscreenshots, other captured media, activity records or application and website records, and no scheduled job\r\nthat deletes them. They are kept until someone deletes them, or until your subscription ends and the deletion\r\ntimetable in the Data Processing Addendum runs. If your assessment sets a retention period, you implement it\r\nby deleting the data on that schedule, or by asking us to.\r\n\r\n**Deleting inside the application is a soft deletion by default.** Deleting a screenshot, a time slot or a\r\ntime entry in the web application marks the record as deleted and removes it from timesheets, galleries and\r\nreports. The database record stays, and so do the image and its thumbnail in object storage. Permanently\r\ndeleting a screenshot through the API removes its record and deletes the stored image and thumbnail. If you need\r\nsoft-deleted captures removed permanently and cannot do it yourself, write to privacy@ever.co and we will\r\ntreat it as a deletion instruction under the Data Processing Addendum.\r\n\r\n**A request log holds a further copy.** The API keeps a log of the time-tracking requests it receives — the\r\naddress, the IP address and user agent, and the request and response bodies, with passwords and tokens\r\nredacted — which therefore includes activity data sent by the desktop applications, keystroke sequences\r\nincluded where they are recorded. The log is on by default in the software and has no automatic expiry.\r\nWhether it is enabled on Ever Gauzy Cloud, and for how long its entries are kept, is **to be\r\nconfirmed**.\r\n\r\n**At the end of your subscription** you have 30 days to export your data, and deletion from our live systems\r\nthen completes within a further 30 days. **Backups** age out within 30 days of a deletion. Both are set out in\r\nthe Data Processing Addendum and the retention section of our [Privacy Policy](https://gauzy.co/privacy).\r\n\r\n### Where monitoring data is stored on Ever Gauzy Cloud\r\n\r\n- **Records** — time slots, activity records, screenshot metadata, settings — are held in the PostgreSQL\r\n database we operate.\r\n- **Captured files** — screenshots, thumbnails and any camera, audio or video files — are held in\r\n S3-compatible object storage that we operate, on our own infrastructure in the European Union. They are not\r\n public: the applications fetch them through signed links that expire after one hour.\r\n- **A workspace can be configured to use its own storage provider** instead. Where your organisation does\r\n that, captured files go to that provider under your own agreement with it.\r\n- **Where AI screenshot analysis is enabled**, each screenshot is sent to the Gauzy AI service for analysis.\r\n Where that service runs, and when content goes onward to a model provider, is described in the annex to our\r\n [Privacy Policy](https://gauzy.co/privacy).\r\n- **Customer separation** is logical. All workspaces share the application and the database; every record\r\n carries the tenant and organisation it belongs to, and the application uses them to scope queries to the\r\n workspace of the person asking.\r\n\r\n### The controls, and the risk each one addresses\r\n\r\n| Control | Default | Risk it reduces | What it leaves, and what you still need to do |\r\n|---|---|---|---|\r\n| Screenshots off, for the organisation or for one person | Screenshots on | Systematic visual monitoring, and incidental capture of special-category data, private messages and third parties on screen | While screenshots are on, everything visible is captured at full resolution. Switch them off for people and roles you have not assessed as needing them |\r\n| Active display only, instead of every display | Every display | Capture of screens the work is not on, and multiplied volume | The active display can still show anything |\r\n| Capture interval | 10 minutes | Volume of capture, under data minimisation | 10 minutes is the longest interval available. On the desktop timer the organisation's interval applies only when the timer policy is enforced; the agent does not read it |\r\n| Enforcing the organisation's timer policy | Not enforced | Inconsistent per-device settings | Enforcing also removes per-person exceptions. It does not reach the background agent's interval |\r\n| Randomised capture | Off | Predictable capture that people work around | Changes volume, in a direction that depends on the application and the interval. In the desktop timer it always increases it — about 80 screenshots in 8 hours at a 10-minute interval instead of 48. In the agent it gives about 100 in 8 hours whatever the interval: more than a fixed 5 or 10 minutes (96 or 48), fewer than a fixed 1 or 3 minutes (480 or 160) |\r\n| Keyboard and mouse tracking, background agent | Off | With it off, no keyboard or mouse data and no keystroke sequence is recorded | **With it on, the sequence of keys pressed and mouse coordinates are recorded.** We consider keeping it off load-bearing for a defensible configuration |\r\n| Inactivity limit and removal of idle time, desktop timer | Limit 10 minutes, answer window 1 minute, idle time kept | Time recorded while nobody is working | Idle detection is by input and operating-system idle time, not by what the person is doing |\r\n| Visibility of tracked data to the person tracked | On | People not knowing what is recorded about them; supports their right of access | The API enforces the setting. It does not replace the notice you owe your people |\r\n| Agent exit and sign-out | Allowed | Monitoring the person cannot stop | The API refuses to restrict either setting for a person or organisation whose country, locale or time zone on record is in the EEA or the UK. Elsewhere a restriction needs an explicit acknowledgement, which is recorded against the administrator's account. A person with no location or time zone on record is treated as outside the EEA and UK, and restrictions applied before this check existed are not lifted automatically |\r\n| Deleting a capture | — | A capture that caught something it should not have | In the web application deletion is soft: the stored image remains until it is permanently deleted |\r\n| Camera, audio and screen recording plugins | Not installed | The most intrusive capture types | Each needs a separate decision and its own assessment |\r\n| AI screenshot analysis | Off | — | When on, an automated verdict on whether content appears work-related is attached to each screenshot. It is an input for a person to weigh, not a decision |\r\n\r\n**Controls that Ever Gauzy does not offer today.** No blurring or masking of screenshots; no excluded\r\napplications or websites; no per-person pause other than stopping the timer or the agent's tracking; no\r\nretention period with automatic deletion; and no log of who viewed a capture — the activity log records\r\ncreation, changes and deletions, not viewing. If your assessment depends on any of these, it cannot rely on\r\nEver Gauzy to provide it today.\r\n\r\n### What we can tell you about your own account\r\n\r\nOn request at privacy@ever.co we will tell you, for your assessment: which capture features are enabled\r\nin your workspace and their current settings, where its captured files are stored, and which sub-processors\r\nare involved.\n\n## Hosting, sub-processors and transfers\r\n\r\nThis section summarises what our [sub-processor page](https://gauzy.co/subprocessors) and\r\n[Security page](https://gauzy.co/security) say in full. Where this summary and those pages differ, those pages\r\nare the current statement and this summary is the one to correct.\r\n\r\n### Where processing happens\r\n\r\n- **Primary processing is in the European Union, on infrastructure we operate.** The Service runs on physical\r\n servers we own, in facilities we control, inside the European Union. The database and the object storage\r\n that hold Customer Personal Data are components we run, not services bought from a third party.\r\n- **Requests pass through a content delivery and security network** that terminates traffic at the edge\r\n location nearest to whoever makes the request, which can be anywhere in the world, before carrying it to our\r\n infrastructure. That provider is in the always-engaged tier of the sub-processor list.\r\n- **Off-site backup copies are held by an external object storage provider**, encrypted by us before they\r\n leave our network. The provider holds ciphertext and no key.\r\n- **Our source code, build pipeline and container images are hosted by a third party.** That is how the\r\n Service is built and deployed, not where your data is stored.\r\n\r\nThis is not multi-region hosting, and we do not describe it as such. The continuity section of the Security\r\npage explains what a site-level failure would mean.\r\n\r\n### Sub-processors\r\n\r\nThe [sub-processor list](https://gauzy.co/subprocessors) for Ever Gauzy has three tiers, and the tier\r\nmatters as much as the name:\r\n\r\n- **Tier 1 — always engaged.** In the path for every customer, with no setting that removes them. This is the\r\n Article 28 list proper.\r\n- **Tier 2 — engaged only when something brings them in**: a feature an administrator enables, an\r\n integration someone connects, a provider configured for the workspace, or a cookie category a visitor\r\n accepts. Several of them are providers that you contract with directly, under your own account.\r\n- **Tier 3 — self-hosted deployments only.** Providers the software can be configured to use in a deployment\r\n you run. We are not a processor for anything in that tier.\r\n\r\nFor each provider the list gives the purpose, the location, the categories of personal data it receives and\r\nthe transfer mechanism relied on. For your assessment, read the categories of data column against the\r\nfeatures you actually enable: a tier 2 provider is not processing your data unless the condition next to it is\r\ntrue.\r\n\r\n### Transfers outside the European Economic Area\r\n\r\nWhere a provider processes personal data outside the European Economic Area, the transfer mechanism is stated\r\nagainst it on the sub-processor list, and Schedule 3 of the Data Processing Addendum describes the mechanism\r\nand the transfer impact assessment behind it. **Where we cannot yet evidence a mechanism for a provider, the\r\nlist says \"To be confirmed\" rather than naming one.** Read those rows as an open item, and ask us at\r\nprivacy@ever.co for the current position on any provider that matters to your assessment.\r\n\r\nIf you need a copy of the safeguards for a named provider — the Standard Contractual Clauses and the modules\r\nthat apply — write to privacy@ever.co and we will send them.\n\n## Security measures\r\n\r\nThe technical and organisational measures we operate are described on our\r\n[Security page](https://gauzy.co/security) and, contractually, in Schedule 2 of the Data Processing Addendum.\r\nThe points below are the ones an assessment of monitoring data usually turns on.\r\n\r\n- **Encryption.** Traffic between users and the Service travels over TLS, and plain HTTP is redirected rather\r\n than served. Storage holding customer content, databases and backups is encrypted at rest, and off-site\r\n backup copies are encrypted before they leave our network, with keys we hold. Encryption at rest protects\r\n against the loss or theft of physical media; it does not protect data from a running system that has\r\n already decrypted it.\r\n- **Access by our personnel.** Production access uses named individual accounts, is scoped to the narrowest\r\n role that lets the work happen, and is revoked when someone no longer needs it. We access the content of a\r\n workspace only where that is necessary to operate, secure or support the Service, and we do not browse or\r\n review captured data for purposes of our own. The access-control section of the Security page describes\r\n this, including its limits for a team of our size.\r\n- **Separation between customers is logical, not physical**, unless you have separately contracted for a\r\n dedicated deployment. The product-specific part of this pack states how that separation works in\r\n Ever Gauzy.\r\n- **Backups and continuity.** Backups are held in three tiers, the last of them off-site and encrypted, and\r\n each backup ages out on its own rolling cycle within the period stated in the retention section of our\r\n [Privacy Policy](https://gauzy.co/privacy).\r\n\r\n**We do not hold a SOC 2 report of any type, and we are not certified to ISO/IEC 27001.** If any document has\r\ntold you otherwise, it is wrong. What we offer instead — the Security page, Schedule 2, answers to a security\r\nquestionnaire and evidence on request — is described on the Security page.\n\n## Questions, and a version you can cite\r\n\r\n- **A question about anything in this pack, an impact-assessment questionnaire, or a request for the current\r\n settings of your own account** — privacy@ever.co\r\n- **A request for the Data Processing Addendum, a security questionnaire, or evidence of a restore test** —\r\n legal@ever.co\r\n- **Something you think has been compromised — tell us immediately** — abuse@ever.co\r\n\r\nBy post: **Ever Technologies LTD**, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — registered in Bulgaria under company number\r\n204599535. We correspond in English.\r\n\r\n**We have not designated a Data Protection Officer under Article 37 GDPR.** dpo@ever.co is a contact\r\nchannel, monitored by the same people as privacy@ever.co, and we will not describe it as a designation. If\r\na questionnaire asks for our data protection officer, that sentence is the honest answer.\r\n\r\nThis document is version 1.0.0 of the DPIA Support Pack for\r\n[gauzy.co](https://gauzy.co), in force from 2026-10-24. It describes the Service as it\r\nstood on that date. Cite the version and the date in your assessment, and check for a newer version before\r\nyou rely on it again."
97
97
  }
@@ -8,7 +8,7 @@
8
8
  "locale": "en",
9
9
  "version": "1.0.2",
10
10
  "effectiveDate": "2026-08-02",
11
- "sha256": "646154c3d3b3e7a2babc890daa4fac8deb8b8cf9096d772bf273012b2d6e52ec",
11
+ "sha256": "1094879c7fde2bfbc439f135b15fb31dfdd6a149e6221b4db49602cf56f8e71e",
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-async/en.html",
363
- "markdown": "# Privacy Policy\n\n**Ever Async** — [async.ever.co](https://async.ever.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 the Ever Async hosted service and the websites,\napplications and application programming interfaces we make available at [async.ever.co](https://async.ever.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 [async.ever.co](https://async.ever.co) and the pages served from it.\n- The the Ever Async hosted service 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 Async — 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 Async, 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 the Ever Async hosted service 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 Async 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 Async 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://async.ever.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 the Ever Async hosted service: 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://async.ever.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 Async provides, and what its defaults are, is set out in the annex later\nin this notice.\n\n## Ever Async: what actually happens to what people write\n\n**Where this annex and a general section above differ, this annex is the accurate one for\nEver Async.**\n\nEver Async sits between a team's chat platform and its work tools. When a conversation is connected,\n**every message posted in it passes through our pipeline** — classified, then enriched by fanning the\nreferences it contains out to the connectors, then either acted on or dropped. So the honest starting\npoint is that this product sees a whole channel, including the parts of it that have nothing to do with\nwork, and including messages from people who never signed up for anything.\n\nThe rest of this annex is about what happens to that text afterwards, and the answer is unusual enough to\nlead with.\n\n### A message body is written to disk for 150 seconds, and only when a nudge is pending\n\n**There is no message-text column in our database.** The events table stores a tenant, a channel, a\nconversation, a message identifier, a thread root, an author identifier, an edit flag and a timestamp —\nand no text. The nudges table stores an author identifier and a timestamp. The contexts table stores a\ncount.\n\n**There is exactly one exception, and it is the whole of it.** When the product decides to nudge someone,\nit schedules the nudge and waits — 150 seconds in every environment we run — so the author has a chance to\nfix the message themselves. The suggested rewrite is generated when the nudge fires rather than when it is\nscheduled, so **the original message text is held in the pending-nudge record for that window**. It is\ndeleted when the nudge fires, and deleted when the author self-corrects and the nudge is cancelled.\n\nThat is the only place a chat message body persists. Everything else about a message is metadata: who\nposted, where, when, whether it was an edit, and what was extracted from it.\n\n**We are not claiming the text is never processed** — it is, in memory, for every observed message, and it\nis sent to a model provider under the conditions below. We are claiming it is not kept, and the storage\nlayer is where you can check that.\n\n### The other half of the truth: nothing expires on its own\n\n**There is no retention job in Ever Async today.** No scheduled purge, no age-based delete, nothing\nthat prunes an old row. The events, seen-event, nudge and context tables grow without bound and are\ndeleted only when the tenant is deleted.\n\nWe could print a tidy retention period here. It would not be enforced by anything, and a retention promise\nthe code does not keep is worse than an uncomfortable fact. **The metadata described above is kept until\nthe tenant is deleted, and there is no automatic expiry.** Introducing one is work we intend to do, and\nwhen it exists this table will say what it does.\n\n### What is held, grouped by where it comes from\n\n- **From every message in a connected conversation** — the plain-text body, in transit through the\n pipeline; the author's chat user identifier; the identifiers of anyone they mentioned; any URLs they\n posted and the references extracted from the message; the workspace or guild identifier, the\n conversation identifier, the message identifier and the thread root; the timestamp and whether it was an\n edit.\n- **In memory only, never written to a table** — the author's display name and whether the account is a\n bot.\n- **From a pending nudge** — the original message text, for the grace window described above.\n- **From the connectors** — what they return: pull request, issue and task titles, states and URLs, and\n the names of their authors and assignees.\n- **From counters** — per-tenant totals of messages observed, nudges sent and context items attached.\n- **From sign-in** — see the next section, because it is shorter than you expect.\n- **From the workspace itself** — the tenant record, memberships and roles, the workspace binding, the\n policy settings and the charter text.\n\n### Sign-in holds less than almost any product we run\n\n**There is no email column anywhere in the schema.** That is not a rounding of the truth, it is the shape\nof the database.\n\n- **Single sign-on.** Where you sign in through Slack, Discord, GitHub, Google or Ever Gauzy, the provider\n returns a provider user identifier, a verified email address and a display name. **The email address and\n the name are held in an in-memory session and are lost when the process restarts.** The only piece that\n reaches a database is the provider user identifier, on the memberships record with the tenant and the\n roles.\n- **Local accounts.** These are supplied to the deployment as an environment variable containing an email\n address and an Argon2id password hash. They are never written to a database.\n- **API tokens.** Static tokens of the form user id, role and secret, also supplied as an environment\n variable.\n\nThe practical consequence: **we usually cannot tell you a person's email address from our own records,\nbecause we do not have it.** A rights request that identifies a person by email may need the chat user\nidentifier as well, and we will say so rather than guess.\n\n### The Gauzy user map: a chat identity wired to an employee record\n\n**This is the sharpest disclosure in the product, so it has its own heading.**\n\nThe Ever Gauzy connector takes a static map from a chat user identifier to an Ever Gauzy employee\nidentifier. **It is a direct link between somebody's chat account and their HR record**, configured by an\nadministrator, without the employee being asked or necessarily told. It is what makes a phrase like \"my\nlast task\" resolvable.\n\n- **The customer configures it, and the customer is the controller of it.** We hold the map because they\n put it in their configuration.\n- **Once a request crosses into Ever Gauzy, that is a separate service** with its own privacy notice, and\n that notice governs what happens there.\n- If a map entry about you exists and you did not know, **ask the organisation that runs the workspace\n first** — it is theirs. Write to privacy@ever.co if that gets you nowhere and we will help you reach\n them.\n\nNot configured, no map, no linkage: the connector simply does not resolve personal references.\n\n### What leaves for a model provider, and exactly when\n\nThe prompt is not a mystery: **the classification prompt embeds the message text verbatim** alongside a\nlink count and a mention count, and the rewrite prompt adds the resolved context items and **the\nworkspace's charter**.\n\n| Configuration | Does the message text leave? |\n|---|---|\n| No `[llm]` provider configured | **No.** Classification runs on plain heuristics and nothing is sent anywhere |\n| Provider configured, sensitivity **conservative** | **No.** The model is never consulted at this setting |\n| Provider configured, sensitivity **balanced** or **high** | **Yes** — but only for the ambiguous middle of the classifier's range, and only to the provider you configured |\n| Provider is a local runtime you run | **No.** The text stays inside the deployment |\n\nTwo things follow that people do not expect:\n\n- **The charter goes with every one of those calls.** A team that writes customer names, staff names or\n case references into its charter sends them to its model provider on every classification. Write the\n charter as though it were the prompt, because it is.\n- **The routing can be indirect.** A model router forwards the request to whichever upstream provider the\n selected model resolves to, and the generic compatible-endpoint adapter will send to any base URL an\n operator configures. Each named provider is in the [Sub-processor List](https://async.ever.co/subprocessors)\n with its location and its transfer mechanism, and some of those mechanisms read **\"To be confirmed\"** —\n which is us saying we have not yet evidenced one, rather than us implying we have.\n\n**We do not use your messages, your prompts or the output to train models**, and our contracts with the\nproviders we engage prohibit them from doing so.\n\n### What is running on the hosted service today\n\nBecause it changes the answer to nearly every question above, it is worth stating rather than leaving to\nbe inferred: **in the environments we operate today, no chat platform is connected, no connector is\nconfigured, no model provider is configured and no notification provider is configured.** The service runs\nwith authentication on, a local database, and sensitivity set to conservative.\n\nSo today, on our hosted service, **no chat message data flows at all.** That will change the moment a\nworkspace connects, which is exactly when everything above starts to apply. It is also why our\nsub-processor list has only three entries in its always-engaged tier, and why the rest are in the tier\nthat depends on what you switch on.\n\n### People in a connected channel who never signed up\n\nAlmost everyone whose data this product touches is in this position: they posted in a channel their\nemployer connected. Article 14 of the GDPR entitles them to be told, and this section is that notice as\nwell as an explanation to the customer.\n\n- **What is held about you.** Your chat user identifier, the fact and timing of your messages in a\n connected conversation, the references and links inside them, who you mentioned, and — for at most the\n grace window, and only if a nudge was scheduled — the text of the message itself.\n- **Where it came from.** Your employer's or your community's chat workspace, connected by an\n administrator of it. **We did not obtain it from you.**\n- **Who decides.** The organisation that connected the workspace is the controller. We are its processor.\n **Ask it first**, and our [Data Processing Addendum](https://async.ever.co/dpa) is what obliges it to answer.\n- **What it is for.** Attaching context to a conversation and privately suggesting a clearer message to\n the person who wrote it.\n- **The nudge is private.** It goes to you and to nobody else. No manager sees it, there is no report of\n who was nudged how often beyond a per-tenant count, and nothing is escalated.\n\nIf a request reaches us directly we will forward it to the organisation, tell you who they are so you can\npursue it, and assist them — but **we will not decide it for you or for them**. Write to\nprivacy@ever.co; you do not need an account and it costs nothing.\n\n### Special categories, and why we do not pretend to filter\n\nA chat channel cannot be filtered in advance. **Health, religion, politics, trade union matters and purely\nprivate business will appear in a connected conversation**, because that is what channels contain. The\nproduct does not seek any of it, does not classify it and **does not detect and strip it** — saying\notherwise would be untrue.\n\nThe protections that actually exist are the ones described above: the body is not stored, the metadata is\nnarrow, and which conversations are connected is a choice the customer makes. Connecting a general channel\nrather than a work-tracking one is the decision that matters most here.\n\n### How long we keep the things that are specific to this product\n\nThese sit alongside the general retention table above; where both could apply, the shorter period wins.\n\n| What | How long |\n|---|---|\n| The text of a chat message | **Not stored.** In memory during processing only |\n| The text of a message with a nudge pending | **The grace window — 150 seconds in every environment we run** — then deleted when the nudge fires or is cancelled |\n| Event metadata: author id, conversation, message id, thread root, edit flag, timestamp | Until the tenant is deleted. **There is no automatic expiry today** |\n| Deduplication records of messages already seen | Until the tenant is deleted |\n| Nudge records: author id and timestamp | Until the tenant is deleted |\n| Context records: a count of items attached | Until the tenant is deleted |\n| Per-tenant counters | Until the tenant is deleted |\n| Sign-in session, including verified email address and display name | **In memory only** — lost when the process restarts or you sign out |\n| Membership record: provider user id, tenant, roles | Until removed from the workspace, or until the tenant is deleted |\n| Charter text, policy settings and workspace bindings | Until changed or until the tenant is deleted |\n| The Gauzy user map | Until the customer changes it or the tenant is deleted |\n| Credentials for a connector or a model provider | Until the customer removes them |\n\nDeleting a tenant deletes everything above for that tenant. Backups age out on the cycle in the general\nretention table and are not restored to bring back something we were asked to delete.\n\n### What is deliberately not here\n\nStated affirmatively rather than left to be inferred from an absence, because an absence is not evidence:\n\n- **No analytics.** Not a third-party tag, and not the first-party cookieless tool some of our other\n products run. Nothing measures your use of this product.\n- **No error tracking or session replay.** No crash reporter, no performance monitor, no reconstruction of\n what was on anyone's screen.\n- **No advertising, no retargeting, no enrichment, no data broker.** Nothing about a message, an author or\n a workspace is used to target anything, anywhere.\n- **No profiling of individuals.** There is no score, no ranking and no per-person record of behaviour\n beyond the metadata listed above. The classifier judges a message, not a person.\n- **No human reading your channels.** Nobody here reads a connected conversation, except where you ask us\n for support and point us at something specific, or where we must to investigate a security incident or\n comply with a legal obligation — and in the last case we tell you unless we are prohibited from doing\n so.\n\nIf any of that changes, it is named in this annex before it runs, not after.\n\n### Exercising your rights here, honestly stated\n\n- **The narrow schema helps you.** There is very little to export, and a tenant delete really does remove\n it.\n- **There is no self-service delete button today, and we are not going to pretend otherwise.** Write to\n privacy@ever.co and we will do it and answer you within one month.\n- **Where an organisation connected the workspace, most requests belong to that organisation**, and we\n route them there. The rights section above explains that routing; this annex is where you can see why it\n applies to nearly everyone whose data is in this product.\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://async.ever.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[async.ever.co](https://async.ever.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://async.ever.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, reverse proxy and TLS termination for every Ever Async hostname — the marketing site, the dashboard, the API and the webhook ingress. TLS is terminated at the edge and there is no certificate in our own pods, so every request to the Service passes through it and no setting removes it. | United States, with your connection terminated at the edge location nearest to you | Standard Contractual Clauses (EU 2021/914) | IP address, TLS and connection metadata, request URLs and headers, user agent, cookies in transit |\n| GitHub, Inc. (a Microsoft Corporation company) | Holds the source, runs the build, and is the container registry the running images are pulled from (ghcr.io/ever-co/everasync and ghcr.io/ever-co/everasync-docs). This is how the Service is built and shipped rather than where message data lives — but it is a genuine third party and it is disclosed as one. | United States, with global edge delivery for registry and release downloads | Standard Contractual Clauses (EU 2021/914) | source, build, release and deployment metadata, developer and automation account identifiers, IP address and user agent of anyone pulling an image or a release |\n| Cloudflare, Inc. (R2 object storage) | Third tier of our backup chain, holding the off-site copy of the volumes this product's database sits on. Everything bound for it is encrypted by us before it leaves our network, so the provider holds ciphertext and no key and cannot read what it stores. | Cloudflare R2 buckets | Standard Contractual Clauses (EU 2021/914) | client-side encrypted backup archives only, which no third party can read, the archives derive from every category of data the Service holds |\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| ActiveCampaign, LLC (Postmark) | Relays every transactional email a product sends - account invitations, verification and sign-in codes, invoices, approvals - and on ever.co also carries contact-form enquiries with PDF attachments, so CVs and the third parties named inside them reach a US processor. | United States | Standard Contractual Clauses (EU 2021/914) | recipient name and email address, full message subject and body - invitations, verification and sign-in codes, invoices, timesheets, HR and approval content, free-text enquiry content and attached CVs from website contact forms, anyone NAMED inside that free text or attachment, delivery, bounce and open metadata |\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| 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| Functional Software, Inc. d/b/a Sentry | Captures application errors, performance traces and - on the tenant site template - masked session replays, attaching the reporting user's identity and IP to each event. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, device and OS details, user id and email attached to an error event or set on the scope, URLs, route params, query strings and stack traces, which can carry request fragments and local variables, masked session replay recordings (maskAllText, blockAllMedia), desktop and mobile crash dumps |\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| Google Ireland Limited (reCAPTCHA) | Scores whether the person submitting a signup, login or contact form is human, loading on the form page before any consent choice is made. | Ireland (contracting entity); processing in Ireland (contracting) / United States (onward processing by Google LLC) | Standard Contractual Clauses (EU 2021/914) | IP address, user agent and device characteristics, mouse, touch and timing signals from the form page, cookies set on google.com |\n\nThe full and current list, including everything below, is published at\n[https://async.ever.co/subprocessors](https://async.ever.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://async.ever.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://async.ever.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 [async.ever.co](https://async.ever.co), turn off the categories you no longer want, and save. The change\n takes effect immediately. Details are in our [Cookie Policy](https://async.ever.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://async.ever.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://async.ever.co/privacy](https://async.ever.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[async.ever.co](https://async.ever.co), in force from 2026-08-02. Earlier versions, with the\ndates they applied, are at [https://async.ever.co/privacy](https://async.ever.co/privacy)."
363
+ "markdown": "# Privacy Policy\r\n\r\n**Ever Async** — [async.ever.co](https://async.ever.co)\r\n\r\nVersion 1.0.2 · In force from 2026-08-02\r\n\r\nThis notice explains what we do with personal data when you use the Ever Async hosted service and the websites,\r\napplications and application programming interfaces we make available at [async.ever.co](https://async.ever.co)\r\n(together, the \"**Service**\"). It tells you what we collect, why, who else sees it, how long we keep it,\r\nand what you can ask us to do about it.\r\n\r\nWe have written it to be read rather than to be defended. Where something is uncomfortable — data we hold\r\nthat you never gave us, or data your employer decides to collect through our software — we say so plainly\r\ninstead of burying it in a list.\r\n\r\n## What this notice covers\r\n\r\n- The website at [async.ever.co](https://async.ever.co) and the pages served from it.\r\n- The the Ever Async hosted service web application, together with any desktop application, mobile application or\r\n browser extension we publish for it.\r\n- The application programming interfaces and integrations we operate for it.\r\n- The emails, notifications and support conversations that go with it.\r\n\r\nA product-specific annex appears later in this notice. It adds detail for Ever Async — what it\r\nactually collects, what is switched off by default, and which controls exist. It sits on top of this\r\nnotice rather than instead of it, and where it is more specific about Ever Async, the annex governs.\r\n\r\n## What this notice does not cover\r\n\r\n**Other companies' products.** Other companies operate their own websites, products and services, and\r\npublish their own privacy notices. This notice covers only what is listed above. If a service is not on\r\nthat list, this notice does not apply to it — whatever it looks like, and whoever links to it.\r\n\r\n**Software you run yourself.** Some of our software is published as open source and can be installed on\r\nyour own infrastructure. **If you run your own deployment, you are the controller of the personal data in\r\nit — not us.** You choose its hosting, its storage, its email provider and every other component. We have\r\nno access to that data, we do not process it, we are not your processor for it, and nothing in this notice\r\ndescribes it. Telling your own users what happens in your deployment is your job, not ours.\r\n\r\n**Sites we link to.** The Service links out to third-party websites and services. Once you follow a link\r\naway from us, the operator of that site decides what happens to your data. We do not control those sites,\r\nwe do not receive what you do on them, and we are not responsible for them. Read their notices, not this\r\none.\r\n\r\n**Your organisation's own systems.** Where your employer or another organisation uses the Service, it also\r\nruns systems of its own. This notice covers our part. Its notice covers its part.\n\n## Who we are\r\n\r\nThe controller of the personal data described in this notice is **Ever Technologies LTD**, a company\r\nregistered in Bulgaria under company number 204599535, with its registered office\r\nat Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria.\r\n\r\n\"Controller\" is the legal term for the organisation that decides why personal data is used and how.\r\nWherever this notice says we make that decision, **Ever Technologies LTD is the organisation accountable to\r\nyou** — and to the Commission for Personal Data Protection (Комисия за защита на личните данни) (CPDP), which\r\nis our lead supervisory authority.\r\n\r\nEver Technologies LTD operates the Ever Async hosted service and is the company you contract with for it. There\r\nis no other operator behind us and no second company you have to chase to get an answer.\r\n\r\nYou can reach us about anything in this notice at privacy@ever.co, or by post at the registered office\r\nabove.\r\n\r\nThere are parts of this notice where we are deliberately **not** the controller: where a customer puts\r\npersonal data about its own people into the Service, that customer decides, and we act on its instructions.\r\nThat split matters, so it has its own section below.\n\n## Other companies in our group\r\n\r\nThere is one other company in our group, and its role is narrow enough to state in a sentence.\r\n\r\n**Ever Co. LTD**, a company registered in Israel under company number\r\n515241842, with its registered office at HaAtsmaut 32/3, Ashdod 77452, Israel, owns the intellectual\r\nproperty in the software. Ever Technologies LTD operates the Service under licence from it.\r\n\r\nThat is the entire relationship. Its consequences are worth stating positively rather than leaving you to\r\nwork them out:\r\n\r\n- **Ever Co. LTD does not access personal data held in the Service.** No administration console,\r\n no production database, no support tooling, no backups, no error reports.\r\n- It is **not a controller** of that data, **not a processor** of it, and **not a sub-processor**. It does\r\n not appear on our sub-processor list, because there is nothing for it to appear against.\r\n- **No personal data is transferred to it.** No international transfer to Israel arises out of\r\n your use of the Service, because none happens.\r\n\r\nOwning software is not the same as having access to the data that software holds, and we have kept the two\r\napart on purpose.\r\n\r\nIf that ever changes — if Ever Co. LTD were to take on any role involving personal data from the\r\nService — we would update this notice before it happened, name the role, disclose the transfer and the\r\nsafeguard we relied on, and add it to our sub-processor list. **Until you read that here, none of it is\r\nhappening.**\n\n## Data protection contact\r\n\r\n**We have not designated a Data Protection Officer.** Article 13(1)(b) of the GDPR asks a controller to\r\npublish a Data Protection Officer's contact details where one has been designated. None has been designated\r\nat Ever Technologies LTD, so there are none to publish. We would rather tell you that outright than let a\r\nmailbox name imply otherwise. We keep the question under review, and if it changes we will publish the\r\ndetails here.\r\n\r\nWhat we do publish is a contact route that is monitored and acted on. **Privacy questions and requests to\r\nexercise your rights are handled through these addresses:**\r\n\r\n- **privacy@ever.co** — use this for anything about this notice, about the personal data we hold, or to\r\n make a request under any of your rights.\r\n- **dpo@ever.co** — an alias that reaches the same people. It exists because procurement forms,\r\n security questionnaires and privacy tooling routinely expect an address in that form. **It is a routing\r\n alias, not an office. Nothing about it means a Data Protection Officer has been designated.**\r\n\r\nYou can also write to us by post at the registered office given above.\r\n\r\nWe will acknowledge your message, and we will answer a request to exercise your rights within one month —\r\nthe deadline the GDPR sets. Where a request is genuinely complex, or where you have made several, we may\r\nextend that by up to two further months. If we do, we will tell you inside the first month and explain\r\nwhy.\n\n## Who decides what: controller and processor\r\n\r\nData protection law splits responsibility in two. The **controller** decides why personal data is used and\r\nhow. The **processor** only acts on the controller's instructions. Which of the two we are is not a\r\nformality — it decides who you go to, who has to answer you, and who is accountable when something goes\r\nwrong.\r\n\r\nOur position depends on whose data it is. There are three cases. We set them out here, in the privacy\r\nnotice, rather than leaving them to a data processing agreement, because the person most affected by the\r\nsecond case is usually the person least likely to read a contract.\r\n\r\n### 1. Our own relationship with you — we are the controller\r\n\r\nWhere we decide, we are accountable. **We are the controller** for:\r\n\r\n- registration and account identity — the name, email address and credentials used to create and hold an\r\n account;\r\n- billing, payments, invoices, tax records and collections;\r\n- support conversations, including the tickets, emails, chats and attachments themselves;\r\n- security, fraud prevention, abuse handling and audit logging;\r\n- our own websites and their analytics, our newsletters, and our marketing to prospective customers; and\r\n- running our business — accounting, insurance, professional advice, and defending claims.\r\n\r\nEverything in this notice about purposes, legal bases, retention, transfers and your rights applies to this\r\nfirst case directly, and you exercise those rights against us.\r\n\r\n### 2. Personal data a customer puts into the Service about its own people — the customer is the controller\r\n\r\nWhen an organisation subscribes to the Service and uses it to run its business, the personal data it puts\r\nin is **its** data. It decides what to collect, which features to switch on, why, and for how long to keep\r\nit. **We process that data only on that organisation's instructions.** For it, the organisation is the\r\ncontroller and we are the processor.\r\n\r\nThis covers the ordinary contents of a workspace — employee and contractor records, contact details,\r\nprojects, tasks, documents and messages. It also covers the parts that matter most, where a product\r\nprovides them and the customer has enabled them:\r\n\r\n- **time-tracking data** — timers, timesheets, time entries and the records behind them;\r\n- **activity data** — how much keyboard and mouse activity occurred in a period, idle time, and which\r\n applications and websites were in use;\r\n- **screen and media capture** — periodic screenshots and, where separately switched on, webcam stills,\r\n audio recordings and screen recordings.\r\n\r\n**We do not decide to collect any of this. The customer does.** We build the features, we document what\r\neach one captures and what each control does, and we run them exactly as the customer configures them. We\r\ndo not use that data for our own purposes, we do not use it to train models, and we do not look at it\r\nexcept where we must in order to run, secure or support the Service.\r\n\r\nWhat Ever Async can capture, what is off by default, and which controls exist is set out in the annex\r\nlater in this notice.\r\n\r\n### 3. Data a customer holds about its own clients and end users — the customer is the controller\r\n\r\nWhere a customer uses the Service to serve its own clients, members, applicants, patients or website\r\nvisitors, that data sits in the same arrangement as case 2. The customer is the controller, we are the\r\nprocessor, and the customer owes those people the notice and the answers. If you have dealt with an\r\norganisation and want to know what it holds about you, ask that organisation.\r\n\r\n### If you are monitored at work, this part is for you\r\n\r\nWe would rather tell you directly than make you work it out from a contract you have never seen.\r\n\r\n**Your employer decides what is captured. We do not.** Screenshots, activity rates, application and website\r\nusage, webcam stills, audio, screen recordings — each of these is a setting your employer switches on or\r\nleaves off, for the organisation and, where the product allows it, for individual people. We cannot switch\r\nthem on for your employer, and we do not switch them on for ourselves.\r\n\r\n**Your employer is the controller of that data.** That means your employer, not us:\r\n\r\n- must have a lawful basis for monitoring you, under the GDPR and under its own national employment law,\r\n which differs sharply from country to country;\r\n- must tell you, before it starts, what is captured, how often, why, and how long it is kept;\r\n- must carry out a data protection impact assessment where one is required, and act on what it finds;\r\n- must consult a works council, employee representatives or a trade union where its national law requires\r\n that; and\r\n- must answer your requests about that data.\r\n\r\n**We make no claim that monitoring employees is lawful across the European Union, because it is not.** Some\r\ncountries restrict it tightly, some require consultation before it starts, and some prohibit particular\r\nforms of it outright. Whether your employer's use of these features is lawful where you work is your\r\nemployer's responsibility. We require every customer to confirm to us that it has dealt with each of the\r\npoints above before it uses these features.\r\n\r\n**How to exercise your rights over monitoring data.** Send your request to your employer — it holds the\r\ndata and it has to answer you. If you send it to us instead, we will not ignore it:\r\n\r\n- we will forward it promptly to the customer whose workspace holds the data;\r\n- we will tell you that we have done so, and to whom, so you are not left waiting on silence; and\r\n- we will help that customer find, correct, export or delete the data, which is what our contract with it\r\n requires of us.\r\n\r\n**What we will not do is release one organisation's data to someone else on request.** We cannot verify an\r\nemployment relationship from the outside, and handing over a workspace's contents to a person the customer\r\nhas not authorised would be a breach in its own right. That restraint protects you as much as it\r\nconstrains you.\r\n\r\nIf you think your employer is monitoring you unlawfully, you can complain to the data protection authority\r\nin your own country, and to your national labour authority. You do not need our permission, and you do not\r\nneed to come through us first.\n\n## Personal data we collect\r\n\r\nWe group this by where the data comes from, because that is what determines what we know about you and what\r\nwe owe you.\r\n\r\nNot every category applies to every product, plan or user. This section describes the shape of what we\r\ncollect; the annex later in this notice lists what Ever Async actually collects.\r\n\r\n### What you give us\r\n\r\n- **Account identity** — your name, username, email address, password (held only as a hash), profile\r\n picture, job title, preferred language and time zone.\r\n- **Organisation details** — the organisation you belong to, your team, your role and permissions within\r\n it, and who invited you.\r\n- **Contact details** — email address, telephone number and postal address, where you provide them.\r\n- **Billing details** — billing name and address, VAT or tax identification number, the plan you are on,\r\n invoices and payment history. **We do not receive or hold your full card number** — that goes straight to\r\n our payment processor.\r\n- **Support correspondence** — the tickets, emails, chat messages, screenshots and files you send when you\r\n ask for help, and our replies.\r\n- **Content you submit** — everything you or your organisation puts into the Service: documents, tasks,\r\n projects, records, messages and uploads. Where that content belongs to your organisation, we hold it as\r\n processor, not as controller.\r\n- **Anything else you volunteer** — survey answers, feedback, event registrations, newsletter sign-ups, and\r\n whatever you choose to write to us.\r\n\r\n### What we collect automatically when you use the Service\r\n\r\n- **Device and browser data** — device type, operating system, browser and version, screen size, language,\r\n and the version of our application you are running.\r\n- **Connection data** — your IP address, and the approximate location it indicates. **That is\r\n city-or-region level, derived from the IP address**, and it is not satellite positioning. Where a\r\n specific feature collects precise location, it says so.\r\n- **Usage data** — pages and screens viewed, features used, actions taken, navigation paths, timestamps and\r\n the page that referred you.\r\n- **Logs** — server and application logs of requests, errors, response times, sign-ins, failed sign-ins and\r\n administrative actions, with the identifiers needed to tie an entry to an account.\r\n- **Diagnostics** — crash reports, stack traces and performance traces. These can incidentally contain\r\n whatever was in the request that failed.\r\n- **Cookies and similar technologies** — cookies, local storage, pixels, software development kit\r\n identifiers and comparable device storage. What each is for, and which ones need your consent, is in our\r\n [Cookie Policy](https://async.ever.co/cookies).\r\n\r\n### What we receive from other people\r\n\r\n- **Identity providers** — if you sign in with a third-party account, we receive that account's identifier,\r\n your email address, your display name and usually your profile picture, plus confirmation that the\r\n sign-in succeeded. **We never receive your password for it.**\r\n- **Payment processors** — whether a payment succeeded or failed, the payment method type, the last four\r\n digits and expiry of a card, the billing country, and any dispute or chargeback.\r\n- **Integrations you or your administrator connect** — whatever the connected service returns within the\r\n permissions granted. That varies by integration and is shown to you when you authorise it.\r\n- **Your organisation** — where an administrator creates your account, invites you, sets your role or\r\n imports records about you.\r\n- **Other sources**, where a particular product uses them. Those are set out in the next section and in the\r\n annex.\r\n\r\n### What you have to give us\r\n\r\nSome of it is unavoidable. Without account identity we cannot create an account for you; without billing\r\ndetails we cannot take payment for a paid plan; without certain records we cannot meet our own legal\r\nobligations. Where data is necessary in that sense, **not providing it means we cannot provide that part of\r\nthe Service** — but nothing worse follows.\r\n\r\nEverything else — an optional profile field, a newsletter subscription, an integration you could simply not\r\nconnect — is genuinely optional, and declining it costs you nothing.\n\n## Data we do not collect\r\n\r\nShorter than the previous section, and just as binding. These are commitments about how the Service is\r\nbuilt, not aspirations.\r\n\r\n- **We do not sell personal data.** Not to data brokers, not to advertisers, not to anyone — and not under\r\n the broader definitions of \"sell\" or \"share\" used outside the European Union.\r\n- **We do not buy marketing lists.** If we contact you about our products it is because you gave us your\r\n details, or because you are already a customer. We do not purchase your name from someone else in order\r\n to email you.\r\n- **We do not use your content to train machine-learning models** — not for our own purposes, and not for\r\n the benefit of other customers. Where a product has an AI feature, it processes your content to produce\r\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\r\n choose, described before you choose it.\r\n- **We do not run advertising inside the Service.** No third-party advertising, no behavioural ad\r\n targeting, no cross-site advertising identifiers in the product.\r\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.**\r\n- **We do not ask for special-category data** — health, racial or ethnic origin, religious or philosophical\r\n beliefs, political opinions, trade union membership, sex life or sexual orientation, genetic or biometric\r\n data. There are no fields for it, we do not infer it, and we do not want it. The one honest caveat is\r\n about what can end up inside a screenshot, and it has its own section below.\r\n- **We do not store full card numbers or card security codes.** Those are entered on our payment\r\n processor's systems and never reach ours.\r\n- **We do not collect precise location by default.** Where a product uses location at all, it is because a\r\n specific feature needs it, and that feature says so.\r\n\r\nIf you find any of this to be untrue of something we ship, tell us at privacy@ever.co. We will treat it\r\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\r\n\r\nNot all of the personal data we hold came from you. Article 14 of the GDPR requires us to tell you where it\r\ncame from, and this section does that.\r\n\r\n- **Your employer, or the administrator of your workspace.** Where an organisation subscribes to the\r\n Service, an administrator creates accounts, invites people, sets roles and imports records. That supplies\r\n your name, work email address, job title, team, role and permissions, and whatever else the organisation\r\n chooses to hold about you in its workspace. **For that data the organisation is the controller**, as set\r\n out above.\r\n- **Identity providers.** If you sign in with a third-party account, that provider supplies the account\r\n identifier, your email address, your display name and usually a profile picture, and confirms the sign-in\r\n succeeded. It supplies nothing else, and never a password.\r\n- **Integrations you or your administrator connect.** A connected service supplies whatever the permissions\r\n you granted allow — for example issues and repositories from a code host, messages and channel names from\r\n a chat tool, calendar entries, contacts, or records from another business system. The scope is shown when\r\n the connection is authorised, and it can be revoked in the same place.\r\n- **Payment processors and resellers.** They supply the outcome of a payment, the payment method type, the\r\n last four digits and expiry of a card, the billing country, and any dispute or chargeback. They do not\r\n pass us the card itself.\r\n- **Publicly available sources, where a product builds profiles from them.** Some products work with\r\n information people have published themselves — a public code-hosting profile, a public company page, a\r\n public professional listing. Where a product does this, the annex names the categories taken and the\r\n sources they came from, explains the basis we rely on, and says how to object. **If we hold a profile\r\n about you that you never gave us, you can object to it and we will act on that.**\r\n- **Service providers acting for us.** Fraud and abuse signals, delivery and bounce information from the\r\n systems that send our email, and security intelligence about addresses and networks.\r\n\r\nWhere we are the controller of personal data that did not come from you, we will tell you within a\r\nreasonable period and at the latest within one month of obtaining it — or, if we use it to contact you, at\r\nthat first contact. Where informing every individual separately would take disproportionate effort, this\r\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\r\n\r\nArticle 6 of the GDPR requires a lawful basis for each purpose. So this is one row per purpose, rather than\r\na general list of all six bases — you can check us against each line.\r\n\r\n| Purpose | Personal data used | Lawful basis |\r\n|---|---|---|\r\n| Providing the Ever Async hosted service: 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 |\r\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) |\r\n| Keeping accounting, tax and invoicing records | Invoices, payment records, billing identity | **Legal obligation** — Art 6(1)(c), under tax and accounting law |\r\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 |\r\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 |\r\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 |\r\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://async.ever.co/cookies) |\r\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 |\r\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 |\r\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) |\r\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 |\r\n\r\nTwo things this table deliberately does not cover.\r\n\r\n**Where we act as processor**, the lawful basis is not ours to pick. The customer that put the data into\r\nthe Service decides the purpose and must have its own basis for it. See the controller and processor\r\nsection above.\r\n\r\n**Where we rely on your consent**, you can withdraw it at any time, and withdrawing it is as easy as giving\r\nit. Withdrawing consent does not make earlier processing unlawful — it stops the processing from that point\r\non.\n\n## The legitimate interests we rely on\r\n\r\nWhere the table above says \"legitimate interests\", the law requires us to tell you what that interest\r\nactually is — not simply to name the basis and move on. For each one we have asked three questions: what is\r\nthe interest, is the processing genuinely necessary for it, and is it fair to you. That last question is\r\nthe balancing test, and we keep a written record of it.\r\n\r\n### Keeping the Service and its users secure\r\n\r\n- **The interest:** preventing unauthorised access, account takeover, fraud, spam, denial-of-service and\r\n abuse of the Service.\r\n- **Why the processing is necessary:** you cannot see an attack without looking at the traffic. Sign-in\r\n records, IP addresses, device data and request logs are what make an intrusion visible at all.\r\n- **Why it does not override your rights:** the data is limited to what security work needs, it is kept for\r\n a bounded period, and the benefit goes to the same accounts and the same people whose data is used. Nobody\r\n reasonably expects a service to be run without security logging.\r\n\r\n### Keeping the Service running\r\n\r\n- **The interest:** operating a reliable service — monitoring, error tracking, debugging, capacity planning\r\n and backups.\r\n- **Why the processing is necessary:** faults surface in logs, and a crash report is only useful if it\r\n records what was happening when the crash occurred.\r\n- **Why it does not override your rights:** it is operational data, kept for short periods, used to fix\r\n software rather than to form views about people, and reachable only by the staff who need it.\r\n\r\n### Understanding how the Service is used\r\n\r\n- **The interest:** knowing which features are used, where people get stuck, and what to build or fix next.\r\n- **Why the processing is necessary:** the alternative is guessing. Aggregate usage data is the only\r\n practical way to see this without interrogating every user.\r\n- **Why it does not override your rights:** we analyse it in aggregate rather than to make decisions about\r\n you individually, and wherever cookies or similar device storage are involved we ask for your consent\r\n instead of relying on this interest at all.\r\n\r\n### Answering people who write to us without an account\r\n\r\n- **The interest:** replying to a question from someone who is not a customer.\r\n- **Why the processing is necessary:** we cannot answer you without keeping your message and your address.\r\n- **Why it does not override your rights:** you chose to contact us, we use it only to answer, and we keep\r\n it no longer than the matter and any follow-up require.\r\n\r\n### Telling existing customers about our own similar products\r\n\r\n- **The interest:** letting people who already buy from us know about the products next to the one they\r\n bought.\r\n- **Why the processing is necessary:** it uses the address they gave us during that sale, and there is no\r\n less intrusive way to reach them.\r\n- **Why it does not override your rights:** it is confined to our own similar products, every message\r\n carries a one-click opt-out, and an opt-out is acted on immediately and permanently.\r\n\r\n### Running and protecting our business\r\n\r\n- **The interest:** accounting, audit, insurance, professional advice, complaints, disputes, enforcing our\r\n terms, and evaluating or completing a corporate transaction.\r\n- **Why the processing is necessary:** these are ordinary obligations of operating a company, and each one\r\n needs the records that relate to it.\r\n- **Why it does not override your rights:** the data is confined to the matter in hand, access is narrow,\r\n and a great deal of it we are required to keep in any event.\r\n\r\n### Your right to object\r\n\r\n**You can object to any processing we base on legitimate interests, at any time, by writing to\r\nprivacy@ever.co.** Tell us which processing, and where you can, why — your particular situation is part\r\nof the balance. We will stop unless we can show compelling legitimate grounds that override your interests,\r\nrights and freedoms, or unless we need the data to establish, exercise or defend legal claims.\r\n\r\n**If you object to direct marketing there is no balancing at all. We stop.** That right is absolute.\r\n\r\nYou can also ask us for a summary of the balancing test behind any interest listed above, and we will give\r\nyou one.\n\n## Special categories of data\r\n\r\nSome personal data carries extra protection under Article 9 of the GDPR: data revealing racial or ethnic\r\norigin, political opinions, religious or philosophical beliefs or trade union membership, and genetic data,\r\nbiometric data used to identify someone, data concerning health, and data about a person's sex life or\r\nsexual orientation. Data about criminal convictions and offences is restricted separately, under Article 10.\r\n\r\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\r\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\r\nsupport ticket either — if you need to show us something sensitive to get help, redact it first.\r\n\r\n### The honest caveat: incidental capture\r\n\r\nWhere a customer switches on screen capture, webcam capture or audio capture, **what gets captured is\r\nwhatever is there**. A screenshot taken while someone has a hospital appointment email open captures health\r\ndata. A webcam still can show a religious head covering. An audio recording can pick up a background\r\nconversation that has nothing to do with work.\r\n\r\nThat is not a theoretical risk and we will not present it as one. It is a direct consequence of capturing a\r\nscreen or a room on a timer, and it is true of every product that does it, ours included.\r\n\r\n### Whose responsibility it is\r\n\r\n**The customer that switches these features on is the controller of what they capture**, including anything\r\nspecial-category that comes with it. So the customer, not us:\r\n\r\n- decides whether to enable capture at all, and has to judge whether the benefit justifies the intrusion;\r\n- must carry out a data protection impact assessment before starting, and act on what it finds — capture of\r\n this kind will normally require one;\r\n- must have a lawful basis, and where special-category data is realistically in scope must also satisfy\r\n Article 9(2), which an employee's consent rarely does on its own, because of the imbalance between\r\n employer and employee;\r\n- must configure the product to reduce that risk rather than accept it; and\r\n- must deal with what has been captured, including deleting a capture that should never have been taken.\r\n\r\nWe are the processor for it. We do not decide to capture anything, we do not review captures for our own\r\npurposes, and we act on the customer's configuration and instructions.\r\n\r\n### The levers, and using them\r\n\r\nWhere a product offers screen or media capture, it also offers controls that materially reduce this risk.\r\nDepending on the product, those include:\r\n\r\n- switching capture off entirely, for the whole organisation or for an individual person;\r\n- switching off the more intrusive capture types — webcam stills, audio and screen recording — while\r\n keeping the rest;\r\n- reducing how often captures are taken;\r\n- blurring captured images;\r\n- shortening how long captures are kept, and deleting them automatically at the end of that period;\r\n- letting people see what has been captured about them; and\r\n- deleting an individual capture.\r\n\r\n**If you are a customer, these are yours to set, and the defaults are not a recommendation.** Choose the\r\nleast intrusive configuration that meets the purpose you actually have, and write down why you chose it.\r\nThat record is what a supervisory authority will ask for.\r\n\r\n**If you are being monitored and something sensitive has been captured, ask your employer to delete it.**\r\nYour employer can do that in the product. If you tell us instead, we will forward your request and help\r\nyour employer act on it, as described in the controller and processor section above.\r\n\r\nWhich of these controls Ever Async provides, and what its defaults are, is set out in the annex later\r\nin this notice.\n\n## Ever Async: what actually happens to what people write\r\n\r\n**Where this annex and a general section above differ, this annex is the accurate one for\r\nEver Async.**\r\n\r\nEver Async sits between a team's chat platform and its work tools. When a conversation is connected,\r\n**every message posted in it passes through our pipeline** — classified, then enriched by fanning the\r\nreferences it contains out to the connectors, then either acted on or dropped. So the honest starting\r\npoint is that this product sees a whole channel, including the parts of it that have nothing to do with\r\nwork, and including messages from people who never signed up for anything.\r\n\r\nThe rest of this annex is about what happens to that text afterwards, and the answer is unusual enough to\r\nlead with.\r\n\r\n### A message body is written to disk for 150 seconds, and only when a nudge is pending\r\n\r\n**There is no message-text column in our database.** The events table stores a tenant, a channel, a\r\nconversation, a message identifier, a thread root, an author identifier, an edit flag and a timestamp —\r\nand no text. The nudges table stores an author identifier and a timestamp. The contexts table stores a\r\ncount.\r\n\r\n**There is exactly one exception, and it is the whole of it.** When the product decides to nudge someone,\r\nit schedules the nudge and waits — 150 seconds in every environment we run — so the author has a chance to\r\nfix the message themselves. The suggested rewrite is generated when the nudge fires rather than when it is\r\nscheduled, so **the original message text is held in the pending-nudge record for that window**. It is\r\ndeleted when the nudge fires, and deleted when the author self-corrects and the nudge is cancelled.\r\n\r\nThat is the only place a chat message body persists. Everything else about a message is metadata: who\r\nposted, where, when, whether it was an edit, and what was extracted from it.\r\n\r\n**We are not claiming the text is never processed** — it is, in memory, for every observed message, and it\r\nis sent to a model provider under the conditions below. We are claiming it is not kept, and the storage\r\nlayer is where you can check that.\r\n\r\n### The other half of the truth: nothing expires on its own\r\n\r\n**There is no retention job in Ever Async today.** No scheduled purge, no age-based delete, nothing\r\nthat prunes an old row. The events, seen-event, nudge and context tables grow without bound and are\r\ndeleted only when the tenant is deleted.\r\n\r\nWe could print a tidy retention period here. It would not be enforced by anything, and a retention promise\r\nthe code does not keep is worse than an uncomfortable fact. **The metadata described above is kept until\r\nthe tenant is deleted, and there is no automatic expiry.** Introducing one is work we intend to do, and\r\nwhen it exists this table will say what it does.\r\n\r\n### What is held, grouped by where it comes from\r\n\r\n- **From every message in a connected conversation** — the plain-text body, in transit through the\r\n pipeline; the author's chat user identifier; the identifiers of anyone they mentioned; any URLs they\r\n posted and the references extracted from the message; the workspace or guild identifier, the\r\n conversation identifier, the message identifier and the thread root; the timestamp and whether it was an\r\n edit.\r\n- **In memory only, never written to a table** — the author's display name and whether the account is a\r\n bot.\r\n- **From a pending nudge** — the original message text, for the grace window described above.\r\n- **From the connectors** — what they return: pull request, issue and task titles, states and URLs, and\r\n the names of their authors and assignees.\r\n- **From counters** — per-tenant totals of messages observed, nudges sent and context items attached.\r\n- **From sign-in** — see the next section, because it is shorter than you expect.\r\n- **From the workspace itself** — the tenant record, memberships and roles, the workspace binding, the\r\n policy settings and the charter text.\r\n\r\n### Sign-in holds less than almost any product we run\r\n\r\n**There is no email column anywhere in the schema.** That is not a rounding of the truth, it is the shape\r\nof the database.\r\n\r\n- **Single sign-on.** Where you sign in through Slack, Discord, GitHub, Google or Ever Gauzy, the provider\r\n returns a provider user identifier, a verified email address and a display name. **The email address and\r\n the name are held in an in-memory session and are lost when the process restarts.** The only piece that\r\n reaches a database is the provider user identifier, on the memberships record with the tenant and the\r\n roles.\r\n- **Local accounts.** These are supplied to the deployment as an environment variable containing an email\r\n address and an Argon2id password hash. They are never written to a database.\r\n- **API tokens.** Static tokens of the form user id, role and secret, also supplied as an environment\r\n variable.\r\n\r\nThe practical consequence: **we usually cannot tell you a person's email address from our own records,\r\nbecause we do not have it.** A rights request that identifies a person by email may need the chat user\r\nidentifier as well, and we will say so rather than guess.\r\n\r\n### The Gauzy user map: a chat identity wired to an employee record\r\n\r\n**This is the sharpest disclosure in the product, so it has its own heading.**\r\n\r\nThe Ever Gauzy connector takes a static map from a chat user identifier to an Ever Gauzy employee\r\nidentifier. **It is a direct link between somebody's chat account and their HR record**, configured by an\r\nadministrator, without the employee being asked or necessarily told. It is what makes a phrase like \"my\r\nlast task\" resolvable.\r\n\r\n- **The customer configures it, and the customer is the controller of it.** We hold the map because they\r\n put it in their configuration.\r\n- **Once a request crosses into Ever Gauzy, that is a separate service** with its own privacy notice, and\r\n that notice governs what happens there.\r\n- If a map entry about you exists and you did not know, **ask the organisation that runs the workspace\r\n first** — it is theirs. Write to privacy@ever.co if that gets you nowhere and we will help you reach\r\n them.\r\n\r\nNot configured, no map, no linkage: the connector simply does not resolve personal references.\r\n\r\n### What leaves for a model provider, and exactly when\r\n\r\nThe prompt is not a mystery: **the classification prompt embeds the message text verbatim** alongside a\r\nlink count and a mention count, and the rewrite prompt adds the resolved context items and **the\r\nworkspace's charter**.\r\n\r\n| Configuration | Does the message text leave? |\r\n|---|---|\r\n| No `[llm]` provider configured | **No.** Classification runs on plain heuristics and nothing is sent anywhere |\r\n| Provider configured, sensitivity **conservative** | **No.** The model is never consulted at this setting |\r\n| Provider configured, sensitivity **balanced** or **high** | **Yes** — but only for the ambiguous middle of the classifier's range, and only to the provider you configured |\r\n| Provider is a local runtime you run | **No.** The text stays inside the deployment |\r\n\r\nTwo things follow that people do not expect:\r\n\r\n- **The charter goes with every one of those calls.** A team that writes customer names, staff names or\r\n case references into its charter sends them to its model provider on every classification. Write the\r\n charter as though it were the prompt, because it is.\r\n- **The routing can be indirect.** A model router forwards the request to whichever upstream provider the\r\n selected model resolves to, and the generic compatible-endpoint adapter will send to any base URL an\r\n operator configures. Each named provider is in the [Sub-processor List](https://async.ever.co/subprocessors)\r\n with its location and its transfer mechanism, and some of those mechanisms read **\"To be confirmed\"** —\r\n which is us saying we have not yet evidenced one, rather than us implying we have.\r\n\r\n**We do not use your messages, your prompts or the output to train models**, and our contracts with the\r\nproviders we engage prohibit them from doing so.\r\n\r\n### What is running on the hosted service today\r\n\r\nBecause it changes the answer to nearly every question above, it is worth stating rather than leaving to\r\nbe inferred: **in the environments we operate today, no chat platform is connected, no connector is\r\nconfigured, no model provider is configured and no notification provider is configured.** The service runs\r\nwith authentication on, a local database, and sensitivity set to conservative.\r\n\r\nSo today, on our hosted service, **no chat message data flows at all.** That will change the moment a\r\nworkspace connects, which is exactly when everything above starts to apply. It is also why our\r\nsub-processor list has only three entries in its always-engaged tier, and why the rest are in the tier\r\nthat depends on what you switch on.\r\n\r\n### People in a connected channel who never signed up\r\n\r\nAlmost everyone whose data this product touches is in this position: they posted in a channel their\r\nemployer connected. Article 14 of the GDPR entitles them to be told, and this section is that notice as\r\nwell as an explanation to the customer.\r\n\r\n- **What is held about you.** Your chat user identifier, the fact and timing of your messages in a\r\n connected conversation, the references and links inside them, who you mentioned, and — for at most the\r\n grace window, and only if a nudge was scheduled — the text of the message itself.\r\n- **Where it came from.** Your employer's or your community's chat workspace, connected by an\r\n administrator of it. **We did not obtain it from you.**\r\n- **Who decides.** The organisation that connected the workspace is the controller. We are its processor.\r\n **Ask it first**, and our [Data Processing Addendum](https://async.ever.co/dpa) is what obliges it to answer.\r\n- **What it is for.** Attaching context to a conversation and privately suggesting a clearer message to\r\n the person who wrote it.\r\n- **The nudge is private.** It goes to you and to nobody else. No manager sees it, there is no report of\r\n who was nudged how often beyond a per-tenant count, and nothing is escalated.\r\n\r\nIf a request reaches us directly we will forward it to the organisation, tell you who they are so you can\r\npursue it, and assist them — but **we will not decide it for you or for them**. Write to\r\nprivacy@ever.co; you do not need an account and it costs nothing.\r\n\r\n### Special categories, and why we do not pretend to filter\r\n\r\nA chat channel cannot be filtered in advance. **Health, religion, politics, trade union matters and purely\r\nprivate business will appear in a connected conversation**, because that is what channels contain. The\r\nproduct does not seek any of it, does not classify it and **does not detect and strip it** — saying\r\notherwise would be untrue.\r\n\r\nThe protections that actually exist are the ones described above: the body is not stored, the metadata is\r\nnarrow, and which conversations are connected is a choice the customer makes. Connecting a general channel\r\nrather than a work-tracking one is the decision that matters most here.\r\n\r\n### How long we keep the things that are specific to this product\r\n\r\nThese sit alongside the general retention table above; where both could apply, the shorter period wins.\r\n\r\n| What | How long |\r\n|---|---|\r\n| The text of a chat message | **Not stored.** In memory during processing only |\r\n| The text of a message with a nudge pending | **The grace window — 150 seconds in every environment we run** — then deleted when the nudge fires or is cancelled |\r\n| Event metadata: author id, conversation, message id, thread root, edit flag, timestamp | Until the tenant is deleted. **There is no automatic expiry today** |\r\n| Deduplication records of messages already seen | Until the tenant is deleted |\r\n| Nudge records: author id and timestamp | Until the tenant is deleted |\r\n| Context records: a count of items attached | Until the tenant is deleted |\r\n| Per-tenant counters | Until the tenant is deleted |\r\n| Sign-in session, including verified email address and display name | **In memory only** — lost when the process restarts or you sign out |\r\n| Membership record: provider user id, tenant, roles | Until removed from the workspace, or until the tenant is deleted |\r\n| Charter text, policy settings and workspace bindings | Until changed or until the tenant is deleted |\r\n| The Gauzy user map | Until the customer changes it or the tenant is deleted |\r\n| Credentials for a connector or a model provider | Until the customer removes them |\r\n\r\nDeleting a tenant deletes everything above for that tenant. Backups age out on the cycle in the general\r\nretention table and are not restored to bring back something we were asked to delete.\r\n\r\n### What is deliberately not here\r\n\r\nStated affirmatively rather than left to be inferred from an absence, because an absence is not evidence:\r\n\r\n- **No analytics.** Not a third-party tag, and not the first-party cookieless tool some of our other\r\n products run. Nothing measures your use of this product.\r\n- **No error tracking or session replay.** No crash reporter, no performance monitor, no reconstruction of\r\n what was on anyone's screen.\r\n- **No advertising, no retargeting, no enrichment, no data broker.** Nothing about a message, an author or\r\n a workspace is used to target anything, anywhere.\r\n- **No profiling of individuals.** There is no score, no ranking and no per-person record of behaviour\r\n beyond the metadata listed above. The classifier judges a message, not a person.\r\n- **No human reading your channels.** Nobody here reads a connected conversation, except where you ask us\r\n for support and point us at something specific, or where we must to investigate a security incident or\r\n comply with a legal obligation — and in the last case we tell you unless we are prohibited from doing\r\n so.\r\n\r\nIf any of that changes, it is named in this annex before it runs, not after.\r\n\r\n### Exercising your rights here, honestly stated\r\n\r\n- **The narrow schema helps you.** There is very little to export, and a tenant delete really does remove\r\n it.\r\n- **There is no self-service delete button today, and we are not going to pretend otherwise.** Write to\r\n privacy@ever.co and we will do it and answer you within one month.\r\n- **Where an organisation connected the workspace, most requests belong to that organisation**, and we\r\n route them there. The rights section above explains that routing; this annex is where you can see why it\r\n applies to nearly everyone whose data is in this product.\n\n## Cookies and similar technologies\r\n\r\nCookies, local storage, pixels, software development kits and similar technologies get their own document,\r\nbecause they need more detail than a summary can carry. What each one is, what it does, how long it lasts,\r\nwho operates it and how to refuse it is set out in our [Cookie Policy](https://async.ever.co/cookies).\r\n\r\nIn short, we sort them into four categories:\r\n\r\n- **Strictly necessary** — needed to deliver what you asked for: signing you in, holding your session,\r\n routing traffic, remembering your cookie choice itself, and protecting forms and sign-in against\r\n automated abuse. These are not optional, and we do not ask for consent to them.\r\n- **Preferences** — remember choices you have made, such as language, region and interface settings.\r\n- **Analytics** — help us understand how the Service is used so we can improve it.\r\n- **Marketing** — measure our campaigns and help us understand which organisations take an interest in us.\r\n\r\n**Nothing in the preferences, analytics or marketing categories is placed or read on your device until you\r\nagree to it.** You can accept everything, refuse everything, or choose category by category, and refusing\r\ntakes exactly as few clicks as accepting.\r\n\r\n### Changing your mind\r\n\r\nYour choices are not permanent. A **Cookie preferences** link sits in the footer of every page on\r\n[async.ever.co](https://async.ever.co) and reopens the same panel you saw the first time. Change a category\r\nthere and it takes effect immediately, for the future. Withdrawing is as easy as agreeing, and nothing\r\nabout the Service is withheld from you for refusing.\r\n\r\nOne analytics tool runs without consent, because it is configured so that it stores and reads nothing on\r\nyour device and never builds a persistent identifier for you. That is a conditional position, not a\r\npermanent one: the [Cookie Policy](https://async.ever.co/cookies) names the tool, describes the exact\r\nconfiguration we rely on, and says what happens if any part of that configuration ever changes.\n\n## Who receives your personal data\r\n\r\nWe disclose personal data only to the categories of recipient below, and only as much as each one needs to\r\ndo the job it is there for.\r\n\r\n- **Service providers acting as our processors** — hosting and infrastructure, storage, content delivery,\r\n email delivery, error monitoring, product analytics, customer support tooling and similar. They act on\r\n our documented instructions under a written contract that meets Article 28 GDPR, they are bound to\r\n confidentiality and appropriate security, and **they may not use your data for their own purposes**.\r\n- **Payment processors** — to take payment, issue invoices and handle refunds and disputes. For their own\r\n regulated obligations — fraud prevention, anti-money-laundering, card-scheme rules — they act as\r\n controllers in their own right, and their own privacy notice governs that part.\r\n- **Professional advisers** — lawyers, accountants, auditors and insurers, bound by professional\r\n confidentiality, where we need advice or have to evidence that we have complied with something.\r\n- **Public authorities, courts and regulators** — where the law requires us to disclose, or where we need\r\n to establish, exercise or defend a legal claim. We check that a request has a proper legal basis and is\r\n no wider than it needs to be, we push back where it is not, and we tell you about it unless we are\r\n legally prohibited from doing so.\r\n- **An acquirer or successor** — if we are reorganised, merged or sold, or if part of the business changes\r\n hands, personal data may pass to the acquirer as part of that transaction. The acquirer is bound by this\r\n policy or by a notice at least as protective, and we will tell you before anything about the handling of\r\n your data changes.\r\n\r\n### The sub-processors we engage for the hosted Service\r\n\r\nThese providers are engaged for the hosted Service as it is delivered to everyone. They are the ones your\r\ndata is most likely to reach.\r\n\r\n| Sub-processor | Purpose | Location | Transfer mechanism | Personal data |\n|---|---|---|---|---|\n| Cloudflare, Inc. | Authoritative DNS, reverse proxy and TLS termination for every Ever Async hostname — the marketing site, the dashboard, the API and the webhook ingress. TLS is terminated at the edge and there is no certificate in our own pods, so every request to the Service passes through it and no setting removes it. | United States, with your connection terminated at the edge location nearest to you | Standard Contractual Clauses (EU 2021/914) | IP address, TLS and connection metadata, request URLs and headers, user agent, cookies in transit |\n| GitHub, Inc. (a Microsoft Corporation company) | Holds the source, runs the build, and is the container registry the running images are pulled from (ghcr.io/ever-co/everasync and ghcr.io/ever-co/everasync-docs). This is how the Service is built and shipped rather than where message data lives — but it is a genuine third party and it is disclosed as one. | United States, with global edge delivery for registry and release downloads | Standard Contractual Clauses (EU 2021/914) | source, build, release and deployment metadata, developer and automation account identifiers, IP address and user agent of anyone pulling an image or a release |\n| Cloudflare, Inc. (R2 object storage) | Third tier of our backup chain, holding the off-site copy of the volumes this product's database sits on. Everything bound for it is encrypted by us before it leaves our network, so the provider holds ciphertext and no key and cannot read what it stores. | Cloudflare R2 buckets | Standard Contractual Clauses (EU 2021/914) | client-side encrypted backup archives only, which no third party can read, the archives derive from every category of data the Service holds |\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| ActiveCampaign, LLC (Postmark) | Relays every transactional email a product sends - account invitations, verification and sign-in codes, invoices, approvals - and on ever.co also carries contact-form enquiries with PDF attachments, so CVs and the third parties named inside them reach a US processor. | United States | Standard Contractual Clauses (EU 2021/914) | recipient name and email address, full message subject and body - invitations, verification and sign-in codes, invoices, timesheets, HR and approval content, free-text enquiry content and attached CVs from website contact forms, anyone NAMED inside that free text or attachment, delivery, bounce and open metadata |\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| 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| Functional Software, Inc. d/b/a Sentry | Captures application errors, performance traces and - on the tenant site template - masked session replays, attaching the reporting user's identity and IP to each event. | United States | Standard Contractual Clauses (EU 2021/914) | IP address, device and OS details, user id and email attached to an error event or set on the scope, URLs, route params, query strings and stack traces, which can carry request fragments and local variables, masked session replay recordings (maskAllText, blockAllMedia), desktop and mobile crash dumps |\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| Google Ireland Limited (reCAPTCHA) | Scores whether the person submitting a signup, login or contact form is human, loading on the form page before any consent choice is made. | Ireland (contracting entity); processing in Ireland (contracting) / United States (onward processing by Google LLC) | Standard Contractual Clauses (EU 2021/914) | IP address, user agent and device characteristics, mouse, touch and timing signals from the form page, cookies set on google.com |\r\n\r\nThe full and current list, including everything below, is published at\r\n[https://async.ever.co/subprocessors](https://async.ever.co/subprocessors), together with the notice period and\r\nobjection procedure that apply when we add or replace one.\r\n\r\n### Three tiers, and why the difference matters\r\n\r\nA single flat list of every vendor that appears anywhere in our software would be both inaccurate and\r\nmisleading, so the sub-processor page is split into three tiers. They mean genuinely different things.\r\n\r\n- **Always engaged.** The providers above. If you use the hosted Service, these are in the path.\r\n- **Engaged only if you turn something on.** Optional integrations, connectors and features. A provider in\r\n this tier is engaged only when you or your workspace administrator enables the specific feature or\r\n connects the specific account it belongs to. Enable nothing and it is never involved. The list says which\r\n feature or setting activates each one.\r\n- **Self-hosted deployments only.** Several of our products are published as open source and can be run on\r\n your own infrastructure. In that case **you** choose the database, object storage, email relay, AI\r\n provider and everything else, using your own credentials. Those providers appear in the list so you can\r\n see what the software can be pointed at — but they are **your** providers, not ours. **We process nothing\r\n in a deployment you run, we are not your processor for it, and the commitments in this policy do not\r\n describe it.**\r\n\r\n### We do not sell your personal data\r\n\r\nWe do not sell personal data, and we do not share it for cross-context behavioural advertising. We do not\r\nsupply it to data brokers, we do not trade it for services, and we do not permit any provider we engage to\r\nuse it to build advertising or interest profiles, on our sites or anywhere else.\n\n## Sending personal data outside the EEA\r\n\r\nMost of the personal data we hold stays inside the European Economic Area, on infrastructure we operate\r\nourselves. Some of it does not: a number of the providers we engage are established outside the EEA —\r\nprincipally in the United States — and some of them route, cache or store data on servers outside it.\r\n\r\nWhere that happens, the transfer needs a lawful mechanism under Chapter V GDPR. We use one of the\r\nfollowing for every transfer, and the sub-processor page names the destination country and the mechanism\r\nprovider by provider.\r\n\r\n### Adequacy\r\n\r\nWhere the European Commission has decided that a country provides an adequate level of protection, the\r\ntransfer relies on that decision and needs nothing further. Adequacy decisions are kept under review by\r\nthe Commission and can be amended, suspended or repealed, so we monitor them rather than treat them as\r\npermanent.\r\n\r\n### Providers in the United States\r\n\r\nFor a US provider we rely on one of two things.\r\n\r\n- **The EU–US Data Privacy Framework**, but only where that provider is *actively self-certified* under it\r\n for the type of data concerned. We check the official Data Privacy Framework list when we engage a\r\n provider and re-check it periodically. **We do not claim the Framework for a provider that has not\r\n certified, or whose certification has lapsed.**\r\n- **Standard Contractual Clauses** — the clauses approved by the European Commission in Implementing\r\n Decision (EU) 2021/914, with the modules that match the relationship, together with a transfer impact\r\n assessment and supplementary measures: encryption in transit and at rest, minimising what is sent in the\r\n first place, contractual limits on onward disclosure, and a commitment from the provider to notify and\r\n where possible challenge a government access request.\r\n\r\n**We keep Standard Contractual Clauses in place as the standing mechanism**, including for providers that\r\nare also certified under the Framework. That is deliberate, and here is the honest reason.\r\n\r\nThe Commission's adequacy decision for the Framework, adopted on 10 July 2023, is currently valid. It was\r\nchallenged, and on 3 September 2025 the General Court of the European Union dismissed that challenge in\r\n*Latombe* (Case T-553/23). **That is not the end of it** — an appeal is pending before the Court of\r\nJustice as Case C-703/25 P, and the two arrangements that preceded this one were each struck down by the\r\nsame court. So we treat the Framework as a mechanism under review rather than a settled answer, and we\r\nkeep a second mechanism standing behind it so that a change in the law is a paperwork event for us and not\r\nan interruption for you.\r\n\r\n### Other countries\r\n\r\nFor a transfer to any other country without an adequacy decision, we use Standard Contractual Clauses with\r\nthe same assessment and supplementary measures. Where a transfer is to the United Kingdom or Switzerland,\r\nthe corresponding UK and Swiss additions are applied to those clauses.\r\n\r\nWe rely on an Article 49 derogation — for example, a transfer that is strictly necessary to perform a\r\ncontract you have asked us to perform — only in a specific, occasional case where no other mechanism fits.\r\nIt is not a routine mechanism for us, and we do not use it to run a regular data flow.\r\n\r\n### Getting a copy of the safeguards\r\n\r\nYou are entitled to see the safeguards we rely on. Write to privacy@ever.co naming the provider or the\r\ntransfer you are asking about, and we will send you a copy of the relevant clauses and tell you which\r\nmodules apply. We may redact commercial terms such as pricing and service levels; we do not redact the\r\ndata protection terms, which are the part that concerns you.\n\n## How long we keep personal data\r\n\r\n\"As long as necessary\" is not an answer, so here are the actual periods. Each one runs from the event in\r\nthe middle column, and at the end of it we delete the data or irreversibly anonymise it.\r\n\r\n| What we hold | How long we keep it | Why that period |\r\n|---|---|---|\r\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 |\r\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 |\r\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 |\r\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 |\r\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 |\r\n| Security, access and audit logs | **12 months** | Investigating unauthorised access, and evidencing that we did |\r\n| Application and error logs, crash reports, diagnostics | **90 days** | Fixing what broke; they lose value quickly |\r\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 |\r\n| Cookie and consent choices | As stated in the [Cookie Policy](https://async.ever.co/cookies), which gives the lifetime of each entry | It belongs with the technology it describes |\r\n| Backups | Each backup ages out on its own rolling cycle, within **30 days** | Recovering from failure and ransomware, without becoming a second archive |\r\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 |\r\n\r\n### Data that belongs to one of our customers\r\n\r\nFor personal data held inside a customer's workspace — including anything the Service captures about that\r\ncustomer's own personnel — **the customer sets the retention period, not us**. We are their processor for\r\nit. The defaults and the limits of what they can configure are described in the product annex to this\r\npolicy.\r\n\r\nWe delete that data when the customer instructs us to, or at the end of the export window after their\r\nagreement ends, whichever comes first. If you are one of their people and you want their data about you\r\ndeleted sooner, ask them — see the section on your rights, which explains how we route that.\r\n\r\n### What \"delete\" means here\r\n\r\nDeletion is applied to live systems straight away. Backup copies are not individually edited — doing so\r\nwould defeat what a backup is for — so a deleted record persists in backups until that backup ages out on\r\nthe cycle above, at most 30 days. During that window the data is not used for anything, and **we do not\r\nrestore a backup to bring back data someone asked us to delete**; a backup is restored only to recover a\r\nwhole system after a failure.\r\n\r\nWhere we can keep something useful without keeping you identifiable, we anonymise instead of deleting —\r\naggregate usage counts, for example. Once anonymised the data is no longer personal data, and it is not\r\npossible for us to re-identify you from it.\n\n## How we protect personal data\r\n\r\nWe take the measures Article 32 GDPR requires: technical and organisational safeguards appropriate to the\r\nrisk, reviewed as the risk changes. In practice that means the following.\r\n\r\n- **Encryption in transit.** Traffic to and from the Service travels over TLS. HTTPS is enforced, and\r\n plain HTTP requests are redirected rather than served.\r\n- **Encryption at rest.** The storage holding customer content, databases and backups is encrypted at\r\n rest, and particularly sensitive values — credentials, tokens and keys — are additionally encrypted at\r\n the application layer rather than stored in readable form.\r\n- **Access control and least privilege.** Access to production systems is limited to the people whose job\r\n needs it, granted by named individual accounts rather than shared logins, protected by multi-factor\r\n authentication, scoped to the narrowest role that works, and reviewed and revoked when a role changes or\r\n someone leaves.\r\n- **Network segmentation.** Databases, storage and internal services sit on segmented internal networks\r\n and are not exposed to the public internet. Administrative interfaces are not publicly reachable.\r\n- **Logging.** Administrative and security-relevant events are logged, retained for the period in the\r\n retention section, and monitored so that unusual activity raises an alert rather than sitting unread.\r\n- **Backups.** Data is backed up regularly, held on separate infrastructure from the live systems, and\r\n restores are tested — an untested backup is a guess, not a control.\r\n- **Vulnerability management.** Dependencies are scanned, code is analysed automatically before it ships,\r\n security patches are applied on a defined schedule with a faster path for serious issues, and we operate\r\n a responsible disclosure route so that anyone who finds a problem can tell us.\r\n- **Personnel.** Everyone with access is bound by written confidentiality obligations that outlast their\r\n engagement, works on a need-to-know basis, and has access removed when it is no longer needed.\r\n- **Providers.** We assess a provider before we engage it, contract with it under Article 28 GDPR, and\r\n hold it to security obligations at least as strict as our own.\r\n\r\nOur [Security page](https://async.ever.co/security) sets out the detail, including which measure applies to\r\nwhich part of the Service, our incident response process, and the shared responsibility split between what\r\nwe secure and what you secure.\r\n\r\n### What we do not claim\r\n\r\n**We do not hold a SOC 2 report and we are not certified to ISO/IEC 27001, and we do not claim either.**\r\nIf anything you read or are told suggests otherwise, it is wrong, and we would like to know where it came\r\nfrom. Where we describe a practice on this page or on the Security page, we describe something we actually\r\ndo; where we adopt a framework as a reference without being audited against it, we say so plainly rather\r\nthan implying a certification.\r\n\r\n### No system is perfectly secure\r\n\r\n**No service, ours included, can be made completely secure, and anyone who tells you otherwise is\r\nselling something.** What we can honestly promise is that we take the measures above seriously, that we\r\nkeep them under review, and that if a personal data breach affects you we will act on it: we notify the\r\nCPDP where the law requires it, within the deadline it sets, and we\r\ntell affected people directly without undue delay where the breach is likely to result in a high risk to\r\nthem.\r\n\r\nYour part matters too. Use a strong and unique password, turn on multi-factor authentication where it is\r\noffered, keep your devices patched, and do not share credentials or access tokens. If you think an account\r\nhas been compromised, tell us at privacy@ever.co immediately.\n\n## Your rights over your personal data\r\n\r\nWhere we are the controller, the GDPR gives you the rights below. They are yours to use, you do not have\r\nto explain why you are using them, and using one costs you nothing.\r\n\r\n- **Access** — ask whether we hold personal data about you and, if we do, get a copy of it together with\r\n the information in this policy about how it is used. (Article 15)\r\n- **Rectification** — have inaccurate data corrected and incomplete data completed. Much of this you can\r\n do yourself in your account settings, which is faster than asking us. (Article 16)\r\n- **Erasure** — have data deleted where we no longer need it for the purpose we collected it for, where\r\n you withdraw the consent it rested on, or where we have processed it unlawfully. (Article 17)\r\n- **Restriction** — have us pause processing while a dispute is sorted out: while we check an accuracy\r\n challenge, for example, or while we consider an objection. We keep the data but stop using it.\r\n (Article 18)\r\n- **Portability** — receive the data you gave us, in a structured, commonly used, machine-readable format,\r\n and have it sent to another provider where that is technically feasible. This applies to data processed\r\n by automated means on the basis of your consent or a contract with you. (Article 20)\r\n- **Objection** — object to processing we base on our legitimate interests. We then stop unless we can\r\n demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or unless\r\n we need the data for a legal claim. (Article 21(1))\r\n- **Objection to direct marketing** — **absolute, and there is nothing to weigh.** If you tell us to stop\r\n using your data for direct marketing, including any profiling connected to it, we stop. No balancing\r\n test, no grace period, no exceptions. (Article 21(2))\r\n\r\nYou also have the right to withdraw consent where consent is what we rely on, which has its own section\r\nbelow, and the right to complain to a supervisory authority, which has the section after that.\r\n\r\nSome of these rights have limits written into the law itself. Erasure does not override an obligation to\r\nkeep invoices for the statutory accounting period, and portability does not extend to data we inferred or\r\ngenerated rather than received from you. **Where we cannot do all of what you ask, we will tell you which\r\npart we cannot do and why**, rather than declining as a whole.\r\n\r\n### How to make a request\r\n\r\nWrite to privacy@ever.co. Tell us which right you are using and enough about yourself for us to find\r\nthe right records — the email address on the account is usually enough. You can also write to us by post\r\nat the address at the end of this policy.\r\n\r\n- **It is free.** We charge nothing for a request. If a request is manifestly unfounded or excessive,\r\n particularly because it repeats one we have already answered, the law lets us charge a reasonable fee\r\n based on our administrative cost or refuse it. If we ever do either, we will explain why and tell you\r\n how to challenge that decision.\r\n- **We answer within one month** of receiving the request. Where a request is complex, or where you have\r\n made several, we may extend that by up to two further months — and if we do, **we will tell you within\r\n the first month, and tell you why**.\r\n- **We check who you are** before we hand over personal data, because the alternative is handing your data\r\n to someone who claims to be you. We ask for the least that makes us confident, usually a reply from the\r\n email address already on the account. We ask for an identity document only where nothing lighter works,\r\n and anything you send us for verification is used for that and nothing else, then deleted.\r\n\r\n### If your data sits in a customer's workspace\r\n\r\n**This is the most important paragraph on this page for many of the people who read it.**\r\n\r\nA large part of the personal data in the Service was put there by one of our customers — your employer,\r\nthe organisation whose workspace you belong to, or the operator of a site built on our platform. Where the\r\nService captures data about how an organisation's own personnel work, that data belongs to that\r\norganisation's workspace.\r\n\r\n**For that data the customer is the controller and we are only their processor.** We process it on their\r\ndocumented instructions and for no purpose of our own, so the law directs your request to them, not to us.\r\nPractically:\r\n\r\n- **Send your request to that organisation.** They decide it, and they are the ones who have to answer you\r\n within the deadline.\r\n- **If you send it to us instead, we will not ignore it.** We will forward it to the relevant customer\r\n promptly, tell you that we have done so, and assist them in answering it as our Data Processing Addendum\r\n requires.\r\n- **We will not decide the request ourselves, and we will not delete, correct or hand over data from a\r\n customer's workspace without their instruction** — unless a law that applies to us requires it. That is\r\n not us being unhelpful: acting on a workspace's data without the controller's instruction is precisely\r\n what a processor is not allowed to do.\r\n\r\nIf you are not sure which of the two situations you are in, ask us at privacy@ever.co and we will tell\r\nyou, and point you to the right organisation if it is not us.\n\n## Withdrawing your consent\r\n\r\nWhere we rely on your consent for something, **you can withdraw it at any time, and withdrawing is as easy\r\nas giving it**. You do not have to give a reason, and we do not ask you to justify it.\r\n\r\nWithdrawing consent stops the processing from that point onwards. **It does not make what we did before\r\nunlawful** — processing carried out while your consent was in force stays lawful, and withdrawal does not\r\nundo it. What it does mean is that we stop, and that we do not start again unless you tell us to.\r\n\r\n### How to withdraw, purpose by purpose\r\n\r\n- **Cookies and similar technologies** — open the **Cookie preferences** link in the footer of any page on\r\n [async.ever.co](https://async.ever.co), turn off the categories you no longer want, and save. The change\r\n takes effect immediately. Details are in our [Cookie Policy](https://async.ever.co/cookies).\r\n- **Marketing emails** — use the unsubscribe link at the bottom of any message we send you, or write to\r\n privacy@ever.co and ask us to stop. Either route works, and the unsubscribe link does not require\r\n you to sign in or find your password first.\r\n- **Optional features and integrations you switched on** — turn the feature off, or disconnect the\r\n connected account, in your settings. If you cannot find the switch, ask us at privacy@ever.co and we\r\n will turn it off for you.\r\n\r\nIf you have consented to something not listed here, write to privacy@ever.co naming it, and we will\r\nact on it the same way.\r\n\r\n### What happens next\r\n\r\nWe stop the processing, and we remove you from the relevant list or turn the relevant feature off. We keep\r\nthe minimum record needed to show that you consented and that you withdrew, because being able to evidence\r\nconsent is itself a legal requirement — for how long, see the retention section.\r\n\r\n**We will not quietly move the same processing onto a different legal basis to keep it running.** If some\r\npart of what you asked us to stop genuinely rests on another basis as well — an invoice we are required to\r\nkeep, for example — we will tell you which part and why, rather than leaving you to discover it.\r\n\r\nMost of what we do is not based on consent at all. It rests on performing our contract with you, on legal\r\nobligations, or on legitimate interests. **Withdrawing consent therefore does not close your account or\r\nswitch off the Service** — it affects only the things you consented to.\n\n## Complaining to a supervisory authority\r\n\r\nIf you think we have handled your personal data badly or unlawfully, **you have the right to complain to a\r\ndata protection supervisory authority**. That right is yours regardless of anything else in this policy.\r\n\r\nWe would like the chance to put it right first. Write to privacy@ever.co, tell us what went wrong, and\r\nwe will look into it and come back to you. In most cases that is the quickest way to get the outcome you\r\nactually want. **You are not required to do this, and it is not a condition of complaining** — you can go\r\nstraight to an authority, and you can do it at any point, including while we are still dealing with your\r\ncomplaint.\r\n\r\n### Our lead supervisory authority\r\n\r\nWe are established in Bulgaria, so our lead authority is the\r\n**Commission for Personal Data Protection (Комисия за защита на личните данни)** — the CPDP. Its website,\r\nincluding its complaint form and current contact details, is at\r\n[https://www.cpdp.bg/](https://www.cpdp.bg/).\r\n\r\n### You can also complain closer to home\r\n\r\nUnder Article 77 GDPR you may lodge your complaint with the supervisory authority in the EU or EEA country:\r\n\r\n- where you live;\r\n- where you work; or\r\n- where the thing you are complaining about took place.\r\n\r\nYou do not have to use ours, and you do not need our agreement to use another one. If you complain to your\r\nlocal authority, it will co-operate with ours through the mechanism the GDPR sets up for exactly this\r\nsituation, so nothing is lost by choosing whichever is easiest for you.\r\n\r\nYou also have the right to an effective judicial remedy — against a supervisory authority's decision, and\r\nagainst us directly — in the courts of the country where you live or where we are established. Complaining\r\nto an authority does not use up that right.\n\n## Automated decision-making and profiling\r\n\r\n**We do not make decisions about you that produce legal effects concerning you, or that similarly\r\nsignificantly affect you, based solely on automated processing.** No algorithm of ours decides whether you\r\nare hired, paid, promoted, disciplined, dismissed, given credit, or charged a different price. Where a\r\ndecision of that kind is made about you by an organisation using the Service, a person at that\r\norganisation makes it.\r\n\r\nWe do use automated rules to detect fraud, spam, abuse and attacks against the Service — rate limits,\r\nanomaly detection, and similar. Those rules can block a request or temporarily restrict an account. If one\r\nof them affects you, write to privacy@ever.co and a person will review it.\r\n\r\n### Where a customer turns on AI features, be aware of this\r\n\r\nThis is the part worth reading carefully, because it is easy to misunderstand.\r\n\r\nSome of our products capture activity data on behalf of a customer — an employer, typically — and some of\r\nthem offer optional AI features on top of it. **Where a customer enables those features, the Service can\r\ngenerate automated assessments of the activity it captures.** The clearest example: classifying whether\r\nthe content of a captured screen appears to be work-related. Other examples include scoring or summarising\r\ncaptured activity and grouping it into categories.\r\n\r\nFour things follow, and we would rather state them plainly than let them be discovered later.\r\n\r\n- **The output goes to the customer, not to us.** It is presented to the organisation whose workspace the\r\n data belongs to. **That organisation is the controller of it, and we are only its processor.**\r\n- **The customer decides what, if anything, to do with it.** We do not act on these assessments, we do not\r\n use them for any purpose of our own, and we do not share them with anyone else.\r\n- **These outputs are not decisions, and must not be used as if they were.** An automated assessment is an\r\n input to a human judgement. **Our terms require the customer not to treat an output of the Service as an\r\n automated decision about a person, and to apply meaningful human review before acting on one.** Whether\r\n any particular use is lawful where that customer operates — including the lawful basis for it, the\r\n notices it has to give, any impact assessment it has to carry out, and any consultation with employee\r\n representatives it has to run — is that customer's responsibility to determine, not ours.\r\n- **They can be wrong.** A classifier reading a screen has no idea what your job is. It can label genuine\r\n work as unrelated, and it can miss the opposite. Anyone relying on one of these outputs should treat it\r\n as a rough signal, and we say so to our customers as well as to you.\r\n\r\n### If an assessment about you has been generated\r\n\r\nAsk the organisation whose workspace holds the data — normally your employer. You can ask them for human\r\ninvolvement, for an explanation of how the assessment was reached, to express your point of view, and to\r\ncontest the result. They are the controller, so they are the ones who have to answer.\r\n\r\nIf you send that request to us, we will forward it to them promptly, tell you we have done so, and assist\r\nthem in answering it. See the routing paragraph in the section on your rights, which explains why we\r\ncannot decide it ourselves.\n\n## Children\r\n\r\n**The Service is not directed at children, and we do not knowingly collect personal data from them.** It\r\nis a business product, bought by organisations and used by the people who work in them. We do not design\r\nit for children, we do not market it to them, and we do not offer accounts to them.\r\n\r\nWhere consent is the basis for an online service offered directly to a child, the GDPR sets the age at\r\nwhich the child can consent alone. **In Bulgaria that age is 14.** Other EU and EEA countries set\r\nit anywhere between 13 and 16, and the age in the country where the child lives is the one that applies.\r\nBelow that age, consent has to come from — or be authorised by — a holder of parental responsibility.\r\nBecause we do not offer the Service to children, we do not operate a parental consent mechanism, and a\r\nchild under the applicable age should not create an account or submit personal data to us.\r\n\r\n### If a child's data has reached us\r\n\r\nTell us. Write to privacy@ever.co with enough detail for us to find the record — an email address, an\r\naccount name, or the page where the data was submitted. You do not need to prove anything first, and you\r\ndo not need to be the child's parent to report it.\r\n\r\nWe will check, and where we confirm that we hold personal data collected from a child without proper\r\nauthorisation, **we will delete it without undue delay**, keeping only what a law that applies to us\r\nrequires us to keep.\r\n\r\nIf the data sits inside one of our customers' workspaces rather than in our own records, the customer is\r\nthe controller of it. Tell them as well, and tell us — we will forward your report to them and press for\r\nit to be dealt with, as the routing paragraph in the section on your rights describes.\n\n## Links and content from other sites\r\n\r\nOur websites and the Service link to services we do not run, and some pages embed content that other\r\npeople host — videos, maps, code repositories, documentation and similar.\r\n\r\nFollowing a link takes you somewhere this policy does not reach. Loading embedded content means the\r\nprovider hosting it receives data directly from your browser, typically your IP address, your device and\r\nbrowser details, and the page you were on, and it may set its own cookies.\r\n\r\n**We do not control those services, and this policy does not apply to them.** What they collect and what\r\nthey do with it is governed by their own privacy notice, which is the one to read before you use them.\r\nWhere embedded content is not strictly necessary to deliver a page, we load it only once you have agreed\r\nto the relevant cookie category — see our [Cookie Policy](https://async.ever.co/cookies).\r\n\r\nA link is not an endorsement. If a link from our site takes you somewhere that mishandles your data, we\r\nwould like to know at privacy@ever.co so we can reconsider carrying it.\n\n## Changes to this policy\r\n\r\nThis policy changes when the Service changes, when we engage or replace a provider, or when the law moves.\r\nWe would rather update it than let it drift out of date and quietly stop being true.\r\n\r\nEvery version carries a version number and the date it takes effect, shown at the top of the page. **This\r\nis version 1.0.2, in force from 2026-08-02.**\r\n\r\n### How we tell you\r\n\r\n- **Minor changes** — clarifying wording, correcting a mistake, adding a provider of a kind already\r\n described — are published with a new version number and a new effective date. We do not send a separate\r\n notice for these.\r\n- **Material changes** — a new purpose, a new category of personal data, a new category of recipient, a\r\n longer retention period, a change to how you exercise your rights, or a change to the legal basis we\r\n rely on — are notified **at least 30 days before they take effect**, by email to account holders and by\r\n a notice on the site. That gives you time to read them and to act before they apply.\r\n- **Changes that need your consent** are not made by publishing a new version. We ask you, and we treat\r\n silence as a no.\r\n\r\nThis policy is a notice, not a contract. **We do not ask you to accept it**, and continuing to use the\r\nService is not us collecting your agreement to it. Where we genuinely need your agreement to something, we\r\nask for it separately and record it.\r\n\r\n### Previous versions stay available\r\n\r\nWe do not overwrite the past. **Every version of this policy that we have published remains available**,\r\nwith the dates it was in force, from the version history linked at the foot of\r\n[https://async.ever.co/privacy](https://async.ever.co/privacy). If you want to know what we said about your data on a\r\nparticular date, that is where to look — and if you cannot find it, ask us at privacy@ever.co and we\r\nwill send it to you.\n\n## How to contact us\r\n\r\nThe controller for the personal data described in this policy is **Ever Technologies LTD**, registered in\r\nBulgaria under company number 204599535, with its registered office at\r\nMladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria.\r\n\r\n- **Privacy questions, and any request about your personal data** — privacy@ever.co\r\n- **Data protection correspondence** — dpo@ever.co\r\n\r\nBoth addresses are monitored by the same people, and either will reach us. By post, write to the registered\r\noffice above and mark the letter for the attention of the privacy team. We correspond in English.\r\n\r\n**We have not designated a Data Protection Officer under Article 37 GDPR.** The dpo@ever.co address is\r\na contact channel, not a designation, and we will not describe it as one. If that position changes, this\r\npolicy will say so and will give the designated office's contact details.\r\n\r\nIf your question is about personal data held inside one of our customers' workspaces, that customer is the\r\ncontroller and the request goes to them — see the routing paragraph in the section on your rights. Write to\r\nus anyway if you are unsure, and we will tell you who to ask.\r\n\r\nThis document is version 1.0.2 of the Privacy Policy for\r\n[async.ever.co](https://async.ever.co), in force from 2026-08-02. Earlier versions, with the\r\ndates they applied, are at [https://async.ever.co/privacy](https://async.ever.co/privacy)."
364
364
  }