@ever-co/legal 0.1.0 → 0.1.2
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.
- package/dist/content/aup/ever-corporate/en.html +2 -2
- package/dist/content/aup/ever-corporate/en.json +3 -3
- package/dist/content/aup/ever-demand/en.html +2 -2
- package/dist/content/aup/ever-demand/en.json +3 -3
- package/dist/content/aup/ever-rec/en.html +2 -2
- package/dist/content/aup/ever-rec/en.json +3 -3
- package/dist/content/aup/ever-teams/en.html +2 -2
- package/dist/content/aup/ever-teams/en.json +3 -3
- package/dist/content/aup/ever-works/en.html +2 -2
- package/dist/content/aup/ever-works/en.json +3 -3
- package/dist/content/aup/everiq/en.html +2 -2
- package/dist/content/aup/everiq/en.json +3 -3
- package/dist/content/aup/gauzy/en.html +2 -2
- package/dist/content/aup/gauzy/en.json +3 -3
- package/dist/content/aup/githands/en.html +2 -2
- package/dist/content/aup/githands/en.json +3 -3
- package/dist/content/aup/hust/en.html +2 -2
- package/dist/content/aup/hust/en.json +3 -3
- package/dist/content/aup/traduora/en.html +2 -2
- package/dist/content/aup/traduora/en.json +3 -3
- package/dist/content/cookies/ever-corporate/en.html +16 -1
- package/dist/content/cookies/ever-corporate/en.json +3 -3
- package/dist/content/cookies/ever-demand/en.html +18 -3
- package/dist/content/cookies/ever-demand/en.json +3 -3
- package/dist/content/cookies/ever-rec/en.html +18 -3
- package/dist/content/cookies/ever-rec/en.json +3 -3
- package/dist/content/cookies/ever-teams/en.html +16 -1
- package/dist/content/cookies/ever-teams/en.json +3 -3
- package/dist/content/cookies/ever-tech/en.html +18 -3
- package/dist/content/cookies/ever-tech/en.json +3 -3
- package/dist/content/cookies/ever-works/en.html +16 -1
- package/dist/content/cookies/ever-works/en.json +3 -3
- package/dist/content/cookies/everiq/en.html +16 -1
- package/dist/content/cookies/everiq/en.json +3 -3
- package/dist/content/cookies/gauzy/en.html +16 -1
- package/dist/content/cookies/gauzy/en.json +3 -3
- package/dist/content/cookies/githands/en.html +16 -1
- package/dist/content/cookies/githands/en.json +3 -3
- package/dist/content/cookies/hust/en.html +16 -1
- package/dist/content/cookies/hust/en.json +3 -3
- package/dist/content/cookies/traduora/en.html +16 -1
- package/dist/content/cookies/traduora/en.json +3 -3
- package/dist/content/dpa/ever-demand/en.html +2 -2
- package/dist/content/dpa/ever-demand/en.json +3 -3
- package/dist/content/dpa/ever-rec/en.html +2 -2
- package/dist/content/dpa/ever-rec/en.json +3 -3
- package/dist/content/dpa/ever-teams/en.html +2 -2
- package/dist/content/dpa/ever-teams/en.json +3 -3
- package/dist/content/dpa/ever-works/en.html +2 -2
- package/dist/content/dpa/ever-works/en.json +3 -3
- package/dist/content/dpa/gauzy/en.html +2 -2
- package/dist/content/dpa/gauzy/en.json +3 -3
- package/dist/content/dpa/githands/en.html +2 -2
- package/dist/content/dpa/githands/en.json +3 -3
- package/dist/content/dpa/hust/en.html +2 -2
- package/dist/content/dpa/hust/en.json +3 -3
- package/dist/content/privacy/ever-corporate/en.html +3 -9
- package/dist/content/privacy/ever-corporate/en.json +3 -3
- package/dist/content/privacy/ever-demand/en.html +3 -3
- package/dist/content/privacy/ever-demand/en.json +3 -3
- package/dist/content/privacy/ever-rec/en.html +3 -9
- package/dist/content/privacy/ever-rec/en.json +3 -3
- package/dist/content/privacy/ever-teams/en.html +3 -3
- package/dist/content/privacy/ever-teams/en.json +3 -3
- package/dist/content/privacy/ever-tech/en.html +3 -9
- package/dist/content/privacy/ever-tech/en.json +3 -3
- package/dist/content/privacy/ever-works/en.html +3 -3
- package/dist/content/privacy/ever-works/en.json +3 -3
- package/dist/content/privacy/everiq/en.html +3 -3
- package/dist/content/privacy/everiq/en.json +3 -3
- package/dist/content/privacy/gauzy/en.html +3 -3
- package/dist/content/privacy/gauzy/en.json +3 -3
- package/dist/content/privacy/githands/en.html +3 -3
- package/dist/content/privacy/githands/en.json +3 -3
- package/dist/content/privacy/hust/en.html +3 -3
- package/dist/content/privacy/hust/en.json +3 -3
- package/dist/content/privacy/traduora/en.html +3 -3
- package/dist/content/privacy/traduora/en.json +3 -3
- package/dist/content/refund/ever-works/en.html +2 -2
- package/dist/content/refund/ever-works/en.json +3 -3
- package/dist/content/refund/gauzy/en.html +2 -2
- package/dist/content/refund/gauzy/en.json +3 -3
- package/dist/content/refund/githands/en.html +2 -2
- package/dist/content/refund/githands/en.json +3 -3
- package/dist/content/refund/hust/en.html +2 -2
- package/dist/content/refund/hust/en.json +3 -3
- package/dist/content/security/ever-demand/en.html +1 -1
- package/dist/content/security/ever-demand/en.json +3 -3
- package/dist/content/security/ever-rec/en.html +1 -1
- package/dist/content/security/ever-rec/en.json +3 -3
- package/dist/content/security/ever-teams/en.html +1 -1
- package/dist/content/security/ever-teams/en.json +3 -3
- package/dist/content/security/ever-works/en.html +1 -1
- package/dist/content/security/ever-works/en.json +3 -3
- package/dist/content/security/gauzy/en.html +1 -1
- package/dist/content/security/gauzy/en.json +3 -3
- package/dist/content/security/githands/en.html +1 -1
- package/dist/content/security/githands/en.json +3 -3
- package/dist/content/security/hust/en.html +1 -1
- package/dist/content/security/hust/en.json +3 -3
- package/dist/content/subprocessors/ever-corporate/en.html +1 -7
- package/dist/content/subprocessors/ever-corporate/en.json +3 -3
- package/dist/content/subprocessors/ever-demand/en.html +1 -1
- package/dist/content/subprocessors/ever-demand/en.json +3 -3
- package/dist/content/subprocessors/ever-rec/en.html +1 -7
- package/dist/content/subprocessors/ever-rec/en.json +3 -3
- package/dist/content/subprocessors/ever-teams/en.html +1 -1
- package/dist/content/subprocessors/ever-teams/en.json +3 -3
- package/dist/content/subprocessors/ever-tech/en.html +1 -7
- package/dist/content/subprocessors/ever-tech/en.json +3 -3
- package/dist/content/subprocessors/ever-works/en.html +1 -1
- package/dist/content/subprocessors/ever-works/en.json +3 -3
- package/dist/content/subprocessors/everiq/en.html +1 -1
- package/dist/content/subprocessors/everiq/en.json +3 -3
- package/dist/content/subprocessors/gauzy/en.html +1 -1
- package/dist/content/subprocessors/gauzy/en.json +3 -3
- package/dist/content/subprocessors/githands/en.html +1 -1
- package/dist/content/subprocessors/githands/en.json +3 -3
- package/dist/content/subprocessors/hust/en.html +1 -1
- package/dist/content/subprocessors/hust/en.json +3 -3
- package/dist/content/subprocessors/traduora/en.html +1 -1
- package/dist/content/subprocessors/traduora/en.json +3 -3
- package/dist/content/tos/ever-corporate/en.html +3 -3
- package/dist/content/tos/ever-corporate/en.json +3 -3
- package/dist/content/tos/ever-demand/en.html +3 -3
- package/dist/content/tos/ever-demand/en.json +3 -3
- package/dist/content/tos/ever-rec/en.html +3 -3
- package/dist/content/tos/ever-rec/en.json +3 -3
- package/dist/content/tos/ever-teams/en.html +3 -3
- package/dist/content/tos/ever-teams/en.json +3 -3
- package/dist/content/tos/ever-tech/en.html +3 -3
- package/dist/content/tos/ever-tech/en.json +3 -3
- package/dist/content/tos/ever-works/en.html +3 -3
- package/dist/content/tos/ever-works/en.json +3 -3
- package/dist/content/tos/everiq/en.html +3 -3
- package/dist/content/tos/everiq/en.json +3 -3
- package/dist/content/tos/gauzy/en.html +3 -3
- package/dist/content/tos/gauzy/en.json +3 -3
- package/dist/content/tos/githands/en.html +3 -3
- package/dist/content/tos/githands/en.json +3 -3
- package/dist/content/tos/hust/en.html +3 -3
- package/dist/content/tos/hust/en.json +3 -3
- package/dist/content/tos/traduora/en.html +3 -3
- package/dist/content/tos/traduora/en.json +3 -3
- package/dist/index.json +144 -144
- package/package.json +50 -50
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
<h1 id="acceptable-use-policy" tabindex="-1">Acceptable Use Policy</h1>
|
|
2
2
|
<p><strong>Ever</strong> — <a href="https://ever.co">ever.co</a></p>
|
|
3
|
-
<p>Version 1.0.
|
|
3
|
+
<p>Version 1.0.2 · In force from 2026-08-02</p>
|
|
4
4
|
<p>This Acceptable Use Policy ("<strong>AUP</strong>") sets out what may and may not be done with the Ever website and
|
|
5
5
|
the websites, applications and application programming interfaces we make available at
|
|
6
6
|
<a href="https://ever.co">ever.co</a> (together, the "<strong>Service</strong>").</p>
|
|
@@ -661,7 +661,7 @@ use this address, customer or not.</strong></li>
|
|
|
661
661
|
<p>By post: <strong>Ever Technologies LTD</strong>, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — registered in Bulgaria under company number
|
|
662
662
|
204599535.</p>
|
|
663
663
|
<p>We correspond in English.</p>
|
|
664
|
-
<p>This document is version 1.0.
|
|
664
|
+
<p>This document is version 1.0.2 of the Acceptable Use Policy for
|
|
665
665
|
<a href="https://ever.co">ever.co</a>, in force from 2026-08-02. It forms part of our
|
|
666
666
|
<a href="https://ever.co/tos">Terms of Service</a>, and earlier versions, with the dates they applied, are published
|
|
667
667
|
alongside them.</p>
|
|
@@ -6,9 +6,9 @@
|
|
|
6
6
|
"entity": "Ever Technologies LTD",
|
|
7
7
|
"entityId": "ever-technologies-bg",
|
|
8
8
|
"locale": "en",
|
|
9
|
-
"version": "1.0.
|
|
9
|
+
"version": "1.0.2",
|
|
10
10
|
"effectiveDate": "2026-08-02",
|
|
11
|
-
"sha256": "
|
|
11
|
+
"sha256": "3cd93fda875da30cf62c972c73a5ab1b61ebf46c3e9f98395ee3832eb55d04b2",
|
|
12
12
|
"publishable": true,
|
|
13
13
|
"sections": [
|
|
14
14
|
"core/aup/010-scope",
|
|
@@ -298,5 +298,5 @@
|
|
|
298
298
|
}
|
|
299
299
|
],
|
|
300
300
|
"path": "content/aup/ever-corporate/en.html",
|
|
301
|
-
"markdown": "# Acceptable Use Policy\n\n**Ever** — [ever.co](https://ever.co)\n\nVersion 1.0.0 · In force from 2026-08-02\n\nThis Acceptable Use Policy (\"**AUP**\") sets out what may and may not be done with the Ever website and\nthe websites, applications and application programming interfaces we make available at\n[ever.co](https://ever.co) (together, the \"**Service**\").\n\nIt forms part of our [Terms of Service](https://ever.co/tos) and uses the words defined there. **Breaking a\nrule in this policy is a breach of those Terms**, and the enforcement section below sets out what we do about\nit.\n\nWe have kept it specific. A policy that only says \"do not misuse the Service\" tells nobody anything and\nprotects nobody — least of all the people our software can be pointed at.\n\n## Who this policy applies to\n\n- **You**, as the customer holding the Subscription.\n- **Your End Users** — everyone you invite into your Workspace, whether an employee, a contractor, a client or\n a colleague. **What they do in the Service counts as your act**, and it is your job to make sure they know\n these rules.\n- **Anyone else who reaches the Service through you** — a person you send a share link to, a person who\n receives a message sent through the Service, anyone using access you granted.\n- **Visitors** to our public websites, documentation and community channels, and anyone using our public\n forms, endpoints or APIs.\n\nYou do not need an account for this policy to apply to you. Using the Service in any way means these rules\napply to what you do with it.\n\n## What this policy does not apply to\n\n**Self-hosted deployments.** Where our software is published as open source, that code is licensed to you\nunder its own licence, and **this policy imposes nothing on you as a self-hoster**. It governs the hosted\nService we operate and nothing else. Nothing here adds a restriction to any open-source licence — the\nopen-source carve-out in our [Terms of Service](https://ever.co/tos) explains the split.\n\n**Lawful workplace monitoring.** Some of our products exist to measure how work happens, and this policy does\nnot prohibit using them for that. What it prohibits is doing it covertly, doing it to people who were never\ntold, and doing it to people who are not yours to monitor. That distinction is drawn deliberately, and in\ndetail, in the privacy and surveillance section below.\n\n## How it fits with everything else\n\n- The product-specific section of this policy adds rules for the particular Service you use. **Where a core\n rule and a product rule both apply, follow the stricter one.**\n- Where your Order, a written agreement with us, or the Documentation permits something this policy would\n otherwise forbid — an agreed rate limit, an authorised security test — that permission governs, for that\n thing only.\n- The examples here are examples. They show what we mean; they are not a complete list of everything that can\n be done wrong. Conduct that is plainly within the spirit of a prohibition is prohibited.\n\n**We are not obliged to monitor what you do in the Service, and we do not routinely read the contents of your\nWorkspace.** We do act on what we find and on what is reported to us, and not acting on one thing never waives\nour right to act on another.\n\n## Illegal and harmful activity\n\nDo not use the Service to do anything unlawful, to help someone else do it, or to conceal that it is being\ndone. **Something is out of bounds here if it is unlawful where you are, where we operate, or where the person\naffected by it is** — you do not get to pick the most permissive of the three.\n\n### Never, under any circumstances\n\nSome conduct has no lawful version and gets no benefit of the doubt. **We terminate immediately for it, we\npreserve what we hold, and we report it to the authorities where the law requires that or where a person is at\nrisk:**\n\n- child sexual abuse material, and sexualised content involving a minor in any form;\n- content that grooms, solicits or endangers a child;\n- non-consensual intimate imagery, and threats to publish it;\n- terrorist content, and material that incites, promotes or gives instruction for terrorism or mass violence;\n- credible threats of serious violence against a person or a group;\n- human trafficking, forced labour, and the sale or exploitation of people.\n\nThere is no enforcement ladder for this list and no cure period.\n\n### Fraud and deception\n\n- Fraud of any kind — payment fraud, invoice fraud, business email compromise, advance-fee schemes, pyramid\n and Ponzi arrangements.\n- Phishing, credential harvesting, and pages or messages built to be mistaken for someone else's.\n- Card testing, use of stolen or unauthorised payment instruments, chargeback abuse, money laundering, and\n moving the proceeds of crime.\n- Impersonating a person, a company, a public body or us; using a false identity; forging message headers or\n sender identities.\n- Fabricated reviews, testimonials, endorsements, certifications, awards or qualifications.\n- **Falsifying records the Service generates or holds** — including tampering with a timer, tracker, activity\n log or timesheet to misstate work done or time worked. Where that record is evidence between you and your\n own employer or customer, falsifying it is fraud against them and a breach of this policy against us.\n\n### Unlawful goods, services and content\n\nDo not use the Service to offer, advertise, arrange, broker or deliver: controlled substances and unlicensed\npharmaceuticals; weapons, ammunition or their components; counterfeit goods; stolen property, stolen data or\nstolen credentials; unlicensed gambling; or anything else you are not licensed to provide where you provide it.\n\nWhere your business is lawful but regulated — health, finance, insurance, legal services, alcohol, tobacco,\nage-restricted goods — **holding the right licences, giving the right disclosures and running the right\nverification and handover checks is yours to do.** We do not check any of it and we are not your compliance\nfunction.\n\n### Sanctions, export controls and embargoes\n\nYou must not use the Service, or allow it to be used, in breach of applicable sanctions or export-control law,\nor for or on behalf of a person or organisation subject to them. The compliance, export and sanctions section\nof our [Terms of Service](https://ever.co/tos) sets out what that means for your Subscription.\n\n### Interfering with the law\n\nDo not use the Service to obstruct a lawful investigation, evade a court order, conceal or destroy material you\nare required to keep, or defeat a removal, blocking or suppression obligation that applies to you.\n\n## Content that infringes someone else's rights\n\nYou need the right to put something into the Service before you put it there. That applies to files, images,\ntext, code, datasets, brand names, and anything an integration brings in on your behalf.\n\n### What is prohibited\n\n- Uploading, storing, publishing, sharing or distributing anything that infringes another person's copyright,\n trade marks, design rights, database rights, patents or trade secrets.\n- Importing or republishing datasets, catalogues, curated lists or harvested collections you have no right to\n use. **An openly licensed source is not an unconditional one** — attribution, share-alike and non-commercial\n conditions travel with the content, and honouring them is your job, not ours.\n- Using someone else's trade mark in a workspace name, project name, URL slug, custom domain or sending domain\n in a way that suggests a connection you do not have. That includes typosquats and look-alike domains.\n- Putting another party's confidential information into the Service where you have no right to disclose it:\n material under a non-disclosure agreement, another company's customer data, privileged or otherwise protected\n work.\n- Removing, obscuring or altering a copyright notice, licence text, attribution or provenance metadata.\n\n### Our own software and brand\n\nWhere a product is published as open source, its licence governs what you may do with the code — but do not\nstrip its licence headers or attribution, do not present a fork or a self-hosted deployment as a service we\noperate, do not redistribute a paid edition, and do not circumvent the limits of the tier you bought. What you\nmay do with our names, logos and other brand features is dealt with in the intellectual property section of our\n[Terms of Service](https://ever.co/tos).\n\n### Reporting infringement\n\nIf something on the Service infringes your rights, tell us at abuse@ever.co. We handle these as\nnotice-and-action complaints under the rules that apply to us as a hosting service in the European Union, and\na notice needs to give us:\n\n- what the right is and why you hold it, or your authority to act for the person who does;\n- exactly where the material is — a URL, share link, workspace or file path, precise enough that we can find it\n without guessing;\n- what the material infringes, and how;\n- a statement that you believe in good faith the use is not authorised by the rights holder, an agent or the\n law; and\n- how to reach you.\n\n### What happens next\n\nWe assess notices on their content, not on their volume or their tone.\n\nWhere a notice is well founded we remove or disable access to the material, and we tell the affected customer\nwhat we did and why, unless the law prevents us. **Where the customer tells us the notice is wrong, we pass\nthat back to the complainant and we may restore the material.** We are not the venue for deciding who owns\nwhat — a genuine ownership dispute belongs in a court, not in our inbox.\n\n**We terminate accounts that infringe repeatedly.** What counts as repeat is a judgement about the pattern and\nthe customer's response to it, not a fixed count we publish for people to stay just underneath.\n\n## Harassment, hate and abusive content\n\nMost of what goes into the Service is private business content in your own Workspace, and we are not the\nmanners police for it. These rules still apply to it, and **they apply with real force to anything you publish\nthrough the Service, send to another person through it, or point a share link at.**\n\n### Prohibited\n\n- **Harassment and bullying** — a course of conduct directed at a person that is intended to, or is reasonably\n likely to, intimidate, humiliate or distress them, including conduct continued after they have asked for it\n to stop.\n- **Threats** of violence, and content that celebrates or wishes serious harm on identifiable people.\n- **Stalking** — using the Service to follow, locate, contact or observe a person against their wishes. Where\n that involves our capture, recording or tracking features, the privacy and surveillance section below governs\n it and we treat it as the most serious category of breach we handle.\n- **Hate speech** — attacking or demeaning people because of race, ethnicity, national origin, religion,\n disability, age, sex, sexual orientation, gender identity or another protected characteristic.\n- **Doxxing** — publishing or sharing a person's private information without their agreement, or assembling it\n so that someone else can act on it. Home addresses, personal contact details, identity documents, location,\n medical and financial details all count.\n- **Sexual content involving a person who has not agreed to it being shared**, and any sexual content involving\n a minor. That second category is dealt with absolutely in the illegal activity section above.\n- **Adult content on public-facing surfaces we host for you**, unless we have agreed it in writing and it is\n lawful and age-gated where it is served.\n- **Abuse of our own people.** Threatening, abusive or discriminatory conduct towards our staff in support\n tickets, chat, calls, issue trackers or community channels. We will end the conversation, and if it continues\n we will end the relationship.\n\n### Content you publish for other people to see\n\nWhere the Service lets you publish something publicly — a page, a directory, a profile, a shared recording, a\npublic team — **you are the publisher of it, not us.** Keep other people's personal data out of it unless they\nknow and you have a basis for holding it there, provide a way for people to complain about what you have\npublished, and act on a reasoned objection rather than ignoring it. **You must not republish content that a\nperson has already had removed.**\n\nWhere you run something on our infrastructure that accepts contributions from the public, moderating it is your\nobligation. Our tools do not discharge it and our policy is not your policy.\n\n### Community and contribution channels\n\nOur public repositories, issue trackers, documentation sites and chat channels carry these rules plus any code\nof conduct published with them. Spam, off-topic promotion, brigading and abuse there are breaches of this\npolicy and we deal with them the same way.\n\n## Privacy and unlawful surveillance\n\n**This is the strictest section in this policy, and it is strict because of what our software can do.**\n\nSome of our products measure how work happens. Depending on the product and the settings your administrators\nchoose, they can capture screenshots, webcam stills, audio, screen recordings, keyboard and mouse activity\nrates, the applications and websites in use, location, and how long each of those lasted. Selling software that\ncan do that places a duty on us that a project-management tool does not carry, and this section is how we\ndischarge it.\n\n**Lawful, disclosed monitoring of your own personnel is a legitimate use of the Service. Covert monitoring is\nnot, and never will be.** Everything below follows from that one line.\n\n### Monitoring that is never permitted\n\nYou must not use the Service, or configure it, to do any of the following.\n\n- **Covert or secret monitoring of any person.** If the person being measured does not know it is happening, it\n is prohibited — whatever your reason, wherever you are, and whether or not you believe you have a lawful\n basis for the underlying processing.\n- **Monitoring anyone who has not been informed in the way their local law requires, before capture starts.**\n Telling someone afterwards is not notice. A line in a handbook they have never seen is not notice either,\n where their law demands more.\n- **Monitoring outside working hours, during breaks, on personal time, or on a person's own device**, without a\n lawful basis and their knowledge. Capture follows the work. It does not follow the person.\n- **Enabling screen capture, webcam stills, audio capture or screen recording where local law prohibits it**,\n restricts it to purposes you are not pursuing, or conditions it on a process you have not completed.\n- **Deploying a configuration the monitored person cannot see, pause, stop or exit.** Combining continuous or\n randomised capture with settings that stop a person closing the agent, logging out, or seeing that capture is\n running produces covert monitoring by construction, and we treat it as covert monitoring however it was\n arrived at.\n- **Monitoring anyone other than your own personnel in the course of their work.** The Service may be used to\n measure your employees, contractors and workers while they work for you. It may not be pointed at a partner,\n a family member, a housemate, a child, a customer, a competitor, a journalist, or any other person who is not\n yours to monitor. **Using our software as stalkerware is an immediate-termination breach and we will treat it\n as one.**\n- **Installing the desktop agent, browser extension or tracker on a device you do not own or control**, without\n the informed agreement of the person who does.\n- **Using captured data for a purpose the monitored person was not told about.** If they were told capture was\n for billing accuracy, it is not then available for discipline, performance ranking or redundancy selection.\n Purpose creep is a breach of this policy, not only of your own notice.\n- **Capturing where capture predictably exposes other people's confidential or special-category data** —\n clinical settings, legally privileged work, HR investigations, child-facing services, or a home where other\n people are visible or audible — unless capture is switched off for the people concerned.\n- **Defeating the controls that exist to protect people.** Do not work around a per-person or per-team disable,\n a blur setting, a retention limit, an excluded-application list or a capture-frequency limit in order to\n observe someone whose monitoring is meant to be off or reduced.\n\n### Other people's privacy, whatever product you use\n\nThese apply across the Service, not only to the products that measure work.\n\n- **Recording a call, meeting, screen or conversation without the notice or consent the law requires** from\n everyone involved. Several jurisdictions require every party to agree, and where participants are in\n different places the strictest rule among them is the one that governs.\n- Capturing another person's screen, device, session or account without their authorisation.\n- Using a browser extension's access to reach pages the person never intended to expose — personal banking,\n health portals, private messaging, personal webmail.\n- Harvesting personal data at scale, from us or from anywhere else, including collecting it in breach of\n another platform's terms, its rate limits or its technical protections.\n- Building biometric profiles, or inferring sensitive characteristics about people — health, beliefs, sexual\n orientation, union membership, immigration status — from anything the Service captures or holds.\n- Entering another person's personal data into our forms, or subscribing an address you do not control.\n- Putting special-category data into the Service without a lawful basis for it, or where your product annex\n states that the Service is not built to hold it.\n\n### What you promise us when you switch monitoring on\n\nBy enabling any capture or activity-measurement feature for a person, **you represent to us** that:\n\n- you are the controller of that processing, you have identified a valid lawful basis for it, and you\n understand that **consent is generally not a valid basis in an employment relationship**, because of the\n imbalance between the person asking and the person consenting;\n- you have given that person the information their law requires — what is captured, how often, why, who sees\n it, how long it is kept, and how to object — **before capture began**;\n- you have carried out a data protection impact assessment where one is required, and consulted your\n supervisory authority where the residual risk requires that;\n- you have completed any works council, trade union or employee-representative process required where that\n person works. **These are not formalities.** Co-determination in Germany, works council consent in Austria,\n works council approval in the Netherlands, prior union agreement or labour-inspectorate authorisation in\n Italy, and co-operation negotiations in Finland can each make a deployment unlawful, and the data it produced\n unusable, if they were skipped;\n- you will not enable capture for anyone in a jurisdiction that prohibits it. **Some do.** Supervision of\n performance by remote technical means is close to prohibited outright in Portugal, and keystroke and\n continuous-capture tooling has been held unlawful elsewhere on proportionality grounds; and\n- you are not using the Service to monitor covertly, or to monitor anyone outside a lawful monitoring programme\n of your own.\n\n**We make no claim that any configuration of the Service is lawful in any country.** This law differs sharply\nfrom one jurisdiction to the next and is still moving. We build the controls, publish what each one does, and\ngive you the material to run your own assessment. **The decision to switch monitoring on is yours, and so is\nthe liability that comes with it.** Your indemnity in our [Terms of Service](https://ever.co/tos) covers claims\nthat arise from breaking the representations above.\n\n### We act on credible reports of covert monitoring\n\n**Anyone can report suspected covert or unlawful monitoring to abuse@ever.co — you do not have to be our\ncustomer.** A monitored worker, a works council, an employee representative, a family member or a regulator can\nall use that address. We would far rather receive a report that turns out to be a misunderstanding than not\nreceive one at all.\n\nWhen we receive a credible report:\n\n- **we treat the reporter's identity as confidential.** We do not pass it to the customer without their\n agreement unless the law compels us. We know that the person best placed to report covert monitoring is\n usually the person with the most to lose by reporting it;\n- **we may require the customer to evidence** the notice it gave, the lawful basis it relies on, and the\n consultations it completed. \"Trust us\" is not evidence, and a customer that cannot produce any is treated as\n a customer that has none;\n- we may switch off specific capture features for that Workspace while we look, suspend the account, or\n terminate it, depending on what we find and how serious it is; and\n- **we will not take a customer's assurance over a credible report from the person being monitored.**\n\n**Retaliating against someone because they reported to us — dismissing them, disciplining them, withdrawing\ntheir work — is itself a breach of this policy**, and we will act on it against the customer that does it.\n\n## Security violations\n\nThe Service is shared infrastructure. The rules below protect other customers at least as much as they protect\nus.\n\n### Do not\n\n- **Access anything you were not given access to** — another customer's Workspace or data, another user's\n account, our internal systems, or any part of the Service behind a boundary you were not invited past.\n- **Probe, scan or test** the Service, our networks or our infrastructure for vulnerabilities without our prior\n written permission, except within the coordinated disclosure route below.\n- **Attack accounts** — credential stuffing, password spraying, brute forcing, or enumerating accounts and\n email addresses through sign-in, recovery or invitation endpoints.\n- **Enumerate or guess identifiers.** Share links, object ids, invitation tokens and export URLs are meant to\n be given to you, not discovered by you.\n- **Circumvent controls** — authentication, authorisation, session handling, tenant isolation, rate limits,\n quotas, access gates, licence-tier limits, or any technical protection measure.\n- **Interfere with the Service** — denial-of-service traffic, load designed or reasonably likely to degrade the\n Service for others, or any attempt to cross the isolation between one Workspace and another.\n- **Reverse engineer, decompile or disassemble** the Service, except to the extent an applicable open-source\n licence or a law that cannot be excluded permits it.\n- **Turn the Service into infrastructure for something else** — an open relay or proxy, an anonymisation or VPN\n service, a command-and-control endpoint, a port scanner, a password-cracking rig, or a staging point for an\n attack on a third party.\n\n### Credentials and access\n\n- **Accounts are for one person.** Do not share a login, and do not hand an account from one person to the next\n as staff change — create and remove accounts instead.\n- Do not share API keys, tokens or seats outside the Workspace they were issued for, and do not leave them\n anywhere others can read them.\n- **Do not give us credentials you are not entitled to use** — a colleague's, a former employer's, a shared\n mailbox you do not control, or an access token, key or configuration file belonging to someone else.\n- Do not use the Service to store, distribute or trade credentials obtained from anyone else.\n- Keep your own credentials secure, turn on multi-factor authentication where we offer it, and **tell us at\n abuse@ever.co as soon as you suspect an account has been compromised.** Delay there costs other people,\n not only you.\n\n### Security research\n\nWe want to hear from researchers, and we will not pursue anyone who acts in good faith.\n\nYour testing is in scope if you work only against your own account and your own data; do not access, modify or\nretain another customer's data; stop at the point that demonstrates the issue rather than pushing further; avoid\ndegrading the Service or causing a privacy impact; do not run automated scanning at volume; and report to us\npromptly and privately at abuse@ever.co before disclosing anywhere else.\n\n**Testing against another customer's Workspace or data is never in scope**, whatever your intent. How we handle\nreports, and what we commit to in return, is set out on our Security page.\n\n## Resource abuse\n\nYou share compute, storage, bandwidth and outbound sending reputation with every other customer. Use your\nshare.\n\n### Do not\n\n- Mine cryptocurrency, run distributed computing, or use the Service for processing that has nothing to do with\n what the Service is for.\n- Use our storage or bandwidth as a general-purpose content delivery network, a file-distribution service, a\n backup target for unrelated data, or a home for media we had no part in producing — including hot-linking\n files held with us into other sites.\n- Run automated bulk extraction against the Service, our websites, our documentation or our APIs. **Issued API\n credentials used within their documented scope and rate limits are exactly what they exist for**; scraping the\n interface, or driving an API past its published limits, is not.\n- Run unbounded or pathological workloads — agent or job loops with no termination condition, retry storms,\n runaway automation, or deliberately expensive requests repeated to see what happens.\n- Hold sessions, connections or reserved capacity open purely to keep hold of them.\n- Evade a limit rather than raise it: extra accounts to farm a free allowance, disposable addresses, referral or\n credit gaming, seat sharing, or a second Workspace created because the first one hit its ceiling.\n\n### Free plans and trials\n\nFree and trial access exists so that you can evaluate the Service and so that small teams can use it. It is not\nanonymous infrastructure. **Limits on free plans are tighter, are enforced at our discretion, and can change\nwithout notice.** We may reclaim idle free resources, and we may decline to keep providing a free plan to an\naccount whose consumption is out of proportion to what free access is for.\n\n### How we handle it\n\nSustained load that is normal for your plan is fine. Bursting is fine. What we act on is load that degrades the\nService for other people, load that is not really use of the product at all, and load that keeps growing after\nwe have asked about it.\n\n**Our first step is normally to contact you, not to cut you off.** We would rather move you onto a plan or a\nlimit that fits than lose you over a number. We throttle before we suspend, and we suspend without warning only\nwhere the platform or other customers are at risk.\n\nIf your usage above a published limit is a genuine business need rather than abuse, write to legal@ever.co\nand we will look at raising it. The numbers themselves are in the fair use section below, in your plan or Order,\nand in the Documentation.\n\n## Spam and unsolicited messaging\n\nThe Service sends mail, invitations, notifications and, in some products, text messages — sometimes from our\nown sending domains and on our own reputation. That makes messaging abuse everybody's problem here: one\ncustomer's cold-outreach campaign is what gets every other customer's invoices and password resets filtered.\n\n### Do not\n\n- **Send unsolicited bulk email, SMS or messages of any kind through the Service**, or use it to prepare, host\n or support a campaign that someone else sends.\n- **Mail a list you cannot stand behind.** You must be able to show us, on request, how each recipient came to\n be on it. Purchased, rented, swapped, harvested and scraped lists are prohibited, and so are address guessing,\n permutation and dictionary attacks.\n- **Spoof or falsify** a sender identity, a header, a reply path or a domain, or send from a domain you do not\n control. Where you send through the Service, configure SPF, DKIM and DMARC for your own domain, respect any\n warm-up schedule and sending rate we set, and keep a working reply path that a human reads.\n- **Strip, hide, disable or visually suppress** an unsubscribe link, a `List-Unsubscribe` header, a required\n postal address, or any compliance footer the Service adds. **Making the opt-out hard to find is the same\n breach as not having one.**\n- **Ignore an opt-out.** Suppression must be honoured promptly and permanently. No re-importing a suppressed\n person, no refreshing them from another source, no moving them into a second Workspace or account to escape\n the suppression list, and no treating an unsubscribe click as an engagement signal.\n- **Repurpose our transactional messages as a marketing channel.** Invitations, verification mails, share\n notifications, estimates, invoices and system notices exist to carry their own content — not to carry an offer\n to someone who never asked for one.\n- **Use invitations to reach people who will not be working in your Workspace.** The invitation flow is a\n foreseeable spam vector and we watch it.\n- **Abuse our own public endpoints** — automated submissions to our contact, newsletter or support forms,\n repeated submissions used to bomb a third party's mailbox through them, or link injection into free-text\n fields.\n\n### The law applies to you, and we do not check it for you\n\nElectronic marketing to individuals is regulated separately from data protection. Depending on where your\nrecipients are you may need prior opt-in, and the existing-customer exception is much narrower than most senders\nassume. **Working out which rule covers which recipient is yours to do.** Nothing the Service does — including\nany compliance footer it adds for you — makes a message lawful that would not otherwise be.\n\n### Deliverability is an enforcement trigger\n\nWe monitor bounce rates, spam complaints, blocklist entries and mailbox-provider feedback for traffic sent\nthrough the Service. **Where a sender's numbers put shared reputation at risk we act immediately and without\nnotice** — pausing a campaign, throttling or suspending sending, revoking a sending domain, or suspending the\naccount. We do the same on a credible complaint from a recipient, a mailbox provider or a blocklist operator.\n\nIf you received a message from someone using the Service and you did not ask for it, report it to\nabuse@ever.co with the full headers if you have them.\n\n## Malware and hostile files\n\n### Do not upload, store, link to or distribute\n\n- **Malware of any kind** — viruses, worms, trojans, ransomware, rootkits, keyloggers, spyware and stalkerware.\n- **Exploit code, exploit kits, cracking and credential-stuffing tools**, and payloads intended to establish or\n keep unauthorised access to anything.\n- **Files built to attack whatever opens them** — decompression bombs, entity-expansion payloads, deliberately\n malformed documents, and uploads crafted to break a parser, a preview renderer or a downstream viewer.\n- **Values crafted to execute somewhere else.** Text you put into a field that is later exported — a name, a\n translation string, a note, a description — must not be built to run as a formula, a script or a command in\n whatever opens the export.\n- **Phishing and credential-harvesting pages**, fake sign-in screens, and deceptive destinations of any kind.\n **A link on our domain lends our credibility to whatever it points at**, which is exactly why share links\n attract this and exactly why we move fast on it.\n\n### We scan, and we are telling you so\n\nWe may scan, sandbox, quarantine, refuse, disable or delete files, links and messages that we reasonably believe\nare hostile, and we may do it without prior notice.\n\n**We are stating this openly because scanning your uploads is itself a processing activity, and undisclosed\nprocessing is not something we are willing to do.** What it means for personal data is set out in our\n[Privacy Policy](https://ever.co/privacy).\n\nAutomated detection is imperfect in both directions. If we have quarantined something wrongly, tell us at\nabuse@ever.co and we will look again.\n\n### Security work with a legitimate need\n\nIf your work genuinely involves handling malware samples — you run a security team, or you research this for a\nliving — do not do it in the Service without asking us first. Write to legal@ever.co, tell us what you need\nand how it will be contained, and we will either agree it in writing or tell you no. **Doing it without that\nagreement is a breach**, however good the reason.\n\n### Your own hygiene\n\nKeep the devices and networks you use to reach the Service reasonably secure and up to date, and tell us at\nabuse@ever.co if you believe a device with access to your Workspace has been compromised.\n\n## AI features, assistants and agents\n\nThese rules apply wherever the Service uses a model on your behalf — an assistant, a generated document, an\nautonomous agent, a connected tool endpoint, or a feature you drive with your own provider key. They sit on top\nof everything else in this policy, and alongside the AI terms in our [Terms of Service](https://ever.co/tos).\n\n**Anything an agent does under your credentials is your act.** Automating a decision does not move\nresponsibility for it.\n\n### Do not generate unlawful, deceptive or infringing content\n\n- Content that is unlawful, defamatory, harassing or discriminatory. The rest of this policy applies to\n generated output exactly as it applies to text you typed yourself.\n- Fraud material — phishing text, fake invoices, scam messages, or anything designed to deceive a person into\n parting with money, credentials or access.\n- Impersonation of a real person or organisation, including synthetic voice, image or video of a real person\n without their agreement, and content presented as authentic when it is not.\n- Fabricated facts about a named person or business: reviews, testimonials, endorsements, qualifications,\n awards, or claims about their conduct, finances or history.\n- Content that infringes someone else's rights, and output presented as original where it is not.\n- Bulk low-value content produced to manipulate search rankings — doorway pages, mirror sites, near-duplicate\n sites generated at scale, cloaking and link schemes.\n- Removing or falsifying provenance metadata or watermarks that mark content as machine-generated, and passing\n model output off as human-created where doing so misleads someone whose decision depends on it.\n\n### Do not make consequential decisions about people without human review\n\n**Model output is an input to a decision. It is never the decision.**\n\nWhere a decision materially affects a person — hiring, promotion, discipline, dismissal, pay, credit, insurance,\ntenancy, education, benefits, access to essential services, or legal and immigration status — you must not treat\na score, ranking, band, signal, summary or recommendation produced through the Service as the sole or\ndeterminative basis for it. **A human being with authority and real discretion must consider the case and be\nable to reach a different answer.**\n\nThat applies with particular force to anything derived from monitoring. An activity percentage, a productivity\nscore, a screenshot summary or an attention metric is not a finding about a person's performance, and treating\nit as one is both a breach of this policy and, in many places, a breach of the law.\n\nYou must not use these features to discriminate on a protected characteristic, directly or through a proxy for\none. **Where we find a customer doing this, we may switch the feature off for that Workspace.**\n\n### Do not present output as professional advice\n\nDo not use the Service to give medical diagnosis or treatment decisions, clinical decision support, legal\nadvice, or financial and investment advice in a way that a recipient would reasonably take as coming from a\nqualified professional. Do not use it in the design or development of weapons.\n\n### Do not attack the models or the pipeline\n\n- **No attempts to extract training data, model weights, system prompts, tool definitions, configuration, or\n another customer's data or prompts.**\n- **No prompt injection.** Do not place instructions in content, files, profile fields, repositories, tickets,\n commits or messages that are designed to make an assistant ignore its policies, act outside its permissions,\n operate on another party's data, call a tool it was not authorised to call, or disclose secrets.\n- **No circumventing safety measures** — content filters, approval gates, human-in-the-loop confirmations, usage\n limits or policy checks. That includes automating a confirmation so an action is taken without a real human\n decision behind it. **The approval gates are load-bearing. Defeating one is a severe breach and we may block\n access immediately.**\n- No using our AI endpoints as a general-purpose relay: proxying traffic, reaching internal or arbitrary hosts,\n or pushing work unrelated to your use of the Service through us to a provider.\n- No supplying provider credentials you are not entitled to use, and no sending a provider content you have no\n right to send it. Where you bring your own key, that provider's terms bind you as well as ours do.\n\n### Do not compete with what you are using\n\nDo not use the Service, its output or its features to develop, train, fine-tune, distil or benchmark a competing\nmodel or product, and do not resell, sublicense or transfer model access obtained through us.\n\n## Fair use and published limits\n\nEvery plan has limits. **We publish them, rather than leaving \"fair use\" to mean whatever we decide later.**\n\n### Where the numbers are\n\nThe limits that apply to you are in your plan description or Order, in the Documentation for the Service, and in\nthe product-specific section of this policy. Where the same limit appears in more than one of those, the one in\nyour Order wins.\n\nDepending on the product, they cover:\n\n- API request rate, and the burst allowance above it;\n- concurrent connections — streaming, websocket, agent and tool endpoints;\n- total stored data per Workspace, and the size of any single upload;\n- capture and media volume, where the product records screenshots, recordings or other media;\n- outbound message volume and sending rate;\n- agent, job or build run time; and\n- seats, Workspaces and connected integrations.\n\n### What \"unlimited\" means when we say it\n\nWhere a plan is described as unlimited, or as fair use, it means **unlimited normal use of the product as it is\nsold** — not permission to use us as generic storage, generic compute or a content delivery network. When your\nusage stops resembling use of the product, it stops being covered by the word.\n\n### How limits are applied\n\nRate limits are enforced technically: over the limit you get an error and a retry signal, not a surprise\ninvoice. **We do not bill overage that was not in your Order.**\n\nWhere a storage or volume ceiling is exceeded, we contact you first and give you a reasonable period to reduce\nusage or move to a plan that fits before we restrict anything. Free and trial plans are the exception, and the\nresource abuse section above says how.\n\n### When limits change\n\nWe may change published limits. Where a change materially reduces what you can do on a plan you are paying for,\nwe give you notice in the way the changes section of our [Terms of Service](https://ever.co/tos) requires, and\nyou may cancel before it takes effect. Increases, and changes to free-plan limits, take effect when we publish\nthem.\n\nIf you have a genuine need above a published limit, ask us at legal@ever.co. **We would much rather agree a\nhigher limit with you in advance than discover the traffic.**\n\n## Reporting abuse\n\n**abuse@ever.co** — one address, read by people, for anything on this page.\n\n**You do not have to be our customer to use it.** We publish it for the person with no other route: a worker who\nbelieves they are being monitored covertly, someone who received a message they never asked for, a rights\nholder, a researcher, a works council, a parent, a regulator. Reports from people who are not customers get the\nsame handling as reports from people who are.\n\n### What to tell us\n\nThe more of this you can give us, the faster we can act. Send what you have — an incomplete report is still\nworth sending.\n\n- **What happened**, in your own words.\n- **Where** — the URL, share link, workspace, sending address, message headers, or the name of the application\n or agent involved. Precise enough that we can find it without guessing.\n- **When**, with dates, times and the time zone you are quoting.\n- **Who is affected**, if you can say, including whether that is you.\n- **Evidence** — headers, message ids, screenshots, links. Attach it where you can, rather than describing it.\n- **What you are asking for** — content removed, messages stopped, monitoring investigated, information.\n- **How to reach you**, if you want an answer. You may report anonymously, but we then cannot come back to you\n for the detail that often decides a case.\n\nSome reports have a better route. A request about your own personal data goes to privacy@ever.co. A security\nvulnerability goes through the coordinated disclosure route in the security violations section above. An\nintellectual property complaint needs the specific details listed in the infringing content section.\n\n**If you are reporting suspected covert monitoring, say so in the first line.** Those go to the front of the\nqueue.\n\n### What we do with it\n\n- **We acknowledge within two business days.**\n- **We give you a substantive answer, or a real status update, within ten business days.** Investigations that\n involve a customer's own workforce sometimes take longer than that. Where they do we will tell you where it\n has got to rather than going quiet on you.\n- **Where a person is at immediate risk, we act first and correspond afterwards.**\n- **We keep the reporter's identity confidential.** We do not pass it to the customer without your agreement\n unless the law compels us, and where that happens we will tell you if we are permitted to.\n- We tell you the outcome in general terms. **We will not hand you another party's account details, internal\n correspondence or personal data**, however much you would like us to. The same protection applies to you.\n\n### What we are not\n\nWe are not a court and we are not an arbitrator. Where a report is really a commercial or contractual dispute\nbetween you and someone else, we will say so and decline to take a side. We enforce our own rules against our\nown customers — that is the whole of our jurisdiction.\n\n**Deliberately false reports, and automated or mass reporting used as a weapon, are themselves a breach of this\npolicy.** Being wrong in good faith is not. We would far rather read a hundred honest reports that come to\nnothing than miss the one that mattered.\n\n## Enforcement\n\n### How we decide\n\nWe aim to be proportionate: the smallest action that actually stops the problem, applied to the narrowest part\nof the account that will do it. We weigh how serious the conduct is, whether anyone is being harmed right now,\nwhether it looks deliberate, whether it is still going on, and what you did when we raised it.\n\n**We also judge you by what you do about abuse by the people using the Service under your Subscription.** A\ncustomer whose End Users cause a problem and who moves quickly to stop it is in a very different position from\none who cannot or will not.\n\n### Investigation\n\nWe may look into a report, or into something we detect ourselves. That can include reviewing account and\nconfiguration metadata, logs, message headers, sending records, public-facing content, and content you have made\navailable to us — and asking you for evidence: the notice you gave your monitored personnel, your opt-in\nrecords, your right to use content, your authority for an integration.\n\n**We do not routinely read the contents of your Workspace.** Where an investigation genuinely requires looking\nat Customer Data, we look at the minimum needed, restrict it to staff who need it, and record that we did.\n\nWe may preserve material relevant to an investigation, and we may hold an account in a restricted state while we\nwork.\n\n### What we can do\n\n- Ask you to fix it, with a deadline.\n- Remove, disable or de-publish specific content, a public page, a share link or a custom domain.\n- Restrict or switch off a specific feature for a Workspace or a user — **including capture and monitoring\n features**.\n- Reduce a rate limit, throttle traffic, pause a campaign, or revoke a sending domain.\n- Suspend a user, a Workspace, a project or the whole account.\n- Terminate your account and these Terms.\n- Decline to contract with you again.\n- Recover our costs, where the law allows it.\n\n### With or without notice\n\n**Where the problem can be fixed, we tell you first and give you a chance to fix it.** That is the normal path\nand most matters end there.\n\n**We act immediately, without prior notice, where waiting would be irresponsible** — including:\n\n- anything in the never-permitted list in the illegal activity section;\n- covert or unlawful monitoring of a person;\n- malware, phishing, or a live security incident;\n- conduct putting shared infrastructure, other customers or sending reputation at risk;\n- a court order, a regulator's direction, a law-enforcement requirement or a takedown obligation; and\n- abuse that continues after we have already raised it with you.\n\nWhere we act without notice we tell you as soon as we reasonably can — what we did, why, and what would have to\nchange for us to undo it — unless a legal obligation stops us. Suspension is also dealt with in the term,\nsuspension and termination section of our [Terms of Service](https://ever.co/tos), and everything there applies\nhere.\n\n### Telling other people\n\nWhere the law requires it, we notify affected people, rights holders and authorities, and we respond to\nregulators, courts and law enforcement. Where someone's safety is at risk, we may notify without being required\nto. We may also tell a mailbox provider, a blocklist operator or a source platform what we did about a complaint\nthey sent us.\n\n**Some legal demands prohibit us from telling you that they exist.** Where that is the case, we comply with the\ndemand.\n\n### Money\n\n**Where we terminate because you broke this policy, you get no refund.**\n\n- Fees for a period already served remain payable.\n- A period during which the account was suspended for abuse is not refunded. It is still part of your paid term.\n- The 30-day money-back guarantee in our Refund Policy is not available on a termination for breach of this\n policy.\n- The export window we allow after an ordinary termination may be withheld where we terminated for cause, as our\n [Terms of Service](https://ever.co/tos) sets out.\n\nYour indemnity in those Terms covers claims brought against us because of what you or your End Users did in\nbreach of this policy.\n\n### If we get it wrong\n\nWe will sometimes get it wrong. Automated detection produces false positives, and reports are sometimes mistaken\nor malicious.\n\n**Write to legal@ever.co and we will look again** — with someone who was not part of the original decision,\nwherever we practically can. If we were wrong we restore access, and we do not charge you for the period we took\nit away. Tell us anything that changes the picture: a decision made on partial information is exactly the kind\nwe want to revisit.\n\n### Two things this section does not do\n\n**It does not oblige us to monitor.** We have no general duty to review what you put into the Service, and\nchoosing not to act on one thing never gives up our right to act on another. Acting in good faith on a report\ndoes not make us responsible for what someone else did.\n\n**It does not take away a consumer's rights.** If you are dealing with us as a consumer rather than for business\npurposes, your mandatory statutory rights stand whatever this section says.\n\n## Changes to this policy\n\nAbuse moves faster than contracts do, so this policy changes more often than the rest of our documents.\n**Every version carries a number and an effective date at the top, and superseded versions stay published**, so\nyou can always establish which rules applied on a given day.\n\n**Where a change materially reduces what you are allowed to do**, we give you at least thirty (30) days' notice\nbefore it takes effect — by email to your administrative contact and in the Service — and you may cancel before\nit applies, on the terms in the changes section of our [Terms of Service](https://ever.co/tos).\n\n**Everything else takes effect when we publish it.** That covers new examples of conduct this policy already\nprohibits, clarifications, corrections, and changes we make because the law, a regulator, a court, a payment\nprovider or an infrastructure provider requires them — sometimes at no notice at all, because we are given none.\n\nThe version in force when you use the Service is the version that governs that use. Continuing to use the\nService after a change has taken effect means you accept it.\n\n## How to reach us\n\nWrite to a person, not a form. These addresses are monitored and we answer them.\n\n- **Abuse, harmful content, covert monitoring, spam, or a security problem** — abuse@ever.co. **Anyone may\n use this address, customer or not.**\n- **Questions about this policy, or about a decision we made under it** — legal@ever.co\n- **Your personal data, and any request about it** — privacy@ever.co\n\nBy post: **Ever Technologies LTD**, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — registered in Bulgaria under company number\n204599535.\n\nWe correspond in English.\n\nThis document is version 1.0.0 of the Acceptable Use Policy for\n[ever.co](https://ever.co), in force from 2026-08-02. It forms part of our\n[Terms of Service](https://ever.co/tos), and earlier versions, with the dates they applied, are published\nalongside them."
|
|
301
|
+
"markdown": "# Acceptable Use Policy\n\n**Ever** — [ever.co](https://ever.co)\n\nVersion 1.0.2 · In force from 2026-08-02\n\nThis Acceptable Use Policy (\"**AUP**\") sets out what may and may not be done with the Ever website and\nthe websites, applications and application programming interfaces we make available at\n[ever.co](https://ever.co) (together, the \"**Service**\").\n\nIt forms part of our [Terms of Service](https://ever.co/tos) and uses the words defined there. **Breaking a\nrule in this policy is a breach of those Terms**, and the enforcement section below sets out what we do about\nit.\n\nWe have kept it specific. A policy that only says \"do not misuse the Service\" tells nobody anything and\nprotects nobody — least of all the people our software can be pointed at.\n\n## Who this policy applies to\n\n- **You**, as the customer holding the Subscription.\n- **Your End Users** — everyone you invite into your Workspace, whether an employee, a contractor, a client or\n a colleague. **What they do in the Service counts as your act**, and it is your job to make sure they know\n these rules.\n- **Anyone else who reaches the Service through you** — a person you send a share link to, a person who\n receives a message sent through the Service, anyone using access you granted.\n- **Visitors** to our public websites, documentation and community channels, and anyone using our public\n forms, endpoints or APIs.\n\nYou do not need an account for this policy to apply to you. Using the Service in any way means these rules\napply to what you do with it.\n\n## What this policy does not apply to\n\n**Self-hosted deployments.** Where our software is published as open source, that code is licensed to you\nunder its own licence, and **this policy imposes nothing on you as a self-hoster**. It governs the hosted\nService we operate and nothing else. Nothing here adds a restriction to any open-source licence — the\nopen-source carve-out in our [Terms of Service](https://ever.co/tos) explains the split.\n\n**Lawful workplace monitoring.** Some of our products exist to measure how work happens, and this policy does\nnot prohibit using them for that. What it prohibits is doing it covertly, doing it to people who were never\ntold, and doing it to people who are not yours to monitor. That distinction is drawn deliberately, and in\ndetail, in the privacy and surveillance section below.\n\n## How it fits with everything else\n\n- The product-specific section of this policy adds rules for the particular Service you use. **Where a core\n rule and a product rule both apply, follow the stricter one.**\n- Where your Order, a written agreement with us, or the Documentation permits something this policy would\n otherwise forbid — an agreed rate limit, an authorised security test — that permission governs, for that\n thing only.\n- The examples here are examples. They show what we mean; they are not a complete list of everything that can\n be done wrong. Conduct that is plainly within the spirit of a prohibition is prohibited.\n\n**We are not obliged to monitor what you do in the Service, and we do not routinely read the contents of your\nWorkspace.** We do act on what we find and on what is reported to us, and not acting on one thing never waives\nour right to act on another.\n\n## Illegal and harmful activity\n\nDo not use the Service to do anything unlawful, to help someone else do it, or to conceal that it is being\ndone. **Something is out of bounds here if it is unlawful where you are, where we operate, or where the person\naffected by it is** — you do not get to pick the most permissive of the three.\n\n### Never, under any circumstances\n\nSome conduct has no lawful version and gets no benefit of the doubt. **We terminate immediately for it, we\npreserve what we hold, and we report it to the authorities where the law requires that or where a person is at\nrisk:**\n\n- child sexual abuse material, and sexualised content involving a minor in any form;\n- content that grooms, solicits or endangers a child;\n- non-consensual intimate imagery, and threats to publish it;\n- terrorist content, and material that incites, promotes or gives instruction for terrorism or mass violence;\n- credible threats of serious violence against a person or a group;\n- human trafficking, forced labour, and the sale or exploitation of people.\n\nThere is no enforcement ladder for this list and no cure period.\n\n### Fraud and deception\n\n- Fraud of any kind — payment fraud, invoice fraud, business email compromise, advance-fee schemes, pyramid\n and Ponzi arrangements.\n- Phishing, credential harvesting, and pages or messages built to be mistaken for someone else's.\n- Card testing, use of stolen or unauthorised payment instruments, chargeback abuse, money laundering, and\n moving the proceeds of crime.\n- Impersonating a person, a company, a public body or us; using a false identity; forging message headers or\n sender identities.\n- Fabricated reviews, testimonials, endorsements, certifications, awards or qualifications.\n- **Falsifying records the Service generates or holds** — including tampering with a timer, tracker, activity\n log or timesheet to misstate work done or time worked. Where that record is evidence between you and your\n own employer or customer, falsifying it is fraud against them and a breach of this policy against us.\n\n### Unlawful goods, services and content\n\nDo not use the Service to offer, advertise, arrange, broker or deliver: controlled substances and unlicensed\npharmaceuticals; weapons, ammunition or their components; counterfeit goods; stolen property, stolen data or\nstolen credentials; unlicensed gambling; or anything else you are not licensed to provide where you provide it.\n\nWhere your business is lawful but regulated — health, finance, insurance, legal services, alcohol, tobacco,\nage-restricted goods — **holding the right licences, giving the right disclosures and running the right\nverification and handover checks is yours to do.** We do not check any of it and we are not your compliance\nfunction.\n\n### Sanctions, export controls and embargoes\n\nYou must not use the Service, or allow it to be used, in breach of applicable sanctions or export-control law,\nor for or on behalf of a person or organisation subject to them. The compliance, export and sanctions section\nof our [Terms of Service](https://ever.co/tos) sets out what that means for your Subscription.\n\n### Interfering with the law\n\nDo not use the Service to obstruct a lawful investigation, evade a court order, conceal or destroy material you\nare required to keep, or defeat a removal, blocking or suppression obligation that applies to you.\n\n## Content that infringes someone else's rights\n\nYou need the right to put something into the Service before you put it there. That applies to files, images,\ntext, code, datasets, brand names, and anything an integration brings in on your behalf.\n\n### What is prohibited\n\n- Uploading, storing, publishing, sharing or distributing anything that infringes another person's copyright,\n trade marks, design rights, database rights, patents or trade secrets.\n- Importing or republishing datasets, catalogues, curated lists or harvested collections you have no right to\n use. **An openly licensed source is not an unconditional one** — attribution, share-alike and non-commercial\n conditions travel with the content, and honouring them is your job, not ours.\n- Using someone else's trade mark in a workspace name, project name, URL slug, custom domain or sending domain\n in a way that suggests a connection you do not have. That includes typosquats and look-alike domains.\n- Putting another party's confidential information into the Service where you have no right to disclose it:\n material under a non-disclosure agreement, another company's customer data, privileged or otherwise protected\n work.\n- Removing, obscuring or altering a copyright notice, licence text, attribution or provenance metadata.\n\n### Our own software and brand\n\nWhere a product is published as open source, its licence governs what you may do with the code — but do not\nstrip its licence headers or attribution, do not present a fork or a self-hosted deployment as a service we\noperate, do not redistribute a paid edition, and do not circumvent the limits of the tier you bought. What you\nmay do with our names, logos and other brand features is dealt with in the intellectual property section of our\n[Terms of Service](https://ever.co/tos).\n\n### Reporting infringement\n\nIf something on the Service infringes your rights, tell us at abuse@ever.co. We handle these as\nnotice-and-action complaints under the rules that apply to us as a hosting service in the European Union, and\na notice needs to give us:\n\n- what the right is and why you hold it, or your authority to act for the person who does;\n- exactly where the material is — a URL, share link, workspace or file path, precise enough that we can find it\n without guessing;\n- what the material infringes, and how;\n- a statement that you believe in good faith the use is not authorised by the rights holder, an agent or the\n law; and\n- how to reach you.\n\n### What happens next\n\nWe assess notices on their content, not on their volume or their tone.\n\nWhere a notice is well founded we remove or disable access to the material, and we tell the affected customer\nwhat we did and why, unless the law prevents us. **Where the customer tells us the notice is wrong, we pass\nthat back to the complainant and we may restore the material.** We are not the venue for deciding who owns\nwhat — a genuine ownership dispute belongs in a court, not in our inbox.\n\n**We terminate accounts that infringe repeatedly.** What counts as repeat is a judgement about the pattern and\nthe customer's response to it, not a fixed count we publish for people to stay just underneath.\n\n## Harassment, hate and abusive content\n\nMost of what goes into the Service is private business content in your own Workspace, and we are not the\nmanners police for it. These rules still apply to it, and **they apply with real force to anything you publish\nthrough the Service, send to another person through it, or point a share link at.**\n\n### Prohibited\n\n- **Harassment and bullying** — a course of conduct directed at a person that is intended to, or is reasonably\n likely to, intimidate, humiliate or distress them, including conduct continued after they have asked for it\n to stop.\n- **Threats** of violence, and content that celebrates or wishes serious harm on identifiable people.\n- **Stalking** — using the Service to follow, locate, contact or observe a person against their wishes. Where\n that involves our capture, recording or tracking features, the privacy and surveillance section below governs\n it and we treat it as the most serious category of breach we handle.\n- **Hate speech** — attacking or demeaning people because of race, ethnicity, national origin, religion,\n disability, age, sex, sexual orientation, gender identity or another protected characteristic.\n- **Doxxing** — publishing or sharing a person's private information without their agreement, or assembling it\n so that someone else can act on it. Home addresses, personal contact details, identity documents, location,\n medical and financial details all count.\n- **Sexual content involving a person who has not agreed to it being shared**, and any sexual content involving\n a minor. That second category is dealt with absolutely in the illegal activity section above.\n- **Adult content on public-facing surfaces we host for you**, unless we have agreed it in writing and it is\n lawful and age-gated where it is served.\n- **Abuse of our own people.** Threatening, abusive or discriminatory conduct towards our staff in support\n tickets, chat, calls, issue trackers or community channels. We will end the conversation, and if it continues\n we will end the relationship.\n\n### Content you publish for other people to see\n\nWhere the Service lets you publish something publicly — a page, a directory, a profile, a shared recording, a\npublic team — **you are the publisher of it, not us.** Keep other people's personal data out of it unless they\nknow and you have a basis for holding it there, provide a way for people to complain about what you have\npublished, and act on a reasoned objection rather than ignoring it. **You must not republish content that a\nperson has already had removed.**\n\nWhere you run something on our infrastructure that accepts contributions from the public, moderating it is your\nobligation. Our tools do not discharge it and our policy is not your policy.\n\n### Community and contribution channels\n\nOur public repositories, issue trackers, documentation sites and chat channels carry these rules plus any code\nof conduct published with them. Spam, off-topic promotion, brigading and abuse there are breaches of this\npolicy and we deal with them the same way.\n\n## Privacy and unlawful surveillance\n\n**This is the strictest section in this policy, and it is strict because of what our software can do.**\n\nSome of our products measure how work happens. Depending on the product and the settings your administrators\nchoose, they can capture screenshots, webcam stills, audio, screen recordings, keyboard and mouse activity\nrates, the applications and websites in use, location, and how long each of those lasted. Selling software that\ncan do that places a duty on us that a project-management tool does not carry, and this section is how we\ndischarge it.\n\n**Lawful, disclosed monitoring of your own personnel is a legitimate use of the Service. Covert monitoring is\nnot, and never will be.** Everything below follows from that one line.\n\n### Monitoring that is never permitted\n\nYou must not use the Service, or configure it, to do any of the following.\n\n- **Covert or secret monitoring of any person.** If the person being measured does not know it is happening, it\n is prohibited — whatever your reason, wherever you are, and whether or not you believe you have a lawful\n basis for the underlying processing.\n- **Monitoring anyone who has not been informed in the way their local law requires, before capture starts.**\n Telling someone afterwards is not notice. A line in a handbook they have never seen is not notice either,\n where their law demands more.\n- **Monitoring outside working hours, during breaks, on personal time, or on a person's own device**, without a\n lawful basis and their knowledge. Capture follows the work. It does not follow the person.\n- **Enabling screen capture, webcam stills, audio capture or screen recording where local law prohibits it**,\n restricts it to purposes you are not pursuing, or conditions it on a process you have not completed.\n- **Deploying a configuration the monitored person cannot see, pause, stop or exit.** Combining continuous or\n randomised capture with settings that stop a person closing the agent, logging out, or seeing that capture is\n running produces covert monitoring by construction, and we treat it as covert monitoring however it was\n arrived at.\n- **Monitoring anyone other than your own personnel in the course of their work.** The Service may be used to\n measure your employees, contractors and workers while they work for you. It may not be pointed at a partner,\n a family member, a housemate, a child, a customer, a competitor, a journalist, or any other person who is not\n yours to monitor. **Using our software as stalkerware is an immediate-termination breach and we will treat it\n as one.**\n- **Installing the desktop agent, browser extension or tracker on a device you do not own or control**, without\n the informed agreement of the person who does.\n- **Using captured data for a purpose the monitored person was not told about.** If they were told capture was\n for billing accuracy, it is not then available for discipline, performance ranking or redundancy selection.\n Purpose creep is a breach of this policy, not only of your own notice.\n- **Capturing where capture predictably exposes other people's confidential or special-category data** —\n clinical settings, legally privileged work, HR investigations, child-facing services, or a home where other\n people are visible or audible — unless capture is switched off for the people concerned.\n- **Defeating the controls that exist to protect people.** Do not work around a per-person or per-team disable,\n a blur setting, a retention limit, an excluded-application list or a capture-frequency limit in order to\n observe someone whose monitoring is meant to be off or reduced.\n\n### Other people's privacy, whatever product you use\n\nThese apply across the Service, not only to the products that measure work.\n\n- **Recording a call, meeting, screen or conversation without the notice or consent the law requires** from\n everyone involved. Several jurisdictions require every party to agree, and where participants are in\n different places the strictest rule among them is the one that governs.\n- Capturing another person's screen, device, session or account without their authorisation.\n- Using a browser extension's access to reach pages the person never intended to expose — personal banking,\n health portals, private messaging, personal webmail.\n- Harvesting personal data at scale, from us or from anywhere else, including collecting it in breach of\n another platform's terms, its rate limits or its technical protections.\n- Building biometric profiles, or inferring sensitive characteristics about people — health, beliefs, sexual\n orientation, union membership, immigration status — from anything the Service captures or holds.\n- Entering another person's personal data into our forms, or subscribing an address you do not control.\n- Putting special-category data into the Service without a lawful basis for it, or where your product annex\n states that the Service is not built to hold it.\n\n### What you promise us when you switch monitoring on\n\nBy enabling any capture or activity-measurement feature for a person, **you represent to us** that:\n\n- you are the controller of that processing, you have identified a valid lawful basis for it, and you\n understand that **consent is generally not a valid basis in an employment relationship**, because of the\n imbalance between the person asking and the person consenting;\n- you have given that person the information their law requires — what is captured, how often, why, who sees\n it, how long it is kept, and how to object — **before capture began**;\n- you have carried out a data protection impact assessment where one is required, and consulted your\n supervisory authority where the residual risk requires that;\n- you have completed any works council, trade union or employee-representative process required where that\n person works. **These are not formalities.** Co-determination in Germany, works council consent in Austria,\n works council approval in the Netherlands, prior union agreement or labour-inspectorate authorisation in\n Italy, and co-operation negotiations in Finland can each make a deployment unlawful, and the data it produced\n unusable, if they were skipped;\n- you will not enable capture for anyone in a jurisdiction that prohibits it. **Some do.** Supervision of\n performance by remote technical means is close to prohibited outright in Portugal, and keystroke and\n continuous-capture tooling has been held unlawful elsewhere on proportionality grounds; and\n- you are not using the Service to monitor covertly, or to monitor anyone outside a lawful monitoring programme\n of your own.\n\n**We make no claim that any configuration of the Service is lawful in any country.** This law differs sharply\nfrom one jurisdiction to the next and is still moving. We build the controls, publish what each one does, and\ngive you the material to run your own assessment. **The decision to switch monitoring on is yours, and so is\nthe liability that comes with it.** Your indemnity in our [Terms of Service](https://ever.co/tos) covers claims\nthat arise from breaking the representations above.\n\n### We act on credible reports of covert monitoring\n\n**Anyone can report suspected covert or unlawful monitoring to abuse@ever.co — you do not have to be our\ncustomer.** A monitored worker, a works council, an employee representative, a family member or a regulator can\nall use that address. We would far rather receive a report that turns out to be a misunderstanding than not\nreceive one at all.\n\nWhen we receive a credible report:\n\n- **we treat the reporter's identity as confidential.** We do not pass it to the customer without their\n agreement unless the law compels us. We know that the person best placed to report covert monitoring is\n usually the person with the most to lose by reporting it;\n- **we may require the customer to evidence** the notice it gave, the lawful basis it relies on, and the\n consultations it completed. \"Trust us\" is not evidence, and a customer that cannot produce any is treated as\n a customer that has none;\n- we may switch off specific capture features for that Workspace while we look, suspend the account, or\n terminate it, depending on what we find and how serious it is; and\n- **we will not take a customer's assurance over a credible report from the person being monitored.**\n\n**Retaliating against someone because they reported to us — dismissing them, disciplining them, withdrawing\ntheir work — is itself a breach of this policy**, and we will act on it against the customer that does it.\n\n## Security violations\n\nThe Service is shared infrastructure. The rules below protect other customers at least as much as they protect\nus.\n\n### Do not\n\n- **Access anything you were not given access to** — another customer's Workspace or data, another user's\n account, our internal systems, or any part of the Service behind a boundary you were not invited past.\n- **Probe, scan or test** the Service, our networks or our infrastructure for vulnerabilities without our prior\n written permission, except within the coordinated disclosure route below.\n- **Attack accounts** — credential stuffing, password spraying, brute forcing, or enumerating accounts and\n email addresses through sign-in, recovery or invitation endpoints.\n- **Enumerate or guess identifiers.** Share links, object ids, invitation tokens and export URLs are meant to\n be given to you, not discovered by you.\n- **Circumvent controls** — authentication, authorisation, session handling, tenant isolation, rate limits,\n quotas, access gates, licence-tier limits, or any technical protection measure.\n- **Interfere with the Service** — denial-of-service traffic, load designed or reasonably likely to degrade the\n Service for others, or any attempt to cross the isolation between one Workspace and another.\n- **Reverse engineer, decompile or disassemble** the Service, except to the extent an applicable open-source\n licence or a law that cannot be excluded permits it.\n- **Turn the Service into infrastructure for something else** — an open relay or proxy, an anonymisation or VPN\n service, a command-and-control endpoint, a port scanner, a password-cracking rig, or a staging point for an\n attack on a third party.\n\n### Credentials and access\n\n- **Accounts are for one person.** Do not share a login, and do not hand an account from one person to the next\n as staff change — create and remove accounts instead.\n- Do not share API keys, tokens or seats outside the Workspace they were issued for, and do not leave them\n anywhere others can read them.\n- **Do not give us credentials you are not entitled to use** — a colleague's, a former employer's, a shared\n mailbox you do not control, or an access token, key or configuration file belonging to someone else.\n- Do not use the Service to store, distribute or trade credentials obtained from anyone else.\n- Keep your own credentials secure, turn on multi-factor authentication where we offer it, and **tell us at\n abuse@ever.co as soon as you suspect an account has been compromised.** Delay there costs other people,\n not only you.\n\n### Security research\n\nWe want to hear from researchers, and we will not pursue anyone who acts in good faith.\n\nYour testing is in scope if you work only against your own account and your own data; do not access, modify or\nretain another customer's data; stop at the point that demonstrates the issue rather than pushing further; avoid\ndegrading the Service or causing a privacy impact; do not run automated scanning at volume; and report to us\npromptly and privately at abuse@ever.co before disclosing anywhere else.\n\n**Testing against another customer's Workspace or data is never in scope**, whatever your intent. How we handle\nreports, and what we commit to in return, is set out on our Security page.\n\n## Resource abuse\n\nYou share compute, storage, bandwidth and outbound sending reputation with every other customer. Use your\nshare.\n\n### Do not\n\n- Mine cryptocurrency, run distributed computing, or use the Service for processing that has nothing to do with\n what the Service is for.\n- Use our storage or bandwidth as a general-purpose content delivery network, a file-distribution service, a\n backup target for unrelated data, or a home for media we had no part in producing — including hot-linking\n files held with us into other sites.\n- Run automated bulk extraction against the Service, our websites, our documentation or our APIs. **Issued API\n credentials used within their documented scope and rate limits are exactly what they exist for**; scraping the\n interface, or driving an API past its published limits, is not.\n- Run unbounded or pathological workloads — agent or job loops with no termination condition, retry storms,\n runaway automation, or deliberately expensive requests repeated to see what happens.\n- Hold sessions, connections or reserved capacity open purely to keep hold of them.\n- Evade a limit rather than raise it: extra accounts to farm a free allowance, disposable addresses, referral or\n credit gaming, seat sharing, or a second Workspace created because the first one hit its ceiling.\n\n### Free plans and trials\n\nFree and trial access exists so that you can evaluate the Service and so that small teams can use it. It is not\nanonymous infrastructure. **Limits on free plans are tighter, are enforced at our discretion, and can change\nwithout notice.** We may reclaim idle free resources, and we may decline to keep providing a free plan to an\naccount whose consumption is out of proportion to what free access is for.\n\n### How we handle it\n\nSustained load that is normal for your plan is fine. Bursting is fine. What we act on is load that degrades the\nService for other people, load that is not really use of the product at all, and load that keeps growing after\nwe have asked about it.\n\n**Our first step is normally to contact you, not to cut you off.** We would rather move you onto a plan or a\nlimit that fits than lose you over a number. We throttle before we suspend, and we suspend without warning only\nwhere the platform or other customers are at risk.\n\nIf your usage above a published limit is a genuine business need rather than abuse, write to legal@ever.co\nand we will look at raising it. The numbers themselves are in the fair use section below, in your plan or Order,\nand in the Documentation.\n\n## Spam and unsolicited messaging\n\nThe Service sends mail, invitations, notifications and, in some products, text messages — sometimes from our\nown sending domains and on our own reputation. That makes messaging abuse everybody's problem here: one\ncustomer's cold-outreach campaign is what gets every other customer's invoices and password resets filtered.\n\n### Do not\n\n- **Send unsolicited bulk email, SMS or messages of any kind through the Service**, or use it to prepare, host\n or support a campaign that someone else sends.\n- **Mail a list you cannot stand behind.** You must be able to show us, on request, how each recipient came to\n be on it. Purchased, rented, swapped, harvested and scraped lists are prohibited, and so are address guessing,\n permutation and dictionary attacks.\n- **Spoof or falsify** a sender identity, a header, a reply path or a domain, or send from a domain you do not\n control. Where you send through the Service, configure SPF, DKIM and DMARC for your own domain, respect any\n warm-up schedule and sending rate we set, and keep a working reply path that a human reads.\n- **Strip, hide, disable or visually suppress** an unsubscribe link, a `List-Unsubscribe` header, a required\n postal address, or any compliance footer the Service adds. **Making the opt-out hard to find is the same\n breach as not having one.**\n- **Ignore an opt-out.** Suppression must be honoured promptly and permanently. No re-importing a suppressed\n person, no refreshing them from another source, no moving them into a second Workspace or account to escape\n the suppression list, and no treating an unsubscribe click as an engagement signal.\n- **Repurpose our transactional messages as a marketing channel.** Invitations, verification mails, share\n notifications, estimates, invoices and system notices exist to carry their own content — not to carry an offer\n to someone who never asked for one.\n- **Use invitations to reach people who will not be working in your Workspace.** The invitation flow is a\n foreseeable spam vector and we watch it.\n- **Abuse our own public endpoints** — automated submissions to our contact, newsletter or support forms,\n repeated submissions used to bomb a third party's mailbox through them, or link injection into free-text\n fields.\n\n### The law applies to you, and we do not check it for you\n\nElectronic marketing to individuals is regulated separately from data protection. Depending on where your\nrecipients are you may need prior opt-in, and the existing-customer exception is much narrower than most senders\nassume. **Working out which rule covers which recipient is yours to do.** Nothing the Service does — including\nany compliance footer it adds for you — makes a message lawful that would not otherwise be.\n\n### Deliverability is an enforcement trigger\n\nWe monitor bounce rates, spam complaints, blocklist entries and mailbox-provider feedback for traffic sent\nthrough the Service. **Where a sender's numbers put shared reputation at risk we act immediately and without\nnotice** — pausing a campaign, throttling or suspending sending, revoking a sending domain, or suspending the\naccount. We do the same on a credible complaint from a recipient, a mailbox provider or a blocklist operator.\n\nIf you received a message from someone using the Service and you did not ask for it, report it to\nabuse@ever.co with the full headers if you have them.\n\n## Malware and hostile files\n\n### Do not upload, store, link to or distribute\n\n- **Malware of any kind** — viruses, worms, trojans, ransomware, rootkits, keyloggers, spyware and stalkerware.\n- **Exploit code, exploit kits, cracking and credential-stuffing tools**, and payloads intended to establish or\n keep unauthorised access to anything.\n- **Files built to attack whatever opens them** — decompression bombs, entity-expansion payloads, deliberately\n malformed documents, and uploads crafted to break a parser, a preview renderer or a downstream viewer.\n- **Values crafted to execute somewhere else.** Text you put into a field that is later exported — a name, a\n translation string, a note, a description — must not be built to run as a formula, a script or a command in\n whatever opens the export.\n- **Phishing and credential-harvesting pages**, fake sign-in screens, and deceptive destinations of any kind.\n **A link on our domain lends our credibility to whatever it points at**, which is exactly why share links\n attract this and exactly why we move fast on it.\n\n### We scan, and we are telling you so\n\nWe may scan, sandbox, quarantine, refuse, disable or delete files, links and messages that we reasonably believe\nare hostile, and we may do it without prior notice.\n\n**We are stating this openly because scanning your uploads is itself a processing activity, and undisclosed\nprocessing is not something we are willing to do.** What it means for personal data is set out in our\n[Privacy Policy](https://ever.co/privacy).\n\nAutomated detection is imperfect in both directions. If we have quarantined something wrongly, tell us at\nabuse@ever.co and we will look again.\n\n### Security work with a legitimate need\n\nIf your work genuinely involves handling malware samples — you run a security team, or you research this for a\nliving — do not do it in the Service without asking us first. Write to legal@ever.co, tell us what you need\nand how it will be contained, and we will either agree it in writing or tell you no. **Doing it without that\nagreement is a breach**, however good the reason.\n\n### Your own hygiene\n\nKeep the devices and networks you use to reach the Service reasonably secure and up to date, and tell us at\nabuse@ever.co if you believe a device with access to your Workspace has been compromised.\n\n## AI features, assistants and agents\n\nThese rules apply wherever the Service uses a model on your behalf — an assistant, a generated document, an\nautonomous agent, a connected tool endpoint, or a feature you drive with your own provider key. They sit on top\nof everything else in this policy, and alongside the AI terms in our [Terms of Service](https://ever.co/tos).\n\n**Anything an agent does under your credentials is your act.** Automating a decision does not move\nresponsibility for it.\n\n### Do not generate unlawful, deceptive or infringing content\n\n- Content that is unlawful, defamatory, harassing or discriminatory. The rest of this policy applies to\n generated output exactly as it applies to text you typed yourself.\n- Fraud material — phishing text, fake invoices, scam messages, or anything designed to deceive a person into\n parting with money, credentials or access.\n- Impersonation of a real person or organisation, including synthetic voice, image or video of a real person\n without their agreement, and content presented as authentic when it is not.\n- Fabricated facts about a named person or business: reviews, testimonials, endorsements, qualifications,\n awards, or claims about their conduct, finances or history.\n- Content that infringes someone else's rights, and output presented as original where it is not.\n- Bulk low-value content produced to manipulate search rankings — doorway pages, mirror sites, near-duplicate\n sites generated at scale, cloaking and link schemes.\n- Removing or falsifying provenance metadata or watermarks that mark content as machine-generated, and passing\n model output off as human-created where doing so misleads someone whose decision depends on it.\n\n### Do not make consequential decisions about people without human review\n\n**Model output is an input to a decision. It is never the decision.**\n\nWhere a decision materially affects a person — hiring, promotion, discipline, dismissal, pay, credit, insurance,\ntenancy, education, benefits, access to essential services, or legal and immigration status — you must not treat\na score, ranking, band, signal, summary or recommendation produced through the Service as the sole or\ndeterminative basis for it. **A human being with authority and real discretion must consider the case and be\nable to reach a different answer.**\n\nThat applies with particular force to anything derived from monitoring. An activity percentage, a productivity\nscore, a screenshot summary or an attention metric is not a finding about a person's performance, and treating\nit as one is both a breach of this policy and, in many places, a breach of the law.\n\nYou must not use these features to discriminate on a protected characteristic, directly or through a proxy for\none. **Where we find a customer doing this, we may switch the feature off for that Workspace.**\n\n### Do not present output as professional advice\n\nDo not use the Service to give medical diagnosis or treatment decisions, clinical decision support, legal\nadvice, or financial and investment advice in a way that a recipient would reasonably take as coming from a\nqualified professional. Do not use it in the design or development of weapons.\n\n### Do not attack the models or the pipeline\n\n- **No attempts to extract training data, model weights, system prompts, tool definitions, configuration, or\n another customer's data or prompts.**\n- **No prompt injection.** Do not place instructions in content, files, profile fields, repositories, tickets,\n commits or messages that are designed to make an assistant ignore its policies, act outside its permissions,\n operate on another party's data, call a tool it was not authorised to call, or disclose secrets.\n- **No circumventing safety measures** — content filters, approval gates, human-in-the-loop confirmations, usage\n limits or policy checks. That includes automating a confirmation so an action is taken without a real human\n decision behind it. **The approval gates are load-bearing. Defeating one is a severe breach and we may block\n access immediately.**\n- No using our AI endpoints as a general-purpose relay: proxying traffic, reaching internal or arbitrary hosts,\n or pushing work unrelated to your use of the Service through us to a provider.\n- No supplying provider credentials you are not entitled to use, and no sending a provider content you have no\n right to send it. Where you bring your own key, that provider's terms bind you as well as ours do.\n\n### Do not compete with what you are using\n\nDo not use the Service, its output or its features to develop, train, fine-tune, distil or benchmark a competing\nmodel or product, and do not resell, sublicense or transfer model access obtained through us.\n\n## Fair use and published limits\n\nEvery plan has limits. **We publish them, rather than leaving \"fair use\" to mean whatever we decide later.**\n\n### Where the numbers are\n\nThe limits that apply to you are in your plan description or Order, in the Documentation for the Service, and in\nthe product-specific section of this policy. Where the same limit appears in more than one of those, the one in\nyour Order wins.\n\nDepending on the product, they cover:\n\n- API request rate, and the burst allowance above it;\n- concurrent connections — streaming, websocket, agent and tool endpoints;\n- total stored data per Workspace, and the size of any single upload;\n- capture and media volume, where the product records screenshots, recordings or other media;\n- outbound message volume and sending rate;\n- agent, job or build run time; and\n- seats, Workspaces and connected integrations.\n\n### What \"unlimited\" means when we say it\n\nWhere a plan is described as unlimited, or as fair use, it means **unlimited normal use of the product as it is\nsold** — not permission to use us as generic storage, generic compute or a content delivery network. When your\nusage stops resembling use of the product, it stops being covered by the word.\n\n### How limits are applied\n\nRate limits are enforced technically: over the limit you get an error and a retry signal, not a surprise\ninvoice. **We do not bill overage that was not in your Order.**\n\nWhere a storage or volume ceiling is exceeded, we contact you first and give you a reasonable period to reduce\nusage or move to a plan that fits before we restrict anything. Free and trial plans are the exception, and the\nresource abuse section above says how.\n\n### When limits change\n\nWe may change published limits. Where a change materially reduces what you can do on a plan you are paying for,\nwe give you notice in the way the changes section of our [Terms of Service](https://ever.co/tos) requires, and\nyou may cancel before it takes effect. Increases, and changes to free-plan limits, take effect when we publish\nthem.\n\nIf you have a genuine need above a published limit, ask us at legal@ever.co. **We would much rather agree a\nhigher limit with you in advance than discover the traffic.**\n\n## Reporting abuse\n\n**abuse@ever.co** — one address, read by people, for anything on this page.\n\n**You do not have to be our customer to use it.** We publish it for the person with no other route: a worker who\nbelieves they are being monitored covertly, someone who received a message they never asked for, a rights\nholder, a researcher, a works council, a parent, a regulator. Reports from people who are not customers get the\nsame handling as reports from people who are.\n\n### What to tell us\n\nThe more of this you can give us, the faster we can act. Send what you have — an incomplete report is still\nworth sending.\n\n- **What happened**, in your own words.\n- **Where** — the URL, share link, workspace, sending address, message headers, or the name of the application\n or agent involved. Precise enough that we can find it without guessing.\n- **When**, with dates, times and the time zone you are quoting.\n- **Who is affected**, if you can say, including whether that is you.\n- **Evidence** — headers, message ids, screenshots, links. Attach it where you can, rather than describing it.\n- **What you are asking for** — content removed, messages stopped, monitoring investigated, information.\n- **How to reach you**, if you want an answer. You may report anonymously, but we then cannot come back to you\n for the detail that often decides a case.\n\nSome reports have a better route. A request about your own personal data goes to privacy@ever.co. A security\nvulnerability goes through the coordinated disclosure route in the security violations section above. An\nintellectual property complaint needs the specific details listed in the infringing content section.\n\n**If you are reporting suspected covert monitoring, say so in the first line.** Those go to the front of the\nqueue.\n\n### What we do with it\n\n- **We acknowledge within two business days.**\n- **We give you a substantive answer, or a real status update, within ten business days.** Investigations that\n involve a customer's own workforce sometimes take longer than that. Where they do we will tell you where it\n has got to rather than going quiet on you.\n- **Where a person is at immediate risk, we act first and correspond afterwards.**\n- **We keep the reporter's identity confidential.** We do not pass it to the customer without your agreement\n unless the law compels us, and where that happens we will tell you if we are permitted to.\n- We tell you the outcome in general terms. **We will not hand you another party's account details, internal\n correspondence or personal data**, however much you would like us to. The same protection applies to you.\n\n### What we are not\n\nWe are not a court and we are not an arbitrator. Where a report is really a commercial or contractual dispute\nbetween you and someone else, we will say so and decline to take a side. We enforce our own rules against our\nown customers — that is the whole of our jurisdiction.\n\n**Deliberately false reports, and automated or mass reporting used as a weapon, are themselves a breach of this\npolicy.** Being wrong in good faith is not. We would far rather read a hundred honest reports that come to\nnothing than miss the one that mattered.\n\n## Enforcement\n\n### How we decide\n\nWe aim to be proportionate: the smallest action that actually stops the problem, applied to the narrowest part\nof the account that will do it. We weigh how serious the conduct is, whether anyone is being harmed right now,\nwhether it looks deliberate, whether it is still going on, and what you did when we raised it.\n\n**We also judge you by what you do about abuse by the people using the Service under your Subscription.** A\ncustomer whose End Users cause a problem and who moves quickly to stop it is in a very different position from\none who cannot or will not.\n\n### Investigation\n\nWe may look into a report, or into something we detect ourselves. That can include reviewing account and\nconfiguration metadata, logs, message headers, sending records, public-facing content, and content you have made\navailable to us — and asking you for evidence: the notice you gave your monitored personnel, your opt-in\nrecords, your right to use content, your authority for an integration.\n\n**We do not routinely read the contents of your Workspace.** Where an investigation genuinely requires looking\nat Customer Data, we look at the minimum needed, restrict it to staff who need it, and record that we did.\n\nWe may preserve material relevant to an investigation, and we may hold an account in a restricted state while we\nwork.\n\n### What we can do\n\n- Ask you to fix it, with a deadline.\n- Remove, disable or de-publish specific content, a public page, a share link or a custom domain.\n- Restrict or switch off a specific feature for a Workspace or a user — **including capture and monitoring\n features**.\n- Reduce a rate limit, throttle traffic, pause a campaign, or revoke a sending domain.\n- Suspend a user, a Workspace, a project or the whole account.\n- Terminate your account and these Terms.\n- Decline to contract with you again.\n- Recover our costs, where the law allows it.\n\n### With or without notice\n\n**Where the problem can be fixed, we tell you first and give you a chance to fix it.** That is the normal path\nand most matters end there.\n\n**We act immediately, without prior notice, where waiting would be irresponsible** — including:\n\n- anything in the never-permitted list in the illegal activity section;\n- covert or unlawful monitoring of a person;\n- malware, phishing, or a live security incident;\n- conduct putting shared infrastructure, other customers or sending reputation at risk;\n- a court order, a regulator's direction, a law-enforcement requirement or a takedown obligation; and\n- abuse that continues after we have already raised it with you.\n\nWhere we act without notice we tell you as soon as we reasonably can — what we did, why, and what would have to\nchange for us to undo it — unless a legal obligation stops us. Suspension is also dealt with in the term,\nsuspension and termination section of our [Terms of Service](https://ever.co/tos), and everything there applies\nhere.\n\n### Telling other people\n\nWhere the law requires it, we notify affected people, rights holders and authorities, and we respond to\nregulators, courts and law enforcement. Where someone's safety is at risk, we may notify without being required\nto. We may also tell a mailbox provider, a blocklist operator or a source platform what we did about a complaint\nthey sent us.\n\n**Some legal demands prohibit us from telling you that they exist.** Where that is the case, we comply with the\ndemand.\n\n### Money\n\n**Where we terminate because you broke this policy, you get no refund.**\n\n- Fees for a period already served remain payable.\n- A period during which the account was suspended for abuse is not refunded. It is still part of your paid term.\n- The 30-day money-back guarantee in our Refund Policy is not available on a termination for breach of this\n policy.\n- The export window we allow after an ordinary termination may be withheld where we terminated for cause, as our\n [Terms of Service](https://ever.co/tos) sets out.\n\nYour indemnity in those Terms covers claims brought against us because of what you or your End Users did in\nbreach of this policy.\n\n### If we get it wrong\n\nWe will sometimes get it wrong. Automated detection produces false positives, and reports are sometimes mistaken\nor malicious.\n\n**Write to legal@ever.co and we will look again** — with someone who was not part of the original decision,\nwherever we practically can. If we were wrong we restore access, and we do not charge you for the period we took\nit away. Tell us anything that changes the picture: a decision made on partial information is exactly the kind\nwe want to revisit.\n\n### Two things this section does not do\n\n**It does not oblige us to monitor.** We have no general duty to review what you put into the Service, and\nchoosing not to act on one thing never gives up our right to act on another. Acting in good faith on a report\ndoes not make us responsible for what someone else did.\n\n**It does not take away a consumer's rights.** If you are dealing with us as a consumer rather than for business\npurposes, your mandatory statutory rights stand whatever this section says.\n\n## Changes to this policy\n\nAbuse moves faster than contracts do, so this policy changes more often than the rest of our documents.\n**Every version carries a number and an effective date at the top, and superseded versions stay published**, so\nyou can always establish which rules applied on a given day.\n\n**Where a change materially reduces what you are allowed to do**, we give you at least thirty (30) days' notice\nbefore it takes effect — by email to your administrative contact and in the Service — and you may cancel before\nit applies, on the terms in the changes section of our [Terms of Service](https://ever.co/tos).\n\n**Everything else takes effect when we publish it.** That covers new examples of conduct this policy already\nprohibits, clarifications, corrections, and changes we make because the law, a regulator, a court, a payment\nprovider or an infrastructure provider requires them — sometimes at no notice at all, because we are given none.\n\nThe version in force when you use the Service is the version that governs that use. Continuing to use the\nService after a change has taken effect means you accept it.\n\n## How to reach us\n\nWrite to a person, not a form. These addresses are monitored and we answer them.\n\n- **Abuse, harmful content, covert monitoring, spam, or a security problem** — abuse@ever.co. **Anyone may\n use this address, customer or not.**\n- **Questions about this policy, or about a decision we made under it** — legal@ever.co\n- **Your personal data, and any request about it** — privacy@ever.co\n\nBy post: **Ever Technologies LTD**, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — registered in Bulgaria under company number\n204599535.\n\nWe correspond in English.\n\nThis document is version 1.0.2 of the Acceptable Use Policy for\n[ever.co](https://ever.co), in force from 2026-08-02. It forms part of our\n[Terms of Service](https://ever.co/tos), and earlier versions, with the dates they applied, are published\nalongside them."
|
|
302
302
|
}
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
<h1 id="acceptable-use-policy" tabindex="-1">Acceptable Use Policy</h1>
|
|
2
2
|
<p><strong>Ever Demand</strong> — <a href="https://everdemand.co">everdemand.co</a></p>
|
|
3
|
-
<p>Version 1.0.
|
|
3
|
+
<p>Version 1.0.2 · In force from 2026-08-02</p>
|
|
4
4
|
<p>This Acceptable Use Policy ("<strong>AUP</strong>") sets out what may and may not be done with Ever Demand and
|
|
5
5
|
the websites, applications and application programming interfaces we make available at
|
|
6
6
|
<a href="https://everdemand.co">everdemand.co</a> (together, the "<strong>Service</strong>").</p>
|
|
@@ -796,7 +796,7 @@ use this address, customer or not.</strong></li>
|
|
|
796
796
|
<p>By post: <strong>Ever Technologies LTD</strong>, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — registered in Bulgaria under company number
|
|
797
797
|
204599535.</p>
|
|
798
798
|
<p>We correspond in English.</p>
|
|
799
|
-
<p>This document is version 1.0.
|
|
799
|
+
<p>This document is version 1.0.2 of the Acceptable Use Policy for
|
|
800
800
|
<a href="https://everdemand.co">everdemand.co</a>, in force from 2026-08-02. It forms part of our
|
|
801
801
|
<a href="https://everdemand.co/tos">Terms of Service</a>, and earlier versions, with the dates they applied, are published
|
|
802
802
|
alongside them.</p>
|
|
@@ -6,9 +6,9 @@
|
|
|
6
6
|
"entity": "Ever Technologies LTD",
|
|
7
7
|
"entityId": "ever-technologies-bg",
|
|
8
8
|
"locale": "en",
|
|
9
|
-
"version": "1.0.
|
|
9
|
+
"version": "1.0.2",
|
|
10
10
|
"effectiveDate": "2026-08-02",
|
|
11
|
-
"sha256": "
|
|
11
|
+
"sha256": "3edeaff7f9e4d846097689ea3dba687322fe3300225a9bf7a21982921525ce2c",
|
|
12
12
|
"publishable": true,
|
|
13
13
|
"sections": [
|
|
14
14
|
"core/aup/010-scope",
|
|
@@ -335,5 +335,5 @@
|
|
|
335
335
|
}
|
|
336
336
|
],
|
|
337
337
|
"path": "content/aup/ever-demand/en.html",
|
|
338
|
-
"markdown": "# Acceptable Use Policy\n\n**Ever Demand** — [everdemand.co](https://everdemand.co)\n\nVersion 1.0.0 · In force from 2026-08-02\n\nThis Acceptable Use Policy (\"**AUP**\") sets out what may and may not be done with Ever Demand and\nthe websites, applications and application programming interfaces we make available at\n[everdemand.co](https://everdemand.co) (together, the \"**Service**\").\n\nIt forms part of our [Terms of Service](https://everdemand.co/tos) and uses the words defined there. **Breaking a\nrule in this policy is a breach of those Terms**, and the enforcement section below sets out what we do about\nit.\n\nWe have kept it specific. A policy that only says \"do not misuse the Service\" tells nobody anything and\nprotects nobody — least of all the people our software can be pointed at.\n\n## Who this policy applies to\n\n- **You**, as the customer holding the Subscription.\n- **Your End Users** — everyone you invite into your Workspace, whether an employee, a contractor, a client or\n a colleague. **What they do in the Service counts as your act**, and it is your job to make sure they know\n these rules.\n- **Anyone else who reaches the Service through you** — a person you send a share link to, a person who\n receives a message sent through the Service, anyone using access you granted.\n- **Visitors** to our public websites, documentation and community channels, and anyone using our public\n forms, endpoints or APIs.\n\nYou do not need an account for this policy to apply to you. Using the Service in any way means these rules\napply to what you do with it.\n\n## What this policy does not apply to\n\n**Self-hosted deployments.** Where our software is published as open source, that code is licensed to you\nunder its own licence, and **this policy imposes nothing on you as a self-hoster**. It governs the hosted\nService we operate and nothing else. Nothing here adds a restriction to any open-source licence — the\nopen-source carve-out in our [Terms of Service](https://everdemand.co/tos) explains the split.\n\n**Lawful workplace monitoring.** Some of our products exist to measure how work happens, and this policy does\nnot prohibit using them for that. What it prohibits is doing it covertly, doing it to people who were never\ntold, and doing it to people who are not yours to monitor. That distinction is drawn deliberately, and in\ndetail, in the privacy and surveillance section below.\n\n## How it fits with everything else\n\n- The product-specific section of this policy adds rules for the particular Service you use. **Where a core\n rule and a product rule both apply, follow the stricter one.**\n- Where your Order, a written agreement with us, or the Documentation permits something this policy would\n otherwise forbid — an agreed rate limit, an authorised security test — that permission governs, for that\n thing only.\n- The examples here are examples. They show what we mean; they are not a complete list of everything that can\n be done wrong. Conduct that is plainly within the spirit of a prohibition is prohibited.\n\n**We are not obliged to monitor what you do in the Service, and we do not routinely read the contents of your\nWorkspace.** We do act on what we find and on what is reported to us, and not acting on one thing never waives\nour right to act on another.\n\n## Illegal and harmful activity\n\nDo not use the Service to do anything unlawful, to help someone else do it, or to conceal that it is being\ndone. **Something is out of bounds here if it is unlawful where you are, where we operate, or where the person\naffected by it is** — you do not get to pick the most permissive of the three.\n\n### Never, under any circumstances\n\nSome conduct has no lawful version and gets no benefit of the doubt. **We terminate immediately for it, we\npreserve what we hold, and we report it to the authorities where the law requires that or where a person is at\nrisk:**\n\n- child sexual abuse material, and sexualised content involving a minor in any form;\n- content that grooms, solicits or endangers a child;\n- non-consensual intimate imagery, and threats to publish it;\n- terrorist content, and material that incites, promotes or gives instruction for terrorism or mass violence;\n- credible threats of serious violence against a person or a group;\n- human trafficking, forced labour, and the sale or exploitation of people.\n\nThere is no enforcement ladder for this list and no cure period.\n\n### Fraud and deception\n\n- Fraud of any kind — payment fraud, invoice fraud, business email compromise, advance-fee schemes, pyramid\n and Ponzi arrangements.\n- Phishing, credential harvesting, and pages or messages built to be mistaken for someone else's.\n- Card testing, use of stolen or unauthorised payment instruments, chargeback abuse, money laundering, and\n moving the proceeds of crime.\n- Impersonating a person, a company, a public body or us; using a false identity; forging message headers or\n sender identities.\n- Fabricated reviews, testimonials, endorsements, certifications, awards or qualifications.\n- **Falsifying records the Service generates or holds** — including tampering with a timer, tracker, activity\n log or timesheet to misstate work done or time worked. Where that record is evidence between you and your\n own employer or customer, falsifying it is fraud against them and a breach of this policy against us.\n\n### Unlawful goods, services and content\n\nDo not use the Service to offer, advertise, arrange, broker or deliver: controlled substances and unlicensed\npharmaceuticals; weapons, ammunition or their components; counterfeit goods; stolen property, stolen data or\nstolen credentials; unlicensed gambling; or anything else you are not licensed to provide where you provide it.\n\nWhere your business is lawful but regulated — health, finance, insurance, legal services, alcohol, tobacco,\nage-restricted goods — **holding the right licences, giving the right disclosures and running the right\nverification and handover checks is yours to do.** We do not check any of it and we are not your compliance\nfunction.\n\n### Sanctions, export controls and embargoes\n\nYou must not use the Service, or allow it to be used, in breach of applicable sanctions or export-control law,\nor for or on behalf of a person or organisation subject to them. The compliance, export and sanctions section\nof our [Terms of Service](https://everdemand.co/tos) sets out what that means for your Subscription.\n\n### Interfering with the law\n\nDo not use the Service to obstruct a lawful investigation, evade a court order, conceal or destroy material you\nare required to keep, or defeat a removal, blocking or suppression obligation that applies to you.\n\n## Content that infringes someone else's rights\n\nYou need the right to put something into the Service before you put it there. That applies to files, images,\ntext, code, datasets, brand names, and anything an integration brings in on your behalf.\n\n### What is prohibited\n\n- Uploading, storing, publishing, sharing or distributing anything that infringes another person's copyright,\n trade marks, design rights, database rights, patents or trade secrets.\n- Importing or republishing datasets, catalogues, curated lists or harvested collections you have no right to\n use. **An openly licensed source is not an unconditional one** — attribution, share-alike and non-commercial\n conditions travel with the content, and honouring them is your job, not ours.\n- Using someone else's trade mark in a workspace name, project name, URL slug, custom domain or sending domain\n in a way that suggests a connection you do not have. That includes typosquats and look-alike domains.\n- Putting another party's confidential information into the Service where you have no right to disclose it:\n material under a non-disclosure agreement, another company's customer data, privileged or otherwise protected\n work.\n- Removing, obscuring or altering a copyright notice, licence text, attribution or provenance metadata.\n\n### Our own software and brand\n\nWhere a product is published as open source, its licence governs what you may do with the code — but do not\nstrip its licence headers or attribution, do not present a fork or a self-hosted deployment as a service we\noperate, do not redistribute a paid edition, and do not circumvent the limits of the tier you bought. What you\nmay do with our names, logos and other brand features is dealt with in the intellectual property section of our\n[Terms of Service](https://everdemand.co/tos).\n\n### Reporting infringement\n\nIf something on the Service infringes your rights, tell us at abuse@ever.co. We handle these as\nnotice-and-action complaints under the rules that apply to us as a hosting service in the European Union, and\na notice needs to give us:\n\n- what the right is and why you hold it, or your authority to act for the person who does;\n- exactly where the material is — a URL, share link, workspace or file path, precise enough that we can find it\n without guessing;\n- what the material infringes, and how;\n- a statement that you believe in good faith the use is not authorised by the rights holder, an agent or the\n law; and\n- how to reach you.\n\n### What happens next\n\nWe assess notices on their content, not on their volume or their tone.\n\nWhere a notice is well founded we remove or disable access to the material, and we tell the affected customer\nwhat we did and why, unless the law prevents us. **Where the customer tells us the notice is wrong, we pass\nthat back to the complainant and we may restore the material.** We are not the venue for deciding who owns\nwhat — a genuine ownership dispute belongs in a court, not in our inbox.\n\n**We terminate accounts that infringe repeatedly.** What counts as repeat is a judgement about the pattern and\nthe customer's response to it, not a fixed count we publish for people to stay just underneath.\n\n## Harassment, hate and abusive content\n\nMost of what goes into the Service is private business content in your own Workspace, and we are not the\nmanners police for it. These rules still apply to it, and **they apply with real force to anything you publish\nthrough the Service, send to another person through it, or point a share link at.**\n\n### Prohibited\n\n- **Harassment and bullying** — a course of conduct directed at a person that is intended to, or is reasonably\n likely to, intimidate, humiliate or distress them, including conduct continued after they have asked for it\n to stop.\n- **Threats** of violence, and content that celebrates or wishes serious harm on identifiable people.\n- **Stalking** — using the Service to follow, locate, contact or observe a person against their wishes. Where\n that involves our capture, recording or tracking features, the privacy and surveillance section below governs\n it and we treat it as the most serious category of breach we handle.\n- **Hate speech** — attacking or demeaning people because of race, ethnicity, national origin, religion,\n disability, age, sex, sexual orientation, gender identity or another protected characteristic.\n- **Doxxing** — publishing or sharing a person's private information without their agreement, or assembling it\n so that someone else can act on it. Home addresses, personal contact details, identity documents, location,\n medical and financial details all count.\n- **Sexual content involving a person who has not agreed to it being shared**, and any sexual content involving\n a minor. That second category is dealt with absolutely in the illegal activity section above.\n- **Adult content on public-facing surfaces we host for you**, unless we have agreed it in writing and it is\n lawful and age-gated where it is served.\n- **Abuse of our own people.** Threatening, abusive or discriminatory conduct towards our staff in support\n tickets, chat, calls, issue trackers or community channels. We will end the conversation, and if it continues\n we will end the relationship.\n\n### Content you publish for other people to see\n\nWhere the Service lets you publish something publicly — a page, a directory, a profile, a shared recording, a\npublic team — **you are the publisher of it, not us.** Keep other people's personal data out of it unless they\nknow and you have a basis for holding it there, provide a way for people to complain about what you have\npublished, and act on a reasoned objection rather than ignoring it. **You must not republish content that a\nperson has already had removed.**\n\nWhere you run something on our infrastructure that accepts contributions from the public, moderating it is your\nobligation. Our tools do not discharge it and our policy is not your policy.\n\n### Community and contribution channels\n\nOur public repositories, issue trackers, documentation sites and chat channels carry these rules plus any code\nof conduct published with them. Spam, off-topic promotion, brigading and abuse there are breaches of this\npolicy and we deal with them the same way.\n\n## Privacy and unlawful surveillance\n\n**This is the strictest section in this policy, and it is strict because of what our software can do.**\n\nSome of our products measure how work happens. Depending on the product and the settings your administrators\nchoose, they can capture screenshots, webcam stills, audio, screen recordings, keyboard and mouse activity\nrates, the applications and websites in use, location, and how long each of those lasted. Selling software that\ncan do that places a duty on us that a project-management tool does not carry, and this section is how we\ndischarge it.\n\n**Lawful, disclosed monitoring of your own personnel is a legitimate use of the Service. Covert monitoring is\nnot, and never will be.** Everything below follows from that one line.\n\n### Monitoring that is never permitted\n\nYou must not use the Service, or configure it, to do any of the following.\n\n- **Covert or secret monitoring of any person.** If the person being measured does not know it is happening, it\n is prohibited — whatever your reason, wherever you are, and whether or not you believe you have a lawful\n basis for the underlying processing.\n- **Monitoring anyone who has not been informed in the way their local law requires, before capture starts.**\n Telling someone afterwards is not notice. A line in a handbook they have never seen is not notice either,\n where their law demands more.\n- **Monitoring outside working hours, during breaks, on personal time, or on a person's own device**, without a\n lawful basis and their knowledge. Capture follows the work. It does not follow the person.\n- **Enabling screen capture, webcam stills, audio capture or screen recording where local law prohibits it**,\n restricts it to purposes you are not pursuing, or conditions it on a process you have not completed.\n- **Deploying a configuration the monitored person cannot see, pause, stop or exit.** Combining continuous or\n randomised capture with settings that stop a person closing the agent, logging out, or seeing that capture is\n running produces covert monitoring by construction, and we treat it as covert monitoring however it was\n arrived at.\n- **Monitoring anyone other than your own personnel in the course of their work.** The Service may be used to\n measure your employees, contractors and workers while they work for you. It may not be pointed at a partner,\n a family member, a housemate, a child, a customer, a competitor, a journalist, or any other person who is not\n yours to monitor. **Using our software as stalkerware is an immediate-termination breach and we will treat it\n as one.**\n- **Installing the desktop agent, browser extension or tracker on a device you do not own or control**, without\n the informed agreement of the person who does.\n- **Using captured data for a purpose the monitored person was not told about.** If they were told capture was\n for billing accuracy, it is not then available for discipline, performance ranking or redundancy selection.\n Purpose creep is a breach of this policy, not only of your own notice.\n- **Capturing where capture predictably exposes other people's confidential or special-category data** —\n clinical settings, legally privileged work, HR investigations, child-facing services, or a home where other\n people are visible or audible — unless capture is switched off for the people concerned.\n- **Defeating the controls that exist to protect people.** Do not work around a per-person or per-team disable,\n a blur setting, a retention limit, an excluded-application list or a capture-frequency limit in order to\n observe someone whose monitoring is meant to be off or reduced.\n\n### Other people's privacy, whatever product you use\n\nThese apply across the Service, not only to the products that measure work.\n\n- **Recording a call, meeting, screen or conversation without the notice or consent the law requires** from\n everyone involved. Several jurisdictions require every party to agree, and where participants are in\n different places the strictest rule among them is the one that governs.\n- Capturing another person's screen, device, session or account without their authorisation.\n- Using a browser extension's access to reach pages the person never intended to expose — personal banking,\n health portals, private messaging, personal webmail.\n- Harvesting personal data at scale, from us or from anywhere else, including collecting it in breach of\n another platform's terms, its rate limits or its technical protections.\n- Building biometric profiles, or inferring sensitive characteristics about people — health, beliefs, sexual\n orientation, union membership, immigration status — from anything the Service captures or holds.\n- Entering another person's personal data into our forms, or subscribing an address you do not control.\n- Putting special-category data into the Service without a lawful basis for it, or where your product annex\n states that the Service is not built to hold it.\n\n### What you promise us when you switch monitoring on\n\nBy enabling any capture or activity-measurement feature for a person, **you represent to us** that:\n\n- you are the controller of that processing, you have identified a valid lawful basis for it, and you\n understand that **consent is generally not a valid basis in an employment relationship**, because of the\n imbalance between the person asking and the person consenting;\n- you have given that person the information their law requires — what is captured, how often, why, who sees\n it, how long it is kept, and how to object — **before capture began**;\n- you have carried out a data protection impact assessment where one is required, and consulted your\n supervisory authority where the residual risk requires that;\n- you have completed any works council, trade union or employee-representative process required where that\n person works. **These are not formalities.** Co-determination in Germany, works council consent in Austria,\n works council approval in the Netherlands, prior union agreement or labour-inspectorate authorisation in\n Italy, and co-operation negotiations in Finland can each make a deployment unlawful, and the data it produced\n unusable, if they were skipped;\n- you will not enable capture for anyone in a jurisdiction that prohibits it. **Some do.** Supervision of\n performance by remote technical means is close to prohibited outright in Portugal, and keystroke and\n continuous-capture tooling has been held unlawful elsewhere on proportionality grounds; and\n- you are not using the Service to monitor covertly, or to monitor anyone outside a lawful monitoring programme\n of your own.\n\n**We make no claim that any configuration of the Service is lawful in any country.** This law differs sharply\nfrom one jurisdiction to the next and is still moving. We build the controls, publish what each one does, and\ngive you the material to run your own assessment. **The decision to switch monitoring on is yours, and so is\nthe liability that comes with it.** Your indemnity in our [Terms of Service](https://everdemand.co/tos) covers claims\nthat arise from breaking the representations above.\n\n### We act on credible reports of covert monitoring\n\n**Anyone can report suspected covert or unlawful monitoring to abuse@ever.co — you do not have to be our\ncustomer.** A monitored worker, a works council, an employee representative, a family member or a regulator can\nall use that address. We would far rather receive a report that turns out to be a misunderstanding than not\nreceive one at all.\n\nWhen we receive a credible report:\n\n- **we treat the reporter's identity as confidential.** We do not pass it to the customer without their\n agreement unless the law compels us. We know that the person best placed to report covert monitoring is\n usually the person with the most to lose by reporting it;\n- **we may require the customer to evidence** the notice it gave, the lawful basis it relies on, and the\n consultations it completed. \"Trust us\" is not evidence, and a customer that cannot produce any is treated as\n a customer that has none;\n- we may switch off specific capture features for that Workspace while we look, suspend the account, or\n terminate it, depending on what we find and how serious it is; and\n- **we will not take a customer's assurance over a credible report from the person being monitored.**\n\n**Retaliating against someone because they reported to us — dismissing them, disciplining them, withdrawing\ntheir work — is itself a breach of this policy**, and we will act on it against the customer that does it.\n\n## Security violations\n\nThe Service is shared infrastructure. The rules below protect other customers at least as much as they protect\nus.\n\n### Do not\n\n- **Access anything you were not given access to** — another customer's Workspace or data, another user's\n account, our internal systems, or any part of the Service behind a boundary you were not invited past.\n- **Probe, scan or test** the Service, our networks or our infrastructure for vulnerabilities without our prior\n written permission, except within the coordinated disclosure route below.\n- **Attack accounts** — credential stuffing, password spraying, brute forcing, or enumerating accounts and\n email addresses through sign-in, recovery or invitation endpoints.\n- **Enumerate or guess identifiers.** Share links, object ids, invitation tokens and export URLs are meant to\n be given to you, not discovered by you.\n- **Circumvent controls** — authentication, authorisation, session handling, tenant isolation, rate limits,\n quotas, access gates, licence-tier limits, or any technical protection measure.\n- **Interfere with the Service** — denial-of-service traffic, load designed or reasonably likely to degrade the\n Service for others, or any attempt to cross the isolation between one Workspace and another.\n- **Reverse engineer, decompile or disassemble** the Service, except to the extent an applicable open-source\n licence or a law that cannot be excluded permits it.\n- **Turn the Service into infrastructure for something else** — an open relay or proxy, an anonymisation or VPN\n service, a command-and-control endpoint, a port scanner, a password-cracking rig, or a staging point for an\n attack on a third party.\n\n### Credentials and access\n\n- **Accounts are for one person.** Do not share a login, and do not hand an account from one person to the next\n as staff change — create and remove accounts instead.\n- Do not share API keys, tokens or seats outside the Workspace they were issued for, and do not leave them\n anywhere others can read them.\n- **Do not give us credentials you are not entitled to use** — a colleague's, a former employer's, a shared\n mailbox you do not control, or an access token, key or configuration file belonging to someone else.\n- Do not use the Service to store, distribute or trade credentials obtained from anyone else.\n- Keep your own credentials secure, turn on multi-factor authentication where we offer it, and **tell us at\n abuse@ever.co as soon as you suspect an account has been compromised.** Delay there costs other people,\n not only you.\n\n### Security research\n\nWe want to hear from researchers, and we will not pursue anyone who acts in good faith.\n\nYour testing is in scope if you work only against your own account and your own data; do not access, modify or\nretain another customer's data; stop at the point that demonstrates the issue rather than pushing further; avoid\ndegrading the Service or causing a privacy impact; do not run automated scanning at volume; and report to us\npromptly and privately at abuse@ever.co before disclosing anywhere else.\n\n**Testing against another customer's Workspace or data is never in scope**, whatever your intent. How we handle\nreports, and what we commit to in return, is set out on our Security page.\n\n## Resource abuse\n\nYou share compute, storage, bandwidth and outbound sending reputation with every other customer. Use your\nshare.\n\n### Do not\n\n- Mine cryptocurrency, run distributed computing, or use the Service for processing that has nothing to do with\n what the Service is for.\n- Use our storage or bandwidth as a general-purpose content delivery network, a file-distribution service, a\n backup target for unrelated data, or a home for media we had no part in producing — including hot-linking\n files held with us into other sites.\n- Run automated bulk extraction against the Service, our websites, our documentation or our APIs. **Issued API\n credentials used within their documented scope and rate limits are exactly what they exist for**; scraping the\n interface, or driving an API past its published limits, is not.\n- Run unbounded or pathological workloads — agent or job loops with no termination condition, retry storms,\n runaway automation, or deliberately expensive requests repeated to see what happens.\n- Hold sessions, connections or reserved capacity open purely to keep hold of them.\n- Evade a limit rather than raise it: extra accounts to farm a free allowance, disposable addresses, referral or\n credit gaming, seat sharing, or a second Workspace created because the first one hit its ceiling.\n\n### Free plans and trials\n\nFree and trial access exists so that you can evaluate the Service and so that small teams can use it. It is not\nanonymous infrastructure. **Limits on free plans are tighter, are enforced at our discretion, and can change\nwithout notice.** We may reclaim idle free resources, and we may decline to keep providing a free plan to an\naccount whose consumption is out of proportion to what free access is for.\n\n### How we handle it\n\nSustained load that is normal for your plan is fine. Bursting is fine. What we act on is load that degrades the\nService for other people, load that is not really use of the product at all, and load that keeps growing after\nwe have asked about it.\n\n**Our first step is normally to contact you, not to cut you off.** We would rather move you onto a plan or a\nlimit that fits than lose you over a number. We throttle before we suspend, and we suspend without warning only\nwhere the platform or other customers are at risk.\n\nIf your usage above a published limit is a genuine business need rather than abuse, write to legal@ever.co\nand we will look at raising it. The numbers themselves are in the fair use section below, in your plan or Order,\nand in the Documentation.\n\n## Spam and unsolicited messaging\n\nThe Service sends mail, invitations, notifications and, in some products, text messages — sometimes from our\nown sending domains and on our own reputation. That makes messaging abuse everybody's problem here: one\ncustomer's cold-outreach campaign is what gets every other customer's invoices and password resets filtered.\n\n### Do not\n\n- **Send unsolicited bulk email, SMS or messages of any kind through the Service**, or use it to prepare, host\n or support a campaign that someone else sends.\n- **Mail a list you cannot stand behind.** You must be able to show us, on request, how each recipient came to\n be on it. Purchased, rented, swapped, harvested and scraped lists are prohibited, and so are address guessing,\n permutation and dictionary attacks.\n- **Spoof or falsify** a sender identity, a header, a reply path or a domain, or send from a domain you do not\n control. Where you send through the Service, configure SPF, DKIM and DMARC for your own domain, respect any\n warm-up schedule and sending rate we set, and keep a working reply path that a human reads.\n- **Strip, hide, disable or visually suppress** an unsubscribe link, a `List-Unsubscribe` header, a required\n postal address, or any compliance footer the Service adds. **Making the opt-out hard to find is the same\n breach as not having one.**\n- **Ignore an opt-out.** Suppression must be honoured promptly and permanently. No re-importing a suppressed\n person, no refreshing them from another source, no moving them into a second Workspace or account to escape\n the suppression list, and no treating an unsubscribe click as an engagement signal.\n- **Repurpose our transactional messages as a marketing channel.** Invitations, verification mails, share\n notifications, estimates, invoices and system notices exist to carry their own content — not to carry an offer\n to someone who never asked for one.\n- **Use invitations to reach people who will not be working in your Workspace.** The invitation flow is a\n foreseeable spam vector and we watch it.\n- **Abuse our own public endpoints** — automated submissions to our contact, newsletter or support forms,\n repeated submissions used to bomb a third party's mailbox through them, or link injection into free-text\n fields.\n\n### The law applies to you, and we do not check it for you\n\nElectronic marketing to individuals is regulated separately from data protection. Depending on where your\nrecipients are you may need prior opt-in, and the existing-customer exception is much narrower than most senders\nassume. **Working out which rule covers which recipient is yours to do.** Nothing the Service does — including\nany compliance footer it adds for you — makes a message lawful that would not otherwise be.\n\n### Deliverability is an enforcement trigger\n\nWe monitor bounce rates, spam complaints, blocklist entries and mailbox-provider feedback for traffic sent\nthrough the Service. **Where a sender's numbers put shared reputation at risk we act immediately and without\nnotice** — pausing a campaign, throttling or suspending sending, revoking a sending domain, or suspending the\naccount. We do the same on a credible complaint from a recipient, a mailbox provider or a blocklist operator.\n\nIf you received a message from someone using the Service and you did not ask for it, report it to\nabuse@ever.co with the full headers if you have them.\n\n## Malware and hostile files\n\n### Do not upload, store, link to or distribute\n\n- **Malware of any kind** — viruses, worms, trojans, ransomware, rootkits, keyloggers, spyware and stalkerware.\n- **Exploit code, exploit kits, cracking and credential-stuffing tools**, and payloads intended to establish or\n keep unauthorised access to anything.\n- **Files built to attack whatever opens them** — decompression bombs, entity-expansion payloads, deliberately\n malformed documents, and uploads crafted to break a parser, a preview renderer or a downstream viewer.\n- **Values crafted to execute somewhere else.** Text you put into a field that is later exported — a name, a\n translation string, a note, a description — must not be built to run as a formula, a script or a command in\n whatever opens the export.\n- **Phishing and credential-harvesting pages**, fake sign-in screens, and deceptive destinations of any kind.\n **A link on our domain lends our credibility to whatever it points at**, which is exactly why share links\n attract this and exactly why we move fast on it.\n\n### We scan, and we are telling you so\n\nWe may scan, sandbox, quarantine, refuse, disable or delete files, links and messages that we reasonably believe\nare hostile, and we may do it without prior notice.\n\n**We are stating this openly because scanning your uploads is itself a processing activity, and undisclosed\nprocessing is not something we are willing to do.** What it means for personal data is set out in our\n[Privacy Policy](https://everdemand.co/privacy).\n\nAutomated detection is imperfect in both directions. If we have quarantined something wrongly, tell us at\nabuse@ever.co and we will look again.\n\n### Security work with a legitimate need\n\nIf your work genuinely involves handling malware samples — you run a security team, or you research this for a\nliving — do not do it in the Service without asking us first. Write to legal@ever.co, tell us what you need\nand how it will be contained, and we will either agree it in writing or tell you no. **Doing it without that\nagreement is a breach**, however good the reason.\n\n### Your own hygiene\n\nKeep the devices and networks you use to reach the Service reasonably secure and up to date, and tell us at\nabuse@ever.co if you believe a device with access to your Workspace has been compromised.\n\n## AI features, assistants and agents\n\nThese rules apply wherever the Service uses a model on your behalf — an assistant, a generated document, an\nautonomous agent, a connected tool endpoint, or a feature you drive with your own provider key. They sit on top\nof everything else in this policy, and alongside the AI terms in our [Terms of Service](https://everdemand.co/tos).\n\n**Anything an agent does under your credentials is your act.** Automating a decision does not move\nresponsibility for it.\n\n### Do not generate unlawful, deceptive or infringing content\n\n- Content that is unlawful, defamatory, harassing or discriminatory. The rest of this policy applies to\n generated output exactly as it applies to text you typed yourself.\n- Fraud material — phishing text, fake invoices, scam messages, or anything designed to deceive a person into\n parting with money, credentials or access.\n- Impersonation of a real person or organisation, including synthetic voice, image or video of a real person\n without their agreement, and content presented as authentic when it is not.\n- Fabricated facts about a named person or business: reviews, testimonials, endorsements, qualifications,\n awards, or claims about their conduct, finances or history.\n- Content that infringes someone else's rights, and output presented as original where it is not.\n- Bulk low-value content produced to manipulate search rankings — doorway pages, mirror sites, near-duplicate\n sites generated at scale, cloaking and link schemes.\n- Removing or falsifying provenance metadata or watermarks that mark content as machine-generated, and passing\n model output off as human-created where doing so misleads someone whose decision depends on it.\n\n### Do not make consequential decisions about people without human review\n\n**Model output is an input to a decision. It is never the decision.**\n\nWhere a decision materially affects a person — hiring, promotion, discipline, dismissal, pay, credit, insurance,\ntenancy, education, benefits, access to essential services, or legal and immigration status — you must not treat\na score, ranking, band, signal, summary or recommendation produced through the Service as the sole or\ndeterminative basis for it. **A human being with authority and real discretion must consider the case and be\nable to reach a different answer.**\n\nThat applies with particular force to anything derived from monitoring. An activity percentage, a productivity\nscore, a screenshot summary or an attention metric is not a finding about a person's performance, and treating\nit as one is both a breach of this policy and, in many places, a breach of the law.\n\nYou must not use these features to discriminate on a protected characteristic, directly or through a proxy for\none. **Where we find a customer doing this, we may switch the feature off for that Workspace.**\n\n### Do not present output as professional advice\n\nDo not use the Service to give medical diagnosis or treatment decisions, clinical decision support, legal\nadvice, or financial and investment advice in a way that a recipient would reasonably take as coming from a\nqualified professional. Do not use it in the design or development of weapons.\n\n### Do not attack the models or the pipeline\n\n- **No attempts to extract training data, model weights, system prompts, tool definitions, configuration, or\n another customer's data or prompts.**\n- **No prompt injection.** Do not place instructions in content, files, profile fields, repositories, tickets,\n commits or messages that are designed to make an assistant ignore its policies, act outside its permissions,\n operate on another party's data, call a tool it was not authorised to call, or disclose secrets.\n- **No circumventing safety measures** — content filters, approval gates, human-in-the-loop confirmations, usage\n limits or policy checks. That includes automating a confirmation so an action is taken without a real human\n decision behind it. **The approval gates are load-bearing. Defeating one is a severe breach and we may block\n access immediately.**\n- No using our AI endpoints as a general-purpose relay: proxying traffic, reaching internal or arbitrary hosts,\n or pushing work unrelated to your use of the Service through us to a provider.\n- No supplying provider credentials you are not entitled to use, and no sending a provider content you have no\n right to send it. Where you bring your own key, that provider's terms bind you as well as ours do.\n\n### Do not compete with what you are using\n\nDo not use the Service, its output or its features to develop, train, fine-tune, distil or benchmark a competing\nmodel or product, and do not resell, sublicense or transfer model access obtained through us.\n\n## Fair use and published limits\n\nEvery plan has limits. **We publish them, rather than leaving \"fair use\" to mean whatever we decide later.**\n\n### Where the numbers are\n\nThe limits that apply to you are in your plan description or Order, in the Documentation for the Service, and in\nthe product-specific section of this policy. Where the same limit appears in more than one of those, the one in\nyour Order wins.\n\nDepending on the product, they cover:\n\n- API request rate, and the burst allowance above it;\n- concurrent connections — streaming, websocket, agent and tool endpoints;\n- total stored data per Workspace, and the size of any single upload;\n- capture and media volume, where the product records screenshots, recordings or other media;\n- outbound message volume and sending rate;\n- agent, job or build run time; and\n- seats, Workspaces and connected integrations.\n\n### What \"unlimited\" means when we say it\n\nWhere a plan is described as unlimited, or as fair use, it means **unlimited normal use of the product as it is\nsold** — not permission to use us as generic storage, generic compute or a content delivery network. When your\nusage stops resembling use of the product, it stops being covered by the word.\n\n### How limits are applied\n\nRate limits are enforced technically: over the limit you get an error and a retry signal, not a surprise\ninvoice. **We do not bill overage that was not in your Order.**\n\nWhere a storage or volume ceiling is exceeded, we contact you first and give you a reasonable period to reduce\nusage or move to a plan that fits before we restrict anything. Free and trial plans are the exception, and the\nresource abuse section above says how.\n\n### When limits change\n\nWe may change published limits. Where a change materially reduces what you can do on a plan you are paying for,\nwe give you notice in the way the changes section of our [Terms of Service](https://everdemand.co/tos) requires, and\nyou may cancel before it takes effect. Increases, and changes to free-plan limits, take effect when we publish\nthem.\n\nIf you have a genuine need above a published limit, ask us at legal@ever.co. **We would much rather agree a\nhigher limit with you in advance than discover the traffic.**\n\n## Annex: Ever Demand — couriers, addresses and deliveries\n\nEver Demand reads a working person's position every few seconds and shows it live to their dispatcher,\nto the shop and to a member of the public waiting for a delivery. It also holds the home addresses of people\nwho never agreed to anything. Those two facts are what this annex is about, and they are why it is longer\nthan the product's size would suggest.\n\n### What this binds, and what it offers everyone else\n\n**These rules bind [everdemand.co](https://everdemand.co), the documentation site, and any instance of the\nplatform we host for you.** If we host your instance, breaking a rule here is a breach of your agreement with\nus and the enforcement section below applies to you in full.\n\n**If you run the software yourself, this annex imposes nothing on you.** The code licence governs the code,\nand we do not add conditions to it through a policy page. What this annex is, in that situation, is the\nstandard we would hold ourselves to and the one we would expect of an operator we hosted — published because\nthe software enforces almost none of it, and because a courier reading it deserves to know what good practice\nlooks like. Where we do host you, the Data Processing Addendum puts the same duties in binding terms.\n\n### The Online switch is the whole design, and you must not defeat it\n\nThe courier application reads position only while the courier's own status is set to Online. **That gate is\nthe single control standing between a dispatch tool and a tracking device, and it lives in client code you\nbuild and ship.** So, on an instance we host:\n\n- **You must not ship a modified courier application that reports position while the courier's status is\n Offline**, that resets the status without the courier doing it, that hides the control, or that makes going\n offline harder than going online.\n- **You must not infer or reconstruct position by other means when a courier is off duty** — polling a device,\n reading location from another application you also control, or treating a delivery-completion event as\n permission to keep sampling.\n- **You must not track a courier outside their working time.** A shift that has ended is not a shorter shift.\n Travel to the depot, a break, an unpaid gap between assignments and the journey home are not working time\n because your operation would find it convenient if they were.\n- **You must not track a courier who is not on duty for you** — someone else's courier, a courier on another\n operator's shift, or a person carrying a device you issued for a job they are not currently doing.\n\nThe platform stores a courier's current position and overwrites it with the next reading, so no route history\naccumulates by itself. **If you build one — logging each position, or deriving a track from them — that is a\nnew processing operation you have chosen to start**, and everything below about purpose applies to it with\nfull force.\n\n### The live map may only be as wide as the delivery\n\nA courier's position is shown to the ordering customer while a delivery is running. That is disclosure of a\nworker's real-time location to a member of the public, and it is only defensible while it is tied to that\ndelivery.\n\n- **Customer-facing visibility must be confined to the active delivery.** Not before it is assigned, not after\n it is completed, and not to a customer whose order the courier is not carrying.\n- **Internal visibility must be confined to people who need it to dispatch.** A live map is not general office\n entertainment, and access to it is an access decision you have to make deliberately.\n- **You must not expose a courier's position through an interface, a share link, an embed or an export to\n anyone outside the delivery it belongs to.**\n- **You must not use the tracking interface to harvest positions** — yours or anyone else's. Pulling courier\n locations in bulk is a surveillance act, whatever endpoint it goes through, and we treat it as one rather\n than as a rate-limit question.\n\n### Location and work counters may only be used for what the courier was told\n\nAlongside position, the platform accumulates lifetime deliveries, deliveries today, distance travelled today,\norders skipped, and the record of going on and off duty. There is also a switch that turns a courier's account\noff.\n\n- **You must not use any of it for a purpose you did not tell the courier about before you started.** If a\n courier was told tracking was for dispatch and delivery estimates, it is not then available for performance\n ranking, pay decisions, discipline, redundancy selection or a reference.\n- **You must not reconstruct a courier's movements to check something you were not open about** — how long a\n break lasted, whether they went home mid-shift, where they live, whether they attended a union meeting,\n whether they work for someone else.\n- **You must not infer anything about a courier's health, beliefs, union membership or private life** from\n where they went or how far they travelled.\n- **You must not combine these counters with data from another system to build a score you never disclosed.**\n A metric that was described as operational and is used as a judgement has become something the courier was\n entitled to be told about.\n- **Switching a courier's account off is an employment act, not a configuration change.** Do it for a reason\n you would be willing to put in writing to the person it affects.\n\n### Other people's addresses and telephone numbers\n\nThe platform will accept any address and telephone number typed into it, from anyone, with no check that the\nperson at the other end has any idea.\n\n- **You must not enter a third party's address, apartment number or telephone number without a basis for\n holding it.** Delivering to someone at their home because they are expecting a delivery is a basis.\n Collecting an address because it might be useful later is not.\n- **The free-text delivery notes field is not a place to record anything about a person beyond finding the\n door.** People write what helps a courier; you must not turn it into a comments field about a household.\n- **You must not use the invite-request flow to collect residential addresses for any purpose other than\n deciding whether to serve that address**, and **you must not keep refused requests as a marketing list.** A\n person who asked whether you deliver to their street has not asked to hear from you.\n- **You must not use addresses held for delivery for anything else** — leaflet drops, list rental, area\n profiling, or sale to anyone.\n- **Everyone in the paragraphs above has a right to be told you hold their data**, including the courier\n enrolled by an administrator and the recipient who never placed the order. Giving that notice is yours, and\n we cannot give it for you because in most cases we have no way to reach them.\n\n### What may be sold and delivered through an instance we host\n\nThe platform has no field that marks a product as restricted, no age check, no allergen record and no\ntemperature control. **Every one of those is something you build or something you go without, and going\nwithout it is not an option the law offers you.**\n\n- **You must not offer or arrange delivery of goods you are not licensed to supply where you supply them** —\n controlled substances, prescription medicines, weapons and ammunition, untaxed or contraband alcohol and\n tobacco, counterfeit goods, live animals, or hazardous materials.\n- **You must not sell age-restricted goods through a deployment we host without an age-verification and\n handover process of your own.** Nothing in the product distinguishes a restricted item from a loaf of bread.\n- **Where you handle food, you must hold the licences, run the temperature controls and give the allergen\n information your local law requires.** The product is marketed for food delivery and carries no allergen\n field; that gap is yours to close, and a delivery that harms someone is not a software fault.\n- **You must not use the platform's push notifications, or a merchant's order mailbox and order telephone\n number, for unsolicited marketing** to shoppers or to couriers.\n\n### Configuration that turns into a breach\n\nSome of this software's defaults are development conveniences, and leaving them on in production is not a\nmisconfiguration so much as an open door. On an instance we host, **you must not run with**:\n\n- the fake data generator or the bulk customer generator enabled;\n- a fake invite code configured, which lets anyone past the invite gate;\n- the administrator password-reset shortcut enabled; or\n- **the signing and session secrets left at the values the repository ships with.** Those values are published\n in public source code, which means they are not secrets from anybody.\n\nYou must also not store a payment secret key belonging to anyone other than the merchant whose gateway account\nit is, and **you must not use a merchant's stored keys for anything beyond routing that merchant's own\ntransactions.** The security annex explains why those keys are worth protecting more carefully than their\ncurrent storage suggests.\n\n### Reporting, and what happens when we cannot reach the deployment\n\nIf you believe a courier is being tracked off duty, that location data is being used for something the courier\nwas never told about, or that someone's address is being held or used without a basis, tell us at\nabuse@ever.co. **You do not need to be our customer, and if you are the courier this was done to, your\nidentity stays with us.** Tell us what you can: the business, what you saw, and how we can reach you.\n\nThen the honest part. **In almost every deployment of this product we are not in the picture at all**, and we\ncannot switch off a feature, read a database or suspend an account on a system somebody else runs. Where that\nis the situation:\n\n- we will tell you plainly that the deployment is not ours, rather than leaving you waiting;\n- we will tell you who the operator appears to be, where we can establish it, so your report reaches somebody\n who can act; and\n- we will tell you that you can go to the data protection authority in your own country, and to your national\n labour authority, without our permission and without coming through us first.\n\nWhere the instance **is** one we host, none of that applies and the enforcement section below does: we can\nrequire you to evidence the notice you gave your couriers, switch tracking off for that instance, suspend it,\nor end it.\n\n## Reporting abuse\n\n**abuse@ever.co** — one address, read by people, for anything on this page.\n\n**You do not have to be our customer to use it.** We publish it for the person with no other route: a worker who\nbelieves they are being monitored covertly, someone who received a message they never asked for, a rights\nholder, a researcher, a works council, a parent, a regulator. Reports from people who are not customers get the\nsame handling as reports from people who are.\n\n### What to tell us\n\nThe more of this you can give us, the faster we can act. Send what you have — an incomplete report is still\nworth sending.\n\n- **What happened**, in your own words.\n- **Where** — the URL, share link, workspace, sending address, message headers, or the name of the application\n or agent involved. Precise enough that we can find it without guessing.\n- **When**, with dates, times and the time zone you are quoting.\n- **Who is affected**, if you can say, including whether that is you.\n- **Evidence** — headers, message ids, screenshots, links. Attach it where you can, rather than describing it.\n- **What you are asking for** — content removed, messages stopped, monitoring investigated, information.\n- **How to reach you**, if you want an answer. You may report anonymously, but we then cannot come back to you\n for the detail that often decides a case.\n\nSome reports have a better route. A request about your own personal data goes to privacy@ever.co. A security\nvulnerability goes through the coordinated disclosure route in the security violations section above. An\nintellectual property complaint needs the specific details listed in the infringing content section.\n\n**If you are reporting suspected covert monitoring, say so in the first line.** Those go to the front of the\nqueue.\n\n### What we do with it\n\n- **We acknowledge within two business days.**\n- **We give you a substantive answer, or a real status update, within ten business days.** Investigations that\n involve a customer's own workforce sometimes take longer than that. Where they do we will tell you where it\n has got to rather than going quiet on you.\n- **Where a person is at immediate risk, we act first and correspond afterwards.**\n- **We keep the reporter's identity confidential.** We do not pass it to the customer without your agreement\n unless the law compels us, and where that happens we will tell you if we are permitted to.\n- We tell you the outcome in general terms. **We will not hand you another party's account details, internal\n correspondence or personal data**, however much you would like us to. The same protection applies to you.\n\n### What we are not\n\nWe are not a court and we are not an arbitrator. Where a report is really a commercial or contractual dispute\nbetween you and someone else, we will say so and decline to take a side. We enforce our own rules against our\nown customers — that is the whole of our jurisdiction.\n\n**Deliberately false reports, and automated or mass reporting used as a weapon, are themselves a breach of this\npolicy.** Being wrong in good faith is not. We would far rather read a hundred honest reports that come to\nnothing than miss the one that mattered.\n\n## Enforcement\n\n### How we decide\n\nWe aim to be proportionate: the smallest action that actually stops the problem, applied to the narrowest part\nof the account that will do it. We weigh how serious the conduct is, whether anyone is being harmed right now,\nwhether it looks deliberate, whether it is still going on, and what you did when we raised it.\n\n**We also judge you by what you do about abuse by the people using the Service under your Subscription.** A\ncustomer whose End Users cause a problem and who moves quickly to stop it is in a very different position from\none who cannot or will not.\n\n### Investigation\n\nWe may look into a report, or into something we detect ourselves. That can include reviewing account and\nconfiguration metadata, logs, message headers, sending records, public-facing content, and content you have made\navailable to us — and asking you for evidence: the notice you gave your monitored personnel, your opt-in\nrecords, your right to use content, your authority for an integration.\n\n**We do not routinely read the contents of your Workspace.** Where an investigation genuinely requires looking\nat Customer Data, we look at the minimum needed, restrict it to staff who need it, and record that we did.\n\nWe may preserve material relevant to an investigation, and we may hold an account in a restricted state while we\nwork.\n\n### What we can do\n\n- Ask you to fix it, with a deadline.\n- Remove, disable or de-publish specific content, a public page, a share link or a custom domain.\n- Restrict or switch off a specific feature for a Workspace or a user — **including capture and monitoring\n features**.\n- Reduce a rate limit, throttle traffic, pause a campaign, or revoke a sending domain.\n- Suspend a user, a Workspace, a project or the whole account.\n- Terminate your account and these Terms.\n- Decline to contract with you again.\n- Recover our costs, where the law allows it.\n\n### With or without notice\n\n**Where the problem can be fixed, we tell you first and give you a chance to fix it.** That is the normal path\nand most matters end there.\n\n**We act immediately, without prior notice, where waiting would be irresponsible** — including:\n\n- anything in the never-permitted list in the illegal activity section;\n- covert or unlawful monitoring of a person;\n- malware, phishing, or a live security incident;\n- conduct putting shared infrastructure, other customers or sending reputation at risk;\n- a court order, a regulator's direction, a law-enforcement requirement or a takedown obligation; and\n- abuse that continues after we have already raised it with you.\n\nWhere we act without notice we tell you as soon as we reasonably can — what we did, why, and what would have to\nchange for us to undo it — unless a legal obligation stops us. Suspension is also dealt with in the term,\nsuspension and termination section of our [Terms of Service](https://everdemand.co/tos), and everything there applies\nhere.\n\n### Telling other people\n\nWhere the law requires it, we notify affected people, rights holders and authorities, and we respond to\nregulators, courts and law enforcement. Where someone's safety is at risk, we may notify without being required\nto. We may also tell a mailbox provider, a blocklist operator or a source platform what we did about a complaint\nthey sent us.\n\n**Some legal demands prohibit us from telling you that they exist.** Where that is the case, we comply with the\ndemand.\n\n### Money\n\n**Where we terminate because you broke this policy, you get no refund.**\n\n- Fees for a period already served remain payable.\n- A period during which the account was suspended for abuse is not refunded. It is still part of your paid term.\n- The 30-day money-back guarantee in our Refund Policy is not available on a termination for breach of this\n policy.\n- The export window we allow after an ordinary termination may be withheld where we terminated for cause, as our\n [Terms of Service](https://everdemand.co/tos) sets out.\n\nYour indemnity in those Terms covers claims brought against us because of what you or your End Users did in\nbreach of this policy.\n\n### If we get it wrong\n\nWe will sometimes get it wrong. Automated detection produces false positives, and reports are sometimes mistaken\nor malicious.\n\n**Write to legal@ever.co and we will look again** — with someone who was not part of the original decision,\nwherever we practically can. If we were wrong we restore access, and we do not charge you for the period we took\nit away. Tell us anything that changes the picture: a decision made on partial information is exactly the kind\nwe want to revisit.\n\n### Two things this section does not do\n\n**It does not oblige us to monitor.** We have no general duty to review what you put into the Service, and\nchoosing not to act on one thing never gives up our right to act on another. Acting in good faith on a report\ndoes not make us responsible for what someone else did.\n\n**It does not take away a consumer's rights.** If you are dealing with us as a consumer rather than for business\npurposes, your mandatory statutory rights stand whatever this section says.\n\n## Changes to this policy\n\nAbuse moves faster than contracts do, so this policy changes more often than the rest of our documents.\n**Every version carries a number and an effective date at the top, and superseded versions stay published**, so\nyou can always establish which rules applied on a given day.\n\n**Where a change materially reduces what you are allowed to do**, we give you at least thirty (30) days' notice\nbefore it takes effect — by email to your administrative contact and in the Service — and you may cancel before\nit applies, on the terms in the changes section of our [Terms of Service](https://everdemand.co/tos).\n\n**Everything else takes effect when we publish it.** That covers new examples of conduct this policy already\nprohibits, clarifications, corrections, and changes we make because the law, a regulator, a court, a payment\nprovider or an infrastructure provider requires them — sometimes at no notice at all, because we are given none.\n\nThe version in force when you use the Service is the version that governs that use. Continuing to use the\nService after a change has taken effect means you accept it.\n\n## How to reach us\n\nWrite to a person, not a form. These addresses are monitored and we answer them.\n\n- **Abuse, harmful content, covert monitoring, spam, or a security problem** — abuse@ever.co. **Anyone may\n use this address, customer or not.**\n- **Questions about this policy, or about a decision we made under it** — legal@ever.co\n- **Your personal data, and any request about it** — privacy@ever.co\n\nBy post: **Ever Technologies LTD**, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — registered in Bulgaria under company number\n204599535.\n\nWe correspond in English.\n\nThis document is version 1.0.0 of the Acceptable Use Policy for\n[everdemand.co](https://everdemand.co), in force from 2026-08-02. It forms part of our\n[Terms of Service](https://everdemand.co/tos), and earlier versions, with the dates they applied, are published\nalongside them."
|
|
338
|
+
"markdown": "# Acceptable Use Policy\n\n**Ever Demand** — [everdemand.co](https://everdemand.co)\n\nVersion 1.0.2 · In force from 2026-08-02\n\nThis Acceptable Use Policy (\"**AUP**\") sets out what may and may not be done with Ever Demand and\nthe websites, applications and application programming interfaces we make available at\n[everdemand.co](https://everdemand.co) (together, the \"**Service**\").\n\nIt forms part of our [Terms of Service](https://everdemand.co/tos) and uses the words defined there. **Breaking a\nrule in this policy is a breach of those Terms**, and the enforcement section below sets out what we do about\nit.\n\nWe have kept it specific. A policy that only says \"do not misuse the Service\" tells nobody anything and\nprotects nobody — least of all the people our software can be pointed at.\n\n## Who this policy applies to\n\n- **You**, as the customer holding the Subscription.\n- **Your End Users** — everyone you invite into your Workspace, whether an employee, a contractor, a client or\n a colleague. **What they do in the Service counts as your act**, and it is your job to make sure they know\n these rules.\n- **Anyone else who reaches the Service through you** — a person you send a share link to, a person who\n receives a message sent through the Service, anyone using access you granted.\n- **Visitors** to our public websites, documentation and community channels, and anyone using our public\n forms, endpoints or APIs.\n\nYou do not need an account for this policy to apply to you. Using the Service in any way means these rules\napply to what you do with it.\n\n## What this policy does not apply to\n\n**Self-hosted deployments.** Where our software is published as open source, that code is licensed to you\nunder its own licence, and **this policy imposes nothing on you as a self-hoster**. It governs the hosted\nService we operate and nothing else. Nothing here adds a restriction to any open-source licence — the\nopen-source carve-out in our [Terms of Service](https://everdemand.co/tos) explains the split.\n\n**Lawful workplace monitoring.** Some of our products exist to measure how work happens, and this policy does\nnot prohibit using them for that. What it prohibits is doing it covertly, doing it to people who were never\ntold, and doing it to people who are not yours to monitor. That distinction is drawn deliberately, and in\ndetail, in the privacy and surveillance section below.\n\n## How it fits with everything else\n\n- The product-specific section of this policy adds rules for the particular Service you use. **Where a core\n rule and a product rule both apply, follow the stricter one.**\n- Where your Order, a written agreement with us, or the Documentation permits something this policy would\n otherwise forbid — an agreed rate limit, an authorised security test — that permission governs, for that\n thing only.\n- The examples here are examples. They show what we mean; they are not a complete list of everything that can\n be done wrong. Conduct that is plainly within the spirit of a prohibition is prohibited.\n\n**We are not obliged to monitor what you do in the Service, and we do not routinely read the contents of your\nWorkspace.** We do act on what we find and on what is reported to us, and not acting on one thing never waives\nour right to act on another.\n\n## Illegal and harmful activity\n\nDo not use the Service to do anything unlawful, to help someone else do it, or to conceal that it is being\ndone. **Something is out of bounds here if it is unlawful where you are, where we operate, or where the person\naffected by it is** — you do not get to pick the most permissive of the three.\n\n### Never, under any circumstances\n\nSome conduct has no lawful version and gets no benefit of the doubt. **We terminate immediately for it, we\npreserve what we hold, and we report it to the authorities where the law requires that or where a person is at\nrisk:**\n\n- child sexual abuse material, and sexualised content involving a minor in any form;\n- content that grooms, solicits or endangers a child;\n- non-consensual intimate imagery, and threats to publish it;\n- terrorist content, and material that incites, promotes or gives instruction for terrorism or mass violence;\n- credible threats of serious violence against a person or a group;\n- human trafficking, forced labour, and the sale or exploitation of people.\n\nThere is no enforcement ladder for this list and no cure period.\n\n### Fraud and deception\n\n- Fraud of any kind — payment fraud, invoice fraud, business email compromise, advance-fee schemes, pyramid\n and Ponzi arrangements.\n- Phishing, credential harvesting, and pages or messages built to be mistaken for someone else's.\n- Card testing, use of stolen or unauthorised payment instruments, chargeback abuse, money laundering, and\n moving the proceeds of crime.\n- Impersonating a person, a company, a public body or us; using a false identity; forging message headers or\n sender identities.\n- Fabricated reviews, testimonials, endorsements, certifications, awards or qualifications.\n- **Falsifying records the Service generates or holds** — including tampering with a timer, tracker, activity\n log or timesheet to misstate work done or time worked. Where that record is evidence between you and your\n own employer or customer, falsifying it is fraud against them and a breach of this policy against us.\n\n### Unlawful goods, services and content\n\nDo not use the Service to offer, advertise, arrange, broker or deliver: controlled substances and unlicensed\npharmaceuticals; weapons, ammunition or their components; counterfeit goods; stolen property, stolen data or\nstolen credentials; unlicensed gambling; or anything else you are not licensed to provide where you provide it.\n\nWhere your business is lawful but regulated — health, finance, insurance, legal services, alcohol, tobacco,\nage-restricted goods — **holding the right licences, giving the right disclosures and running the right\nverification and handover checks is yours to do.** We do not check any of it and we are not your compliance\nfunction.\n\n### Sanctions, export controls and embargoes\n\nYou must not use the Service, or allow it to be used, in breach of applicable sanctions or export-control law,\nor for or on behalf of a person or organisation subject to them. The compliance, export and sanctions section\nof our [Terms of Service](https://everdemand.co/tos) sets out what that means for your Subscription.\n\n### Interfering with the law\n\nDo not use the Service to obstruct a lawful investigation, evade a court order, conceal or destroy material you\nare required to keep, or defeat a removal, blocking or suppression obligation that applies to you.\n\n## Content that infringes someone else's rights\n\nYou need the right to put something into the Service before you put it there. That applies to files, images,\ntext, code, datasets, brand names, and anything an integration brings in on your behalf.\n\n### What is prohibited\n\n- Uploading, storing, publishing, sharing or distributing anything that infringes another person's copyright,\n trade marks, design rights, database rights, patents or trade secrets.\n- Importing or republishing datasets, catalogues, curated lists or harvested collections you have no right to\n use. **An openly licensed source is not an unconditional one** — attribution, share-alike and non-commercial\n conditions travel with the content, and honouring them is your job, not ours.\n- Using someone else's trade mark in a workspace name, project name, URL slug, custom domain or sending domain\n in a way that suggests a connection you do not have. That includes typosquats and look-alike domains.\n- Putting another party's confidential information into the Service where you have no right to disclose it:\n material under a non-disclosure agreement, another company's customer data, privileged or otherwise protected\n work.\n- Removing, obscuring or altering a copyright notice, licence text, attribution or provenance metadata.\n\n### Our own software and brand\n\nWhere a product is published as open source, its licence governs what you may do with the code — but do not\nstrip its licence headers or attribution, do not present a fork or a self-hosted deployment as a service we\noperate, do not redistribute a paid edition, and do not circumvent the limits of the tier you bought. What you\nmay do with our names, logos and other brand features is dealt with in the intellectual property section of our\n[Terms of Service](https://everdemand.co/tos).\n\n### Reporting infringement\n\nIf something on the Service infringes your rights, tell us at abuse@ever.co. We handle these as\nnotice-and-action complaints under the rules that apply to us as a hosting service in the European Union, and\na notice needs to give us:\n\n- what the right is and why you hold it, or your authority to act for the person who does;\n- exactly where the material is — a URL, share link, workspace or file path, precise enough that we can find it\n without guessing;\n- what the material infringes, and how;\n- a statement that you believe in good faith the use is not authorised by the rights holder, an agent or the\n law; and\n- how to reach you.\n\n### What happens next\n\nWe assess notices on their content, not on their volume or their tone.\n\nWhere a notice is well founded we remove or disable access to the material, and we tell the affected customer\nwhat we did and why, unless the law prevents us. **Where the customer tells us the notice is wrong, we pass\nthat back to the complainant and we may restore the material.** We are not the venue for deciding who owns\nwhat — a genuine ownership dispute belongs in a court, not in our inbox.\n\n**We terminate accounts that infringe repeatedly.** What counts as repeat is a judgement about the pattern and\nthe customer's response to it, not a fixed count we publish for people to stay just underneath.\n\n## Harassment, hate and abusive content\n\nMost of what goes into the Service is private business content in your own Workspace, and we are not the\nmanners police for it. These rules still apply to it, and **they apply with real force to anything you publish\nthrough the Service, send to another person through it, or point a share link at.**\n\n### Prohibited\n\n- **Harassment and bullying** — a course of conduct directed at a person that is intended to, or is reasonably\n likely to, intimidate, humiliate or distress them, including conduct continued after they have asked for it\n to stop.\n- **Threats** of violence, and content that celebrates or wishes serious harm on identifiable people.\n- **Stalking** — using the Service to follow, locate, contact or observe a person against their wishes. Where\n that involves our capture, recording or tracking features, the privacy and surveillance section below governs\n it and we treat it as the most serious category of breach we handle.\n- **Hate speech** — attacking or demeaning people because of race, ethnicity, national origin, religion,\n disability, age, sex, sexual orientation, gender identity or another protected characteristic.\n- **Doxxing** — publishing or sharing a person's private information without their agreement, or assembling it\n so that someone else can act on it. Home addresses, personal contact details, identity documents, location,\n medical and financial details all count.\n- **Sexual content involving a person who has not agreed to it being shared**, and any sexual content involving\n a minor. That second category is dealt with absolutely in the illegal activity section above.\n- **Adult content on public-facing surfaces we host for you**, unless we have agreed it in writing and it is\n lawful and age-gated where it is served.\n- **Abuse of our own people.** Threatening, abusive or discriminatory conduct towards our staff in support\n tickets, chat, calls, issue trackers or community channels. We will end the conversation, and if it continues\n we will end the relationship.\n\n### Content you publish for other people to see\n\nWhere the Service lets you publish something publicly — a page, a directory, a profile, a shared recording, a\npublic team — **you are the publisher of it, not us.** Keep other people's personal data out of it unless they\nknow and you have a basis for holding it there, provide a way for people to complain about what you have\npublished, and act on a reasoned objection rather than ignoring it. **You must not republish content that a\nperson has already had removed.**\n\nWhere you run something on our infrastructure that accepts contributions from the public, moderating it is your\nobligation. Our tools do not discharge it and our policy is not your policy.\n\n### Community and contribution channels\n\nOur public repositories, issue trackers, documentation sites and chat channels carry these rules plus any code\nof conduct published with them. Spam, off-topic promotion, brigading and abuse there are breaches of this\npolicy and we deal with them the same way.\n\n## Privacy and unlawful surveillance\n\n**This is the strictest section in this policy, and it is strict because of what our software can do.**\n\nSome of our products measure how work happens. Depending on the product and the settings your administrators\nchoose, they can capture screenshots, webcam stills, audio, screen recordings, keyboard and mouse activity\nrates, the applications and websites in use, location, and how long each of those lasted. Selling software that\ncan do that places a duty on us that a project-management tool does not carry, and this section is how we\ndischarge it.\n\n**Lawful, disclosed monitoring of your own personnel is a legitimate use of the Service. Covert monitoring is\nnot, and never will be.** Everything below follows from that one line.\n\n### Monitoring that is never permitted\n\nYou must not use the Service, or configure it, to do any of the following.\n\n- **Covert or secret monitoring of any person.** If the person being measured does not know it is happening, it\n is prohibited — whatever your reason, wherever you are, and whether or not you believe you have a lawful\n basis for the underlying processing.\n- **Monitoring anyone who has not been informed in the way their local law requires, before capture starts.**\n Telling someone afterwards is not notice. A line in a handbook they have never seen is not notice either,\n where their law demands more.\n- **Monitoring outside working hours, during breaks, on personal time, or on a person's own device**, without a\n lawful basis and their knowledge. Capture follows the work. It does not follow the person.\n- **Enabling screen capture, webcam stills, audio capture or screen recording where local law prohibits it**,\n restricts it to purposes you are not pursuing, or conditions it on a process you have not completed.\n- **Deploying a configuration the monitored person cannot see, pause, stop or exit.** Combining continuous or\n randomised capture with settings that stop a person closing the agent, logging out, or seeing that capture is\n running produces covert monitoring by construction, and we treat it as covert monitoring however it was\n arrived at.\n- **Monitoring anyone other than your own personnel in the course of their work.** The Service may be used to\n measure your employees, contractors and workers while they work for you. It may not be pointed at a partner,\n a family member, a housemate, a child, a customer, a competitor, a journalist, or any other person who is not\n yours to monitor. **Using our software as stalkerware is an immediate-termination breach and we will treat it\n as one.**\n- **Installing the desktop agent, browser extension or tracker on a device you do not own or control**, without\n the informed agreement of the person who does.\n- **Using captured data for a purpose the monitored person was not told about.** If they were told capture was\n for billing accuracy, it is not then available for discipline, performance ranking or redundancy selection.\n Purpose creep is a breach of this policy, not only of your own notice.\n- **Capturing where capture predictably exposes other people's confidential or special-category data** —\n clinical settings, legally privileged work, HR investigations, child-facing services, or a home where other\n people are visible or audible — unless capture is switched off for the people concerned.\n- **Defeating the controls that exist to protect people.** Do not work around a per-person or per-team disable,\n a blur setting, a retention limit, an excluded-application list or a capture-frequency limit in order to\n observe someone whose monitoring is meant to be off or reduced.\n\n### Other people's privacy, whatever product you use\n\nThese apply across the Service, not only to the products that measure work.\n\n- **Recording a call, meeting, screen or conversation without the notice or consent the law requires** from\n everyone involved. Several jurisdictions require every party to agree, and where participants are in\n different places the strictest rule among them is the one that governs.\n- Capturing another person's screen, device, session or account without their authorisation.\n- Using a browser extension's access to reach pages the person never intended to expose — personal banking,\n health portals, private messaging, personal webmail.\n- Harvesting personal data at scale, from us or from anywhere else, including collecting it in breach of\n another platform's terms, its rate limits or its technical protections.\n- Building biometric profiles, or inferring sensitive characteristics about people — health, beliefs, sexual\n orientation, union membership, immigration status — from anything the Service captures or holds.\n- Entering another person's personal data into our forms, or subscribing an address you do not control.\n- Putting special-category data into the Service without a lawful basis for it, or where your product annex\n states that the Service is not built to hold it.\n\n### What you promise us when you switch monitoring on\n\nBy enabling any capture or activity-measurement feature for a person, **you represent to us** that:\n\n- you are the controller of that processing, you have identified a valid lawful basis for it, and you\n understand that **consent is generally not a valid basis in an employment relationship**, because of the\n imbalance between the person asking and the person consenting;\n- you have given that person the information their law requires — what is captured, how often, why, who sees\n it, how long it is kept, and how to object — **before capture began**;\n- you have carried out a data protection impact assessment where one is required, and consulted your\n supervisory authority where the residual risk requires that;\n- you have completed any works council, trade union or employee-representative process required where that\n person works. **These are not formalities.** Co-determination in Germany, works council consent in Austria,\n works council approval in the Netherlands, prior union agreement or labour-inspectorate authorisation in\n Italy, and co-operation negotiations in Finland can each make a deployment unlawful, and the data it produced\n unusable, if they were skipped;\n- you will not enable capture for anyone in a jurisdiction that prohibits it. **Some do.** Supervision of\n performance by remote technical means is close to prohibited outright in Portugal, and keystroke and\n continuous-capture tooling has been held unlawful elsewhere on proportionality grounds; and\n- you are not using the Service to monitor covertly, or to monitor anyone outside a lawful monitoring programme\n of your own.\n\n**We make no claim that any configuration of the Service is lawful in any country.** This law differs sharply\nfrom one jurisdiction to the next and is still moving. We build the controls, publish what each one does, and\ngive you the material to run your own assessment. **The decision to switch monitoring on is yours, and so is\nthe liability that comes with it.** Your indemnity in our [Terms of Service](https://everdemand.co/tos) covers claims\nthat arise from breaking the representations above.\n\n### We act on credible reports of covert monitoring\n\n**Anyone can report suspected covert or unlawful monitoring to abuse@ever.co — you do not have to be our\ncustomer.** A monitored worker, a works council, an employee representative, a family member or a regulator can\nall use that address. We would far rather receive a report that turns out to be a misunderstanding than not\nreceive one at all.\n\nWhen we receive a credible report:\n\n- **we treat the reporter's identity as confidential.** We do not pass it to the customer without their\n agreement unless the law compels us. We know that the person best placed to report covert monitoring is\n usually the person with the most to lose by reporting it;\n- **we may require the customer to evidence** the notice it gave, the lawful basis it relies on, and the\n consultations it completed. \"Trust us\" is not evidence, and a customer that cannot produce any is treated as\n a customer that has none;\n- we may switch off specific capture features for that Workspace while we look, suspend the account, or\n terminate it, depending on what we find and how serious it is; and\n- **we will not take a customer's assurance over a credible report from the person being monitored.**\n\n**Retaliating against someone because they reported to us — dismissing them, disciplining them, withdrawing\ntheir work — is itself a breach of this policy**, and we will act on it against the customer that does it.\n\n## Security violations\n\nThe Service is shared infrastructure. The rules below protect other customers at least as much as they protect\nus.\n\n### Do not\n\n- **Access anything you were not given access to** — another customer's Workspace or data, another user's\n account, our internal systems, or any part of the Service behind a boundary you were not invited past.\n- **Probe, scan or test** the Service, our networks or our infrastructure for vulnerabilities without our prior\n written permission, except within the coordinated disclosure route below.\n- **Attack accounts** — credential stuffing, password spraying, brute forcing, or enumerating accounts and\n email addresses through sign-in, recovery or invitation endpoints.\n- **Enumerate or guess identifiers.** Share links, object ids, invitation tokens and export URLs are meant to\n be given to you, not discovered by you.\n- **Circumvent controls** — authentication, authorisation, session handling, tenant isolation, rate limits,\n quotas, access gates, licence-tier limits, or any technical protection measure.\n- **Interfere with the Service** — denial-of-service traffic, load designed or reasonably likely to degrade the\n Service for others, or any attempt to cross the isolation between one Workspace and another.\n- **Reverse engineer, decompile or disassemble** the Service, except to the extent an applicable open-source\n licence or a law that cannot be excluded permits it.\n- **Turn the Service into infrastructure for something else** — an open relay or proxy, an anonymisation or VPN\n service, a command-and-control endpoint, a port scanner, a password-cracking rig, or a staging point for an\n attack on a third party.\n\n### Credentials and access\n\n- **Accounts are for one person.** Do not share a login, and do not hand an account from one person to the next\n as staff change — create and remove accounts instead.\n- Do not share API keys, tokens or seats outside the Workspace they were issued for, and do not leave them\n anywhere others can read them.\n- **Do not give us credentials you are not entitled to use** — a colleague's, a former employer's, a shared\n mailbox you do not control, or an access token, key or configuration file belonging to someone else.\n- Do not use the Service to store, distribute or trade credentials obtained from anyone else.\n- Keep your own credentials secure, turn on multi-factor authentication where we offer it, and **tell us at\n abuse@ever.co as soon as you suspect an account has been compromised.** Delay there costs other people,\n not only you.\n\n### Security research\n\nWe want to hear from researchers, and we will not pursue anyone who acts in good faith.\n\nYour testing is in scope if you work only against your own account and your own data; do not access, modify or\nretain another customer's data; stop at the point that demonstrates the issue rather than pushing further; avoid\ndegrading the Service or causing a privacy impact; do not run automated scanning at volume; and report to us\npromptly and privately at abuse@ever.co before disclosing anywhere else.\n\n**Testing against another customer's Workspace or data is never in scope**, whatever your intent. How we handle\nreports, and what we commit to in return, is set out on our Security page.\n\n## Resource abuse\n\nYou share compute, storage, bandwidth and outbound sending reputation with every other customer. Use your\nshare.\n\n### Do not\n\n- Mine cryptocurrency, run distributed computing, or use the Service for processing that has nothing to do with\n what the Service is for.\n- Use our storage or bandwidth as a general-purpose content delivery network, a file-distribution service, a\n backup target for unrelated data, or a home for media we had no part in producing — including hot-linking\n files held with us into other sites.\n- Run automated bulk extraction against the Service, our websites, our documentation or our APIs. **Issued API\n credentials used within their documented scope and rate limits are exactly what they exist for**; scraping the\n interface, or driving an API past its published limits, is not.\n- Run unbounded or pathological workloads — agent or job loops with no termination condition, retry storms,\n runaway automation, or deliberately expensive requests repeated to see what happens.\n- Hold sessions, connections or reserved capacity open purely to keep hold of them.\n- Evade a limit rather than raise it: extra accounts to farm a free allowance, disposable addresses, referral or\n credit gaming, seat sharing, or a second Workspace created because the first one hit its ceiling.\n\n### Free plans and trials\n\nFree and trial access exists so that you can evaluate the Service and so that small teams can use it. It is not\nanonymous infrastructure. **Limits on free plans are tighter, are enforced at our discretion, and can change\nwithout notice.** We may reclaim idle free resources, and we may decline to keep providing a free plan to an\naccount whose consumption is out of proportion to what free access is for.\n\n### How we handle it\n\nSustained load that is normal for your plan is fine. Bursting is fine. What we act on is load that degrades the\nService for other people, load that is not really use of the product at all, and load that keeps growing after\nwe have asked about it.\n\n**Our first step is normally to contact you, not to cut you off.** We would rather move you onto a plan or a\nlimit that fits than lose you over a number. We throttle before we suspend, and we suspend without warning only\nwhere the platform or other customers are at risk.\n\nIf your usage above a published limit is a genuine business need rather than abuse, write to legal@ever.co\nand we will look at raising it. The numbers themselves are in the fair use section below, in your plan or Order,\nand in the Documentation.\n\n## Spam and unsolicited messaging\n\nThe Service sends mail, invitations, notifications and, in some products, text messages — sometimes from our\nown sending domains and on our own reputation. That makes messaging abuse everybody's problem here: one\ncustomer's cold-outreach campaign is what gets every other customer's invoices and password resets filtered.\n\n### Do not\n\n- **Send unsolicited bulk email, SMS or messages of any kind through the Service**, or use it to prepare, host\n or support a campaign that someone else sends.\n- **Mail a list you cannot stand behind.** You must be able to show us, on request, how each recipient came to\n be on it. Purchased, rented, swapped, harvested and scraped lists are prohibited, and so are address guessing,\n permutation and dictionary attacks.\n- **Spoof or falsify** a sender identity, a header, a reply path or a domain, or send from a domain you do not\n control. Where you send through the Service, configure SPF, DKIM and DMARC for your own domain, respect any\n warm-up schedule and sending rate we set, and keep a working reply path that a human reads.\n- **Strip, hide, disable or visually suppress** an unsubscribe link, a `List-Unsubscribe` header, a required\n postal address, or any compliance footer the Service adds. **Making the opt-out hard to find is the same\n breach as not having one.**\n- **Ignore an opt-out.** Suppression must be honoured promptly and permanently. No re-importing a suppressed\n person, no refreshing them from another source, no moving them into a second Workspace or account to escape\n the suppression list, and no treating an unsubscribe click as an engagement signal.\n- **Repurpose our transactional messages as a marketing channel.** Invitations, verification mails, share\n notifications, estimates, invoices and system notices exist to carry their own content — not to carry an offer\n to someone who never asked for one.\n- **Use invitations to reach people who will not be working in your Workspace.** The invitation flow is a\n foreseeable spam vector and we watch it.\n- **Abuse our own public endpoints** — automated submissions to our contact, newsletter or support forms,\n repeated submissions used to bomb a third party's mailbox through them, or link injection into free-text\n fields.\n\n### The law applies to you, and we do not check it for you\n\nElectronic marketing to individuals is regulated separately from data protection. Depending on where your\nrecipients are you may need prior opt-in, and the existing-customer exception is much narrower than most senders\nassume. **Working out which rule covers which recipient is yours to do.** Nothing the Service does — including\nany compliance footer it adds for you — makes a message lawful that would not otherwise be.\n\n### Deliverability is an enforcement trigger\n\nWe monitor bounce rates, spam complaints, blocklist entries and mailbox-provider feedback for traffic sent\nthrough the Service. **Where a sender's numbers put shared reputation at risk we act immediately and without\nnotice** — pausing a campaign, throttling or suspending sending, revoking a sending domain, or suspending the\naccount. We do the same on a credible complaint from a recipient, a mailbox provider or a blocklist operator.\n\nIf you received a message from someone using the Service and you did not ask for it, report it to\nabuse@ever.co with the full headers if you have them.\n\n## Malware and hostile files\n\n### Do not upload, store, link to or distribute\n\n- **Malware of any kind** — viruses, worms, trojans, ransomware, rootkits, keyloggers, spyware and stalkerware.\n- **Exploit code, exploit kits, cracking and credential-stuffing tools**, and payloads intended to establish or\n keep unauthorised access to anything.\n- **Files built to attack whatever opens them** — decompression bombs, entity-expansion payloads, deliberately\n malformed documents, and uploads crafted to break a parser, a preview renderer or a downstream viewer.\n- **Values crafted to execute somewhere else.** Text you put into a field that is later exported — a name, a\n translation string, a note, a description — must not be built to run as a formula, a script or a command in\n whatever opens the export.\n- **Phishing and credential-harvesting pages**, fake sign-in screens, and deceptive destinations of any kind.\n **A link on our domain lends our credibility to whatever it points at**, which is exactly why share links\n attract this and exactly why we move fast on it.\n\n### We scan, and we are telling you so\n\nWe may scan, sandbox, quarantine, refuse, disable or delete files, links and messages that we reasonably believe\nare hostile, and we may do it without prior notice.\n\n**We are stating this openly because scanning your uploads is itself a processing activity, and undisclosed\nprocessing is not something we are willing to do.** What it means for personal data is set out in our\n[Privacy Policy](https://everdemand.co/privacy).\n\nAutomated detection is imperfect in both directions. If we have quarantined something wrongly, tell us at\nabuse@ever.co and we will look again.\n\n### Security work with a legitimate need\n\nIf your work genuinely involves handling malware samples — you run a security team, or you research this for a\nliving — do not do it in the Service without asking us first. Write to legal@ever.co, tell us what you need\nand how it will be contained, and we will either agree it in writing or tell you no. **Doing it without that\nagreement is a breach**, however good the reason.\n\n### Your own hygiene\n\nKeep the devices and networks you use to reach the Service reasonably secure and up to date, and tell us at\nabuse@ever.co if you believe a device with access to your Workspace has been compromised.\n\n## AI features, assistants and agents\n\nThese rules apply wherever the Service uses a model on your behalf — an assistant, a generated document, an\nautonomous agent, a connected tool endpoint, or a feature you drive with your own provider key. They sit on top\nof everything else in this policy, and alongside the AI terms in our [Terms of Service](https://everdemand.co/tos).\n\n**Anything an agent does under your credentials is your act.** Automating a decision does not move\nresponsibility for it.\n\n### Do not generate unlawful, deceptive or infringing content\n\n- Content that is unlawful, defamatory, harassing or discriminatory. The rest of this policy applies to\n generated output exactly as it applies to text you typed yourself.\n- Fraud material — phishing text, fake invoices, scam messages, or anything designed to deceive a person into\n parting with money, credentials or access.\n- Impersonation of a real person or organisation, including synthetic voice, image or video of a real person\n without their agreement, and content presented as authentic when it is not.\n- Fabricated facts about a named person or business: reviews, testimonials, endorsements, qualifications,\n awards, or claims about their conduct, finances or history.\n- Content that infringes someone else's rights, and output presented as original where it is not.\n- Bulk low-value content produced to manipulate search rankings — doorway pages, mirror sites, near-duplicate\n sites generated at scale, cloaking and link schemes.\n- Removing or falsifying provenance metadata or watermarks that mark content as machine-generated, and passing\n model output off as human-created where doing so misleads someone whose decision depends on it.\n\n### Do not make consequential decisions about people without human review\n\n**Model output is an input to a decision. It is never the decision.**\n\nWhere a decision materially affects a person — hiring, promotion, discipline, dismissal, pay, credit, insurance,\ntenancy, education, benefits, access to essential services, or legal and immigration status — you must not treat\na score, ranking, band, signal, summary or recommendation produced through the Service as the sole or\ndeterminative basis for it. **A human being with authority and real discretion must consider the case and be\nable to reach a different answer.**\n\nThat applies with particular force to anything derived from monitoring. An activity percentage, a productivity\nscore, a screenshot summary or an attention metric is not a finding about a person's performance, and treating\nit as one is both a breach of this policy and, in many places, a breach of the law.\n\nYou must not use these features to discriminate on a protected characteristic, directly or through a proxy for\none. **Where we find a customer doing this, we may switch the feature off for that Workspace.**\n\n### Do not present output as professional advice\n\nDo not use the Service to give medical diagnosis or treatment decisions, clinical decision support, legal\nadvice, or financial and investment advice in a way that a recipient would reasonably take as coming from a\nqualified professional. Do not use it in the design or development of weapons.\n\n### Do not attack the models or the pipeline\n\n- **No attempts to extract training data, model weights, system prompts, tool definitions, configuration, or\n another customer's data or prompts.**\n- **No prompt injection.** Do not place instructions in content, files, profile fields, repositories, tickets,\n commits or messages that are designed to make an assistant ignore its policies, act outside its permissions,\n operate on another party's data, call a tool it was not authorised to call, or disclose secrets.\n- **No circumventing safety measures** — content filters, approval gates, human-in-the-loop confirmations, usage\n limits or policy checks. That includes automating a confirmation so an action is taken without a real human\n decision behind it. **The approval gates are load-bearing. Defeating one is a severe breach and we may block\n access immediately.**\n- No using our AI endpoints as a general-purpose relay: proxying traffic, reaching internal or arbitrary hosts,\n or pushing work unrelated to your use of the Service through us to a provider.\n- No supplying provider credentials you are not entitled to use, and no sending a provider content you have no\n right to send it. Where you bring your own key, that provider's terms bind you as well as ours do.\n\n### Do not compete with what you are using\n\nDo not use the Service, its output or its features to develop, train, fine-tune, distil or benchmark a competing\nmodel or product, and do not resell, sublicense or transfer model access obtained through us.\n\n## Fair use and published limits\n\nEvery plan has limits. **We publish them, rather than leaving \"fair use\" to mean whatever we decide later.**\n\n### Where the numbers are\n\nThe limits that apply to you are in your plan description or Order, in the Documentation for the Service, and in\nthe product-specific section of this policy. Where the same limit appears in more than one of those, the one in\nyour Order wins.\n\nDepending on the product, they cover:\n\n- API request rate, and the burst allowance above it;\n- concurrent connections — streaming, websocket, agent and tool endpoints;\n- total stored data per Workspace, and the size of any single upload;\n- capture and media volume, where the product records screenshots, recordings or other media;\n- outbound message volume and sending rate;\n- agent, job or build run time; and\n- seats, Workspaces and connected integrations.\n\n### What \"unlimited\" means when we say it\n\nWhere a plan is described as unlimited, or as fair use, it means **unlimited normal use of the product as it is\nsold** — not permission to use us as generic storage, generic compute or a content delivery network. When your\nusage stops resembling use of the product, it stops being covered by the word.\n\n### How limits are applied\n\nRate limits are enforced technically: over the limit you get an error and a retry signal, not a surprise\ninvoice. **We do not bill overage that was not in your Order.**\n\nWhere a storage or volume ceiling is exceeded, we contact you first and give you a reasonable period to reduce\nusage or move to a plan that fits before we restrict anything. Free and trial plans are the exception, and the\nresource abuse section above says how.\n\n### When limits change\n\nWe may change published limits. Where a change materially reduces what you can do on a plan you are paying for,\nwe give you notice in the way the changes section of our [Terms of Service](https://everdemand.co/tos) requires, and\nyou may cancel before it takes effect. Increases, and changes to free-plan limits, take effect when we publish\nthem.\n\nIf you have a genuine need above a published limit, ask us at legal@ever.co. **We would much rather agree a\nhigher limit with you in advance than discover the traffic.**\n\n## Annex: Ever Demand — couriers, addresses and deliveries\n\nEver Demand reads a working person's position every few seconds and shows it live to their dispatcher,\nto the shop and to a member of the public waiting for a delivery. It also holds the home addresses of people\nwho never agreed to anything. Those two facts are what this annex is about, and they are why it is longer\nthan the product's size would suggest.\n\n### What this binds, and what it offers everyone else\n\n**These rules bind [everdemand.co](https://everdemand.co), the documentation site, and any instance of the\nplatform we host for you.** If we host your instance, breaking a rule here is a breach of your agreement with\nus and the enforcement section below applies to you in full.\n\n**If you run the software yourself, this annex imposes nothing on you.** The code licence governs the code,\nand we do not add conditions to it through a policy page. What this annex is, in that situation, is the\nstandard we would hold ourselves to and the one we would expect of an operator we hosted — published because\nthe software enforces almost none of it, and because a courier reading it deserves to know what good practice\nlooks like. Where we do host you, the Data Processing Addendum puts the same duties in binding terms.\n\n### The Online switch is the whole design, and you must not defeat it\n\nThe courier application reads position only while the courier's own status is set to Online. **That gate is\nthe single control standing between a dispatch tool and a tracking device, and it lives in client code you\nbuild and ship.** So, on an instance we host:\n\n- **You must not ship a modified courier application that reports position while the courier's status is\n Offline**, that resets the status without the courier doing it, that hides the control, or that makes going\n offline harder than going online.\n- **You must not infer or reconstruct position by other means when a courier is off duty** — polling a device,\n reading location from another application you also control, or treating a delivery-completion event as\n permission to keep sampling.\n- **You must not track a courier outside their working time.** A shift that has ended is not a shorter shift.\n Travel to the depot, a break, an unpaid gap between assignments and the journey home are not working time\n because your operation would find it convenient if they were.\n- **You must not track a courier who is not on duty for you** — someone else's courier, a courier on another\n operator's shift, or a person carrying a device you issued for a job they are not currently doing.\n\nThe platform stores a courier's current position and overwrites it with the next reading, so no route history\naccumulates by itself. **If you build one — logging each position, or deriving a track from them — that is a\nnew processing operation you have chosen to start**, and everything below about purpose applies to it with\nfull force.\n\n### The live map may only be as wide as the delivery\n\nA courier's position is shown to the ordering customer while a delivery is running. That is disclosure of a\nworker's real-time location to a member of the public, and it is only defensible while it is tied to that\ndelivery.\n\n- **Customer-facing visibility must be confined to the active delivery.** Not before it is assigned, not after\n it is completed, and not to a customer whose order the courier is not carrying.\n- **Internal visibility must be confined to people who need it to dispatch.** A live map is not general office\n entertainment, and access to it is an access decision you have to make deliberately.\n- **You must not expose a courier's position through an interface, a share link, an embed or an export to\n anyone outside the delivery it belongs to.**\n- **You must not use the tracking interface to harvest positions** — yours or anyone else's. Pulling courier\n locations in bulk is a surveillance act, whatever endpoint it goes through, and we treat it as one rather\n than as a rate-limit question.\n\n### Location and work counters may only be used for what the courier was told\n\nAlongside position, the platform accumulates lifetime deliveries, deliveries today, distance travelled today,\norders skipped, and the record of going on and off duty. There is also a switch that turns a courier's account\noff.\n\n- **You must not use any of it for a purpose you did not tell the courier about before you started.** If a\n courier was told tracking was for dispatch and delivery estimates, it is not then available for performance\n ranking, pay decisions, discipline, redundancy selection or a reference.\n- **You must not reconstruct a courier's movements to check something you were not open about** — how long a\n break lasted, whether they went home mid-shift, where they live, whether they attended a union meeting,\n whether they work for someone else.\n- **You must not infer anything about a courier's health, beliefs, union membership or private life** from\n where they went or how far they travelled.\n- **You must not combine these counters with data from another system to build a score you never disclosed.**\n A metric that was described as operational and is used as a judgement has become something the courier was\n entitled to be told about.\n- **Switching a courier's account off is an employment act, not a configuration change.** Do it for a reason\n you would be willing to put in writing to the person it affects.\n\n### Other people's addresses and telephone numbers\n\nThe platform will accept any address and telephone number typed into it, from anyone, with no check that the\nperson at the other end has any idea.\n\n- **You must not enter a third party's address, apartment number or telephone number without a basis for\n holding it.** Delivering to someone at their home because they are expecting a delivery is a basis.\n Collecting an address because it might be useful later is not.\n- **The free-text delivery notes field is not a place to record anything about a person beyond finding the\n door.** People write what helps a courier; you must not turn it into a comments field about a household.\n- **You must not use the invite-request flow to collect residential addresses for any purpose other than\n deciding whether to serve that address**, and **you must not keep refused requests as a marketing list.** A\n person who asked whether you deliver to their street has not asked to hear from you.\n- **You must not use addresses held for delivery for anything else** — leaflet drops, list rental, area\n profiling, or sale to anyone.\n- **Everyone in the paragraphs above has a right to be told you hold their data**, including the courier\n enrolled by an administrator and the recipient who never placed the order. Giving that notice is yours, and\n we cannot give it for you because in most cases we have no way to reach them.\n\n### What may be sold and delivered through an instance we host\n\nThe platform has no field that marks a product as restricted, no age check, no allergen record and no\ntemperature control. **Every one of those is something you build or something you go without, and going\nwithout it is not an option the law offers you.**\n\n- **You must not offer or arrange delivery of goods you are not licensed to supply where you supply them** —\n controlled substances, prescription medicines, weapons and ammunition, untaxed or contraband alcohol and\n tobacco, counterfeit goods, live animals, or hazardous materials.\n- **You must not sell age-restricted goods through a deployment we host without an age-verification and\n handover process of your own.** Nothing in the product distinguishes a restricted item from a loaf of bread.\n- **Where you handle food, you must hold the licences, run the temperature controls and give the allergen\n information your local law requires.** The product is marketed for food delivery and carries no allergen\n field; that gap is yours to close, and a delivery that harms someone is not a software fault.\n- **You must not use the platform's push notifications, or a merchant's order mailbox and order telephone\n number, for unsolicited marketing** to shoppers or to couriers.\n\n### Configuration that turns into a breach\n\nSome of this software's defaults are development conveniences, and leaving them on in production is not a\nmisconfiguration so much as an open door. On an instance we host, **you must not run with**:\n\n- the fake data generator or the bulk customer generator enabled;\n- a fake invite code configured, which lets anyone past the invite gate;\n- the administrator password-reset shortcut enabled; or\n- **the signing and session secrets left at the values the repository ships with.** Those values are published\n in public source code, which means they are not secrets from anybody.\n\nYou must also not store a payment secret key belonging to anyone other than the merchant whose gateway account\nit is, and **you must not use a merchant's stored keys for anything beyond routing that merchant's own\ntransactions.** The security annex explains why those keys are worth protecting more carefully than their\ncurrent storage suggests.\n\n### Reporting, and what happens when we cannot reach the deployment\n\nIf you believe a courier is being tracked off duty, that location data is being used for something the courier\nwas never told about, or that someone's address is being held or used without a basis, tell us at\nabuse@ever.co. **You do not need to be our customer, and if you are the courier this was done to, your\nidentity stays with us.** Tell us what you can: the business, what you saw, and how we can reach you.\n\nThen the honest part. **In almost every deployment of this product we are not in the picture at all**, and we\ncannot switch off a feature, read a database or suspend an account on a system somebody else runs. Where that\nis the situation:\n\n- we will tell you plainly that the deployment is not ours, rather than leaving you waiting;\n- we will tell you who the operator appears to be, where we can establish it, so your report reaches somebody\n who can act; and\n- we will tell you that you can go to the data protection authority in your own country, and to your national\n labour authority, without our permission and without coming through us first.\n\nWhere the instance **is** one we host, none of that applies and the enforcement section below does: we can\nrequire you to evidence the notice you gave your couriers, switch tracking off for that instance, suspend it,\nor end it.\n\n## Reporting abuse\n\n**abuse@ever.co** — one address, read by people, for anything on this page.\n\n**You do not have to be our customer to use it.** We publish it for the person with no other route: a worker who\nbelieves they are being monitored covertly, someone who received a message they never asked for, a rights\nholder, a researcher, a works council, a parent, a regulator. Reports from people who are not customers get the\nsame handling as reports from people who are.\n\n### What to tell us\n\nThe more of this you can give us, the faster we can act. Send what you have — an incomplete report is still\nworth sending.\n\n- **What happened**, in your own words.\n- **Where** — the URL, share link, workspace, sending address, message headers, or the name of the application\n or agent involved. Precise enough that we can find it without guessing.\n- **When**, with dates, times and the time zone you are quoting.\n- **Who is affected**, if you can say, including whether that is you.\n- **Evidence** — headers, message ids, screenshots, links. Attach it where you can, rather than describing it.\n- **What you are asking for** — content removed, messages stopped, monitoring investigated, information.\n- **How to reach you**, if you want an answer. You may report anonymously, but we then cannot come back to you\n for the detail that often decides a case.\n\nSome reports have a better route. A request about your own personal data goes to privacy@ever.co. A security\nvulnerability goes through the coordinated disclosure route in the security violations section above. An\nintellectual property complaint needs the specific details listed in the infringing content section.\n\n**If you are reporting suspected covert monitoring, say so in the first line.** Those go to the front of the\nqueue.\n\n### What we do with it\n\n- **We acknowledge within two business days.**\n- **We give you a substantive answer, or a real status update, within ten business days.** Investigations that\n involve a customer's own workforce sometimes take longer than that. Where they do we will tell you where it\n has got to rather than going quiet on you.\n- **Where a person is at immediate risk, we act first and correspond afterwards.**\n- **We keep the reporter's identity confidential.** We do not pass it to the customer without your agreement\n unless the law compels us, and where that happens we will tell you if we are permitted to.\n- We tell you the outcome in general terms. **We will not hand you another party's account details, internal\n correspondence or personal data**, however much you would like us to. The same protection applies to you.\n\n### What we are not\n\nWe are not a court and we are not an arbitrator. Where a report is really a commercial or contractual dispute\nbetween you and someone else, we will say so and decline to take a side. We enforce our own rules against our\nown customers — that is the whole of our jurisdiction.\n\n**Deliberately false reports, and automated or mass reporting used as a weapon, are themselves a breach of this\npolicy.** Being wrong in good faith is not. We would far rather read a hundred honest reports that come to\nnothing than miss the one that mattered.\n\n## Enforcement\n\n### How we decide\n\nWe aim to be proportionate: the smallest action that actually stops the problem, applied to the narrowest part\nof the account that will do it. We weigh how serious the conduct is, whether anyone is being harmed right now,\nwhether it looks deliberate, whether it is still going on, and what you did when we raised it.\n\n**We also judge you by what you do about abuse by the people using the Service under your Subscription.** A\ncustomer whose End Users cause a problem and who moves quickly to stop it is in a very different position from\none who cannot or will not.\n\n### Investigation\n\nWe may look into a report, or into something we detect ourselves. That can include reviewing account and\nconfiguration metadata, logs, message headers, sending records, public-facing content, and content you have made\navailable to us — and asking you for evidence: the notice you gave your monitored personnel, your opt-in\nrecords, your right to use content, your authority for an integration.\n\n**We do not routinely read the contents of your Workspace.** Where an investigation genuinely requires looking\nat Customer Data, we look at the minimum needed, restrict it to staff who need it, and record that we did.\n\nWe may preserve material relevant to an investigation, and we may hold an account in a restricted state while we\nwork.\n\n### What we can do\n\n- Ask you to fix it, with a deadline.\n- Remove, disable or de-publish specific content, a public page, a share link or a custom domain.\n- Restrict or switch off a specific feature for a Workspace or a user — **including capture and monitoring\n features**.\n- Reduce a rate limit, throttle traffic, pause a campaign, or revoke a sending domain.\n- Suspend a user, a Workspace, a project or the whole account.\n- Terminate your account and these Terms.\n- Decline to contract with you again.\n- Recover our costs, where the law allows it.\n\n### With or without notice\n\n**Where the problem can be fixed, we tell you first and give you a chance to fix it.** That is the normal path\nand most matters end there.\n\n**We act immediately, without prior notice, where waiting would be irresponsible** — including:\n\n- anything in the never-permitted list in the illegal activity section;\n- covert or unlawful monitoring of a person;\n- malware, phishing, or a live security incident;\n- conduct putting shared infrastructure, other customers or sending reputation at risk;\n- a court order, a regulator's direction, a law-enforcement requirement or a takedown obligation; and\n- abuse that continues after we have already raised it with you.\n\nWhere we act without notice we tell you as soon as we reasonably can — what we did, why, and what would have to\nchange for us to undo it — unless a legal obligation stops us. Suspension is also dealt with in the term,\nsuspension and termination section of our [Terms of Service](https://everdemand.co/tos), and everything there applies\nhere.\n\n### Telling other people\n\nWhere the law requires it, we notify affected people, rights holders and authorities, and we respond to\nregulators, courts and law enforcement. Where someone's safety is at risk, we may notify without being required\nto. We may also tell a mailbox provider, a blocklist operator or a source platform what we did about a complaint\nthey sent us.\n\n**Some legal demands prohibit us from telling you that they exist.** Where that is the case, we comply with the\ndemand.\n\n### Money\n\n**Where we terminate because you broke this policy, you get no refund.**\n\n- Fees for a period already served remain payable.\n- A period during which the account was suspended for abuse is not refunded. It is still part of your paid term.\n- The 30-day money-back guarantee in our Refund Policy is not available on a termination for breach of this\n policy.\n- The export window we allow after an ordinary termination may be withheld where we terminated for cause, as our\n [Terms of Service](https://everdemand.co/tos) sets out.\n\nYour indemnity in those Terms covers claims brought against us because of what you or your End Users did in\nbreach of this policy.\n\n### If we get it wrong\n\nWe will sometimes get it wrong. Automated detection produces false positives, and reports are sometimes mistaken\nor malicious.\n\n**Write to legal@ever.co and we will look again** — with someone who was not part of the original decision,\nwherever we practically can. If we were wrong we restore access, and we do not charge you for the period we took\nit away. Tell us anything that changes the picture: a decision made on partial information is exactly the kind\nwe want to revisit.\n\n### Two things this section does not do\n\n**It does not oblige us to monitor.** We have no general duty to review what you put into the Service, and\nchoosing not to act on one thing never gives up our right to act on another. Acting in good faith on a report\ndoes not make us responsible for what someone else did.\n\n**It does not take away a consumer's rights.** If you are dealing with us as a consumer rather than for business\npurposes, your mandatory statutory rights stand whatever this section says.\n\n## Changes to this policy\n\nAbuse moves faster than contracts do, so this policy changes more often than the rest of our documents.\n**Every version carries a number and an effective date at the top, and superseded versions stay published**, so\nyou can always establish which rules applied on a given day.\n\n**Where a change materially reduces what you are allowed to do**, we give you at least thirty (30) days' notice\nbefore it takes effect — by email to your administrative contact and in the Service — and you may cancel before\nit applies, on the terms in the changes section of our [Terms of Service](https://everdemand.co/tos).\n\n**Everything else takes effect when we publish it.** That covers new examples of conduct this policy already\nprohibits, clarifications, corrections, and changes we make because the law, a regulator, a court, a payment\nprovider or an infrastructure provider requires them — sometimes at no notice at all, because we are given none.\n\nThe version in force when you use the Service is the version that governs that use. Continuing to use the\nService after a change has taken effect means you accept it.\n\n## How to reach us\n\nWrite to a person, not a form. These addresses are monitored and we answer them.\n\n- **Abuse, harmful content, covert monitoring, spam, or a security problem** — abuse@ever.co. **Anyone may\n use this address, customer or not.**\n- **Questions about this policy, or about a decision we made under it** — legal@ever.co\n- **Your personal data, and any request about it** — privacy@ever.co\n\nBy post: **Ever Technologies LTD**, Mladost 2, bl. 211, ent. A, Sofia 1799, Bulgaria — registered in Bulgaria under company number\n204599535.\n\nWe correspond in English.\n\nThis document is version 1.0.2 of the Acceptable Use Policy for\n[everdemand.co](https://everdemand.co), in force from 2026-08-02. It forms part of our\n[Terms of Service](https://everdemand.co/tos), and earlier versions, with the dates they applied, are published\nalongside them."
|
|
339
339
|
}
|