Legal › Privacy Policy
Privacy Policy
How Enemo Consulting Group, Inc. handles personal information when people use EnemoAi, visit www.enemo.ai or receive our emails.
Contents
- Who we are and what this Policy covers
- Information we collect and where it comes from
- How we use information, and our legal bases
- Who can see your information inside your business
- Who we disclose information to
- California and other U.S. state privacy rights
- EU, UK and Swiss rights
- People named in public records
- How long we keep information
- Where information is processed, and international transfers
- Your choices and how to exercise your rights
- Security
- Children
- Changes to this Policy
- Contact and version history
1. Who we are and what this Policy covers
1.1EnemoAi is provided by Enemo Consulting Group, Inc., a wholly owned subsidiary of The Ravine of Willows, Inc., 1412 Main St STE 609, Dallas, TX 75202, United States (“EnemoAi”, “we”, “us”). Contact: hello@enemo.ai (please use the subject “Privacy”).
1.2This Policy covers personal information about (a) people who use EnemoAi on behalf of a business (“Authorized Users”), (b) visitors to www.enemo.ai, (c) people who receive our emails, (d) people named in the public records EnemoAi reads, and (e) people invited to join a business on EnemoAi, whose WorkPair ID the person inviting them enters. Capitalized words not defined here have the meanings in the Terms of Service.
1.3Two roles. For account, billing, security and website information, EnemoAi decides how the information is used and is its controller (or business under U.S. state laws). For the content a business puts into EnemoAi (questions, uploaded documents, answers, decisions, its watchlist, and the business data it connects through the Data API or imports), EnemoAi acts for that business as its processor (or service provider) under our Data Processing Addendum; the business’s own privacy notice also applies, and we may refer requests about that content to the business.
1.4EnemoAi is a service for businesses in the United States. It is not directed at people in the European Union, the European Economic Area or the United Kingdom, but Sections 3, 7 and 10 apply wherever their laws do. This Policy does not cover WorkPair, Link or Stripe, which have their own privacy policies.
2. Information we collect and where it comes from
From WorkPair, when you sign in (with your consent on WorkPair)
- A pairwise identifier that WorkPair creates for you for EnemoAi only, which other services cannot link to you.
- Your legal name, your verified email address and your public WorkPair ID.
- Confirmation that WorkPair has verified your identity to assurance level 2, and the identifiers of the signed proof and its status entry, so we can tell if it is later withdrawn.
- For your business: its WorkPair organization ID, legal name, domain, its standing on WorkPair (active, suspended or closed, and whether it is business-verified, pending, needs re-verification or unverified), the profile it publishes on WorkPair (country, region, sector, legal form, size and website), and your role (owner, admin or member).
We do not receive your date of birth, address, identity documents, photographs taken for verification or biometric data. WorkPair keeps those under its own policies.
From you and your business
- Questions and answers: what you ask, the Mode, any follow-up, the answer and its citations, quotes you approve or decline, and decisions you log with their review dates and outcomes.
- Uploaded documents: files you attach for review (PDF, images, Word, Excel, text, CSV), and the text extracted from them.
- Company profile: for a business on WorkPair, the organization information above, which comes from its WorkPair account, is refreshed from WorkPair and cannot be edited in EnemoAi, with the date we last fetched it, and the logo the owner adds; for businesses that set up before WorkPair sign-in, the industry, size, state and employer identification number they entered.
- Business data your business connects through the EnemoAi Data API or by importing files: bank, card, loan and credit-line accounts (balances, limits, covenants; only the last 4 digits of an account number), transactions, ledger entries and chart of accounts, invoices and bills, payroll totals by pay period, sales, inventory, customers and suppliers, KPIs, and documents such as contracts and board decks. This is business information. It can include people’s names where they appear in a transaction description or a document. EnemoAi refuses payroll records about individual employees (names, identifiers, Social Security numbers, addresses, bank details or pay rates), department payroll totals covering fewer than 3 people, and customers or suppliers named as individuals, family trusts or estates.
- Watchlist: the companies your business asks EnemoAi to watch, their role (supplier, customer, lender and so on), and which possible matches you confirm or dismiss.
- Preferences: profile photo and company logo (optional), read-aloud voice, approval and spending limits, sharing defaults, and email preferences.
- Invitations: the WorkPair ID of each person your business invites, the role and any spending limit, and who sent the invitation.
- Messages: what you send us at hello@enemo.ai.
- Accounts from before WorkPair sign-in: these were opened with a typed name and email address. EnemoAi no longer has passwords: every password hash has been deleted. Linking WorkPair replaces the typed name and email with WorkPair’s.
Created when you use EnemoAi
- Wallet and billing records: top-ups, charges, refunds and credits, who ran each charge, the price, the payment reference, and the amount and currency paid; your Monitoring subscription status.
- Usage and service data: when questions were asked, their price and computing cost, timings, which alerts were read, and error states.
- Security records: session records (we store only a cryptographic hash of your session token) and how each session began; WorkPair sign-in steps; the security log of sign-ins, sign-outs, team changes and similar events, with the network each came from; counters used for abuse limits; reports people make to us about a teammate or an answer; bans, which are tied to a WorkPair identity; and the record of each legal document you accept. In these records we keep only the first three parts of an IPv4 address or the first 48 bits of an IPv6 address, never the full address. Records of password sign-in attempts, which held full addresses, were deleted when passwords were retired.
- Data API keys and what is built from business data: for each key, a cryptographic hash of it (never the key itself), its name, the data types it may send, its rate limit, who created or revoked it, and when and from which network it was last used; a record of each import; and the cash forecasts, warnings and public-record matches EnemoAi works out from your business’s data. Each use of a key is written to the security log (which key, what it did and how many records, never the data).
- What EnemoAi knows about your business (its knowledge profile): facts EnemoAi works out from your business’s data (for example its cash, credit lines, largest customers and suppliers), from the contracts and loan agreements your business keeps with EnemoAi (the other parties, covenants, renewal and termination dates and pricing terms, each with the sentence it came from), from the decisions you log and from EnemoAi’s earlier answers to you, plus anything you tell it and your confirmations, corrections and dismissals. EnemoAi reads contracts itself, on its own servers; nothing is sent to another service to read them. The parties it remembers are businesses: names that look like a private individual’s are left out.
- Follow-through drafts: letters, memos, notices and financing packets EnemoAi drafts at your request after an answer, your instructions for them, your edits, the sources they cite and the check of their figures. EnemoAi never sends a draft to anyone; you do.
- Server logs: our servers’ operational logs record each request to our API, including the full IP address it came from, the time and the address requested (never question content). They are deleted automatically after 30 days.
From payment providers
When the owner tops up the wallet or subscribes to Monitoring, Link (Stripe’s merchant-of-record service) collects the payment details directly. We receive confirmation of payment, the amount, currency, tax charged, a payment reference, and notices of refunds and disputes. We never receive full card or bank account numbers.
From your browser
Your browser sends its IP address and user agent to our servers and our website host with each request, as all browsers do. We use one sign-in cookie and, briefly, one sign-in-flow cookie; see the Cookie Notice. We use no analytics or advertising trackers.
From our apps
The EnemoAi apps for iPhone and iPad, Mac, Apple Vision Pro, Apple TV and Android sign you in through WorkPair like the website. Apple TV signs in with a code instead: the TV shows a short code, and a person signed in to EnemoAi on a phone or computer enters it at www.enemo.ai/tv and approves (after confirming with WorkPair); the TV is then signed in as that person, for their business. While a TV waits, we keep a cryptographic hash of its code and of the secret it uses to collect its sign-in (never the codes themselves), the label the TV gives itself, the app’s version, and who approved or declined it. For each app sign-in we keep a cryptographic hash of its sign-in token (never the token), which app it is and its version, a device label (such as “EnemoAi for iPhone or iPad”, or a name the app supplies), when it began and when it was last used. If you allow notifications, the app sends us its push token from Apple or Google, the notification service it uses, your device’s language and time zone (so the morning briefing arrives at 7am your time) and the app’s version. The apps contain no analytics, advertising or tracking software, and we do not collect your contacts, location, photos or other information from your device.
From public sources
EnemoAi reads SEC filings, including the financial figures companies tag in them (XBRL data), and records published by U.S. bankruptcy courts, the FDIC, the Treasury Department’s Office of Foreign Assets Control, the FDA, the Consumer Product Safety Commission, the Justice Department, the Federal Register, the Consumer Financial Protection Bureau (only yearly counts of complaints per company, never a complaint itself or anything about the consumer who filed it), the Labor Department (OSHA inspections and Wage and Hour Division cases), the Environmental Protection Agency, the National Highway Traffic Safety Administration, USAspending.gov (federal contract, grant and loan awards), the Commerce Department’s Consolidated Screening List (entities only), the Federal Trade Commission, the National Labor Relations Board, U.S. district courts (lawsuits between businesses only), state labor departments (WARN layoff notices, never a contact person), and state business registries and UCC filing offices (businesses only, never a registered agent, officer or individual debtor). It also reads U.S. economic and industry statistics from the Federal Reserve, the Treasury Department, the Bureau of Labor Statistics and the Census Bureau, which are aggregate figures and name no one. These records are about businesses, but some name individuals (for example, an executive in a filing, or a person named in a Justice Department press release). We do not build profiles of individuals; Section 8 explains how we limit this.
3. How we use information, and our legal bases
Where the EU or UK General Data Protection Regulation (“GDPR”) applies, we rely on the legal bases shown.
| Purpose | Information used | Legal basis (GDPR) |
|---|---|---|
| Create and run your business’s account; sign you in through WorkPair; keep names and emails current from WorkPair | WorkPair information, account and security records | Contract; legitimate interests in operating a verified-business service |
| Answer questions, review documents, run replays, read answers aloud, keep your library and decision ledger | Questions, documents, answers, preferences | Contract (as processor for your business) |
| Use the business data your business connects: answer its questions with its own figures, and, if it turns on live monitoring, forecast its cash, warn it, and check its customers, suppliers, banks and lenders against public records | Business data, keys and import records, public records | Contract (as processor for your business) |
| Remember what EnemoAi learns about your business (its knowledge profile) and use it in every answer and draft; read the contracts your business keeps with EnemoAi; check the other parties to them against public records and count down to their covenant tests and notice dates if your business turns on live monitoring; write the drafts you ask for | Business data, contracts, your decisions and earlier answers, what you tell EnemoAi, public records | Contract (as processor for your business) |
| Decision dataset contributions, only with consent: if your business’s owner or an admin allows contributions and you opt in, each decision you log, tag with a kind of move and review with an outcome rating adds an anonymous record (the kind of move from EnemoAi’s list, the quarter it was logged, the review period in four bands, and the rating) to the dataset EnemoAi uses to show every business how such moves turn out, only in totals of at least 5 and labeled as self-reported. The record has no words, figures, names, industry, business or person. We keep a link from your decision to its record inside your business, protected like your other records, only so that we can delete the record when consent ends | Kind of move, quarter, review period, outcome rating; consent records (who agreed, to which wording and version, when, network prefix) | Consent (you may withdraw it at any time; withdrawal deletes the records) |
| Price questions, show quotes, charge the wallet, give refunds and credits, show the free-month savings notice | Usage, wallet and billing records | Contract |
| Monitoring: watch the companies your business lists, send alerts and the morning briefing | Watchlist, email address, email preferences, public records | Contract; for people named in public records, legitimate interests (Section 8) |
| Send push notifications to our apps, if you allow them: serious alerts, that the morning briefing is ready, and that a long answer is ready | Push token, notification preferences, language and time zone | Contract; legitimate interests |
| Send service emails: alerts, briefings, account closure confirmations, notices of changes to terms | Name, email address | Contract; legitimate interests |
| Let a business invite people by their WorkPair ID | Invitee’s WorkPair ID, role and spending limit | Legitimate interests of the business and of EnemoAi in letting teams form |
| Keep EnemoAi secure: keep the security log, apply abuse limits, require a fresh WorkPair sign-in for sensitive actions, review reports, ban WorkPair identities that abuse EnemoAi, investigate incidents, enforce our terms | Security records, usage records | Legitimate interests in security; legal obligation |
| Record acceptance of our terms | Acceptance records | Legitimate interests in proving the agreement; legal obligation |
| Improve pricing and reliability (for example, tuning the estimator that prices questions) | Usage and service data, never the content of questions, documents or answers | Legitimate interests |
| Accounting, tax and legal compliance; respond to lawful requests; establish or defend legal claims | Wallet and billing records, acceptance records, as needed | Legal obligation; legitimate interests |
We do not use personal information for advertising, sell it, or make decisions about individuals that produce legal or similarly significant effects by automated means. We do not use the content of questions, documents, answers or the business data your business connects to train AI models, and never use one business’s data for another (the only exception is the anonymous decision records described above, and only with your business’s and your consent), and under Anthropic’s commercial terms, Anthropic does not train its models on what we send it.
4. Who can see your information inside your business
4.1Your questions, quotes, answers, uploaded documents and logged decisions are private to you, including from your business’s owner and admins, unless you share them with the team. This is enforced in the database by row-level security, not only in the app. Text you send to be read aloud is kept for up to a day and can be fetched only with the private, unguessable link the app creates for you.
4.2The owner and admins can see who spent what, in which Mode and when, but never the question; each person’s email address and when they last asked a question; and your business’s security log (who signed in or out, invited, removed or changed whom, and when, with a shortened network address). The security log shows that a report was made to EnemoAi staff, but never who made it or who or what it was about. Members see only their own charges, and see teammates’ names and roles only. Each person sees only their own WorkPair ID. The watchlist and alerts are shared across the business.
4.3Business data your business connects belongs to the whole business: everyone in it can ask questions that use it and see the cash forecast and warnings. Only the owner and admins can create or revoke Data API keys, import or delete data, and see the keys, imports and where each record came from; their data download includes it. It is never shown to, or used for, any other business.
4.3aWhat EnemoAi knows about your business follows the same rules. Facts from your business’s data and contracts, and facts an owner or admin adds for the company, are shared with everyone in the business; only the owner and admins can confirm, correct or dismiss them, add or remove contracts, and see where each came from in their data download. Facts EnemoAi learns from your own answers and decisions, and notes you add for yourself, are always private to you, even when you share the answer. Follow-through drafts are private to the person who asked for them. None of it is ever shown to, or used for, another business, and none of it is used to train AI models.
4.4If your business removes you, your sessions end and your name, email address, WorkPair identifiers and photo are removed from its account at once. The questions, answers and decisions you created stay with the business, shown as from a former team member, and stay private unless you had shared them.
5. Who we disclose information to
5.1Service providers (subprocessors). We use the providers listed on our Subprocessors page, under contracts that limit their use of the information to providing their service to us. In summary:
- Anthropic (Claude API, United States) receives your question, earlier turns of that conversation, documents you attach, and the source excerpts we retrieved, to write the answer; when your business has connected its own data, it also receives the facts from that data that bear on the question, and with every question it receives the facts from your business’s knowledge profile that you may see. To write a draft you ask for, it receives the answer the draft follows, that answer’s sources, your business’s data and profile facts, and your instructions for the draft. Under its commercial terms, Anthropic does not train its models on this content. It keeps API inputs and outputs for the period stated in its commercial data-retention policy, and longer where they are flagged for enforcement of its usage policy or where the law requires.
- Hetzner Online hosts our servers and database in Helsinki, Finland.
- Backblaze (United States) stores our encrypted nightly database backups for 30 days. The encryption key is held only by EnemoAi and never given to Backblaze, so Backblaze cannot read them.
- Google (Google Workspace) delivers our emails (alerts, briefings, closure confirmations) and hosts our mailbox.
- Vercel hosts the website at www.enemo.ai and receives the IP address and browser details of each page request.
- Cloudflare provides our domain name service and stores our library of public filings; it does not receive account or question data.
- Apple (Apple Push Notification service) and Google (Firebase Cloud Messaging, for Android) deliver notifications to our apps if you allow them. They receive the device’s push token, a short title (for example, “Your morning briefing is ready”) and a link that opens the app. A notification never contains your questions, answers, documents, the names of companies you watch, figures or any business data; the app fetches those from us once you are signed in.
5.2Link and Stripe. Link, Stripe’s merchant-of-record service, sells wallet top-ups and Monitoring to your business. It receives the email address of the owner who first pays, your business’s legal name, our internal numbers for the business and the person paying, and the payment details you enter, and it uses payment information as its own controller under its privacy policy (for example, for fraud prevention, tax and receipts).
5.3WorkPair. When you sign in, your browser goes to WorkPair, so WorkPair learns that you are signing in to EnemoAi and which organization you chose to share. WorkPair is operated by WorkPair Incorporated, an affiliate of ours under common ownership: Enemo Consulting Group, Inc. and WorkPair Incorporated are both wholly owned subsidiaries of The Ravine of Willows, Inc. They are distinct companies, and nothing is mingled between them. WorkPair handles your WorkPair ID under its own privacy policy. We do not send WorkPair your questions or other content. WorkPair notifies us if your identity proof or consent is withdrawn or your organization membership, standing or profile changes. We also ask WorkPair for your business’s current organization record at each sign-in, when WorkPair tells us it changed, and about once a day; that request names only the organization ID.
5.4Your browser’s speech recognition. If you dictate a question with the microphone button, your browser’s built-in speech recognition turns your voice into text before anything reaches us. Depending on your browser, your voice may be processed by its maker (for example, Google for Chrome or Apple for Safari) under that company’s terms. We receive only the text you submit. Read-aloud audio is generated on our own servers.
5.5Website font. Our app’s pages load a typeface from Google Fonts, so your browser sends your IP address and browser details to Google when those pages load. Google states that requests to Google Fonts are unauthenticated and that no cookies are sent with them. Our legal pages load no third-party resources.
5.6Legal and safety. We may disclose information if we believe in good faith it is required by law or legal process, or necessary to protect the rights, property or safety of EnemoAi, our customers or others. For content belonging to a business, Section 15.7 of the Terms applies: we refer requests to the business and notify it where lawful.
5.7Business transfers. If we are involved in a merger, acquisition, financing or sale of assets, information may transfer to the successor, which must honor this Policy for information collected under it.
5.8No sale or sharing. We do not sell personal information, and we do not share it for cross-context behavioral advertising, as those terms are defined by California and other state laws. We have not done so in the past 12 months. We do not knowingly collect personal information of people under 18.
6. California and other U.S. state privacy rights
6.1The table below describes, for the past 12 months, the categories of personal information we collected, using the categories in the California Consumer Privacy Act as amended (“CCPA”). Sources and purposes are in Sections 2 and 3; recipients are in Section 5. We disclosed each category for business purposes only, to the recipients listed.
| Category | Examples | Disclosed for a business purpose to | Sold or shared |
|---|---|---|---|
| Identifiers | Legal name, email address, WorkPair ID and pairwise identifier, IP address, session identifiers | Hosting, backup, email and website providers; Link and Stripe (the owner who pays only); WorkPair (at sign-in) | No |
| Customer records (Cal. Civ. Code § 1798.80(e)) | Name, email address; payment details are collected by Link, not us | Hosting, backup and email providers; Link and Stripe (the owner who pays only) | No |
| Commercial information | Wallet top-ups, charges, refunds, Monitoring subscription; for businesses that set up before WorkPair sign-in, the employer identification number entered | Hosting and backup providers; Link and Stripe (payments only) | No |
| Internet or other electronic network activity | Questions asked and their Mode, timings, alerts read, sign-in records, server logs, text sent for read-aloud | Hosting and backup providers; Anthropic (question content only, to answer it) | No |
| Audio, electronic or visual information | Optional profile photo (we do not receive your voice) | Hosting and backup providers | No |
| Professional or employment-related information | Your business, its WorkPair standing and profile, your role in it, your WorkPair organization membership | Hosting provider; WorkPair (at sign-in, and the organization ID when we refresh your business’s record) | No |
| Sensitive personal information | We do not ask for any. A question or document may contain sensitive information if you choose to include it | Hosting provider; Anthropic (document content only, to answer) | No |
| Inferences | None. We do not create profiles of individuals | Not applicable | No |
6.2We use sensitive personal information only to provide the service requested, to keep EnemoAi secure, and for other purposes the CCPA permits without a right to limit; we do not use it to infer characteristics about anyone.
6.3Your rights. Depending on where you live, you may have the right to: know what personal information we collect, use and disclose, and receive a copy of it; correct it; delete it; opt out of its sale or sharing, targeted advertising or profiling (we do none of these); limit the use of sensitive personal information (we use it only as Section 6.2 allows); and not be discriminated against for exercising these rights. Some state laws exempt information about people acting for a business; we honor these rights regardless.
6.4Global Privacy Control and similar opt-out signals are honored automatically, because we do not sell or share personal information or use it for targeted advertising.
7. EU, UK and Swiss rights
7.1Where the GDPR, the UK GDPR or the Swiss Federal Act on Data Protection applies to our processing, you have the right to access, rectify and erase your personal data, to restrict or object to processing (including processing based on legitimate interests), to data portability, and to withdraw consent where we rely on it, without affecting earlier processing. You may complain to your data protection authority; we would welcome the chance to address your concern first.
7.2We have not appointed a data protection officer, as our processing does not require one. Because EnemoAi is offered to businesses in the United States and not directed at the EU or the UK, we have not appointed a representative there. Contact us at hello@enemo.ai.
8. People named in public records
8.1EnemoAi exists to inform businesses about businesses. We limit what we keep about individuals: we discard Chapter 13 bankruptcy cases (which are for individuals) as the court feeds are read, and never store them; we store a bankruptcy case or a lawsuit inside one only when name-based rules show the party is plainly a business, discarding cases filed by individuals, personal trusts and estates and replacing an individual on the other side of a lawsuit with “an individual or other party”; we keep only entities, never individuals, from the sanctions list and the export screening lists; from OSHA, Wage and Hour, EPA, FTC, NLRB, NHTSA and federal award records we skip any whose named party is, or plainly contains, a private individual’s name; from the complaint database we keep only counts per company and year; and our Acceptable Use Policy forbids using EnemoAi to watch or research individuals or to make decisions about them.
8.2Some records we keep, such as SEC filings and Justice Department press releases, name individuals as their publishers did. We keep these records as published, as the record of what a public body said, because they are lawfully made available by government and are needed to answer business questions accurately; this is our legitimate interest. EnemoAi is not a consumer reporting agency and does not provide information for decisions about individuals’ eligibility for credit, insurance, employment or housing.
8.3If you are named in a record EnemoAi cites and believe our description of it is inaccurate, or you wish to object, email hello@enemo.ai with the subject “Correction”. See the Monitoring and Public Records Notice.
9. How long we keep information
| Information | How long |
|---|---|
| Uploaded documents | 7 days after upload, or sooner if you remove them; then deleted automatically. Research paused for your approval, which can include a document’s text, is deleted a day after the quote is settled. Passages an answer quotes from your document stay with that answer |
| Business data your business connects (Data API records and documents, imports), and the forecasts and warnings built from it | While your business’s account is open, unless the owner or an admin deletes it sooner (a record, an import with everything it brought in, one data type, or everything); deleted at once when the account closes. Daily cash forecasts are kept 90 days. A Data API request’s idempotency record (which lets a retried request be recognised, and holds that request’s result) is kept 7 days |
| Text sent for read-aloud | Up to 1 day, then deleted automatically |
| Abuse-limit counters | 2 days, then deleted automatically |
| Server logs (with full IP addresses) | 30 days, then deleted automatically |
| Security log | Kept permanently as an append-only record that cannot be edited or deleted. It contains who did what and when, with a shortened network address, and never question content |
| Reports to us | The report’s free-text description is deleted one year after the report (or when the business closes its account, if sooner). The date, category, and who made it and who it concerned stay in our report records, which only EnemoAi staff can see. The email that tells our staff a report arrived names no one and copies nothing |
| Bans | While the ban is in force, then one year after it is lifted, then deleted automatically |
| Invitations | Unused invitations are deleted 30 days after they expire or are withdrawn; an accepted invitation stops naming anyone 30 days after it is accepted |
| Quotes you approve, decline or let expire | The question’s text is deleted 30 days after the quote ends; its price and status stay with the wallet ledger |
| People removed from a business | De-identified when removed: name, email address, WorkPair identifiers and photo are deleted. What they created stays with the business until its account closes; anything they had not shared stays private and unread. The business can ask us to delete it sooner |
| Email-change requests; checkout sessions; WorkPair notices | Email-change requests 30 days after they lapse; records of checkout sessions 30 days after they start; WorkPair notice identifiers after 90 days; all deleted automatically |
| A closed business’s name and owner contact | Kept 120 days after closure (money can still arrive or be returned in that time), and for as long as a refund we owe the business is unpaid, then deleted automatically. Refunds we owe are recorded with the business’s legal name and owner contact until paid or reported as unclaimed property where the law requires, then kept with our accounting records for 7 years and deleted automatically |
| Sessions | Until you sign out or after 30 days; expired session records are deleted automatically. An app’s sign-in lasts 30 days from its last use |
| Push tokens | Until you sign out of that app, sign out everywhere, remove the device or turn notifications off in the app, or Apple or Google tell us the token is no longer valid; then deleted at once. One-time app sign-in codes expire after 5 minutes and are deleted within a day. Apple TV sign-in codes expire after 10 minutes and are deleted within a day |
| WorkPair sign-in steps | Expire after 10 minutes; deleted within a day |
| Account, profile and WorkPair information; questions, answers, quotes, decisions, documents, watchlist, alerts, invitations, preferences, Data API keys and connected business data; contracts kept with EnemoAi, the knowledge profile and follow-through drafts | While your business’s account is open. When the owner closes it, the content is deleted at once and every person is de-identified: names, email addresses, WorkPair identifiers, photos and preferences are deleted, and the user record that remains (because the wallet ledger and security log point to it) says only “former team member”. The business record keeps only its creation and closing dates, its Monitoring status and the Stripe customer number for its payment records |
| A closed business’s WorkPair organization ID | Kept with only whether it used the Free Month and a Monitoring trial, so those promotions are not given twice. The organization can sign up again |
| Database backups | Encrypted nightly backups are kept 30 days and then permanently deleted, so deleted information leaves the backups within 30 days |
| Wallet ledger and billing records | Kept as our accounting record for at least 7 years after each transaction, for tax and accounting. After an account closes, the ledger holds only amounts, dates, kinds of entry and payment references, linked to the de-identified records; never question text |
| Legal acceptance records | While the account is open and for 4 years after it closes, as evidence of the agreement, then deleted automatically |
| Emails we send and receive | Our email provider keeps copies of sent and received messages (including alerts, briefings and closure confirmations) in our mailbox while we need them for support and records; closing an account does not delete them |
| What EnemoAi learned from a source | Goes with its source: removing a contract deletes what EnemoAi read from it at once; deleting your business’s data deletes what EnemoAi learned from it at once; a deleted answer or decision takes what EnemoAi learned from it at the next update (within minutes). You can delete a note you added at any time, and a draft at any time. A draft price that was declined, lapsed or never written is deleted after 30 days |
| Public records | Kept permanently, as published, as part of EnemoAi’s source library |
| Anonymous decision dataset contributions, and consent records | A contribution is kept while both consents stand; it is deleted at once when you stop contributing, your business stops allowing it, you are removed from the business or the business closes (and leaves the backups within 30 days). Consent records (the wording you agreed to, when, and when you withdrew) are kept while the account is open, then deleted with it |
An individual can ask us to delete their own information sooner (Section 11). If we must keep information longer because of a legal obligation or claim, we keep only what is needed, for as long as needed.
10. Where information is processed, and international transfers
10.1Our servers and database are hosted by Hetzner Online in Helsinki, Finland, in the European Union. Encrypted backups are stored with Backblaze in the United States. EnemoAi is a U.S. company, and some of our providers, including Anthropic, Stripe and Link, Google, Vercel and, for app notifications, Apple, process information in the United States and elsewhere.
10.2Where the GDPR, UK GDPR or Swiss law requires a transfer mechanism for personal data sent to a country without an adequacy decision, we rely on the European Commission’s Standard Contractual Clauses (with the UK Addendum and Swiss amendments as applicable), included in our contracts with providers and in our Data Processing Addendum, or on a provider’s certification under the EU–U.S. Data Privacy Framework and its UK and Swiss extensions where the provider holds one. You may ask us for a copy of the relevant safeguards.
11. Your choices and how to exercise your rights
11.1In the app. You can delete uploaded documents, remove your photo, change email and push notification preferences or unsubscribe from alert and briefing emails, see where you are signed in and sign out any device, choose whether to share answers, and download your data: your profile, your answers and those shared with you, your decisions, the watchlist, your document list and your legal acceptances; the owner and admins also receive the company profile, wallet history, security log and the business data your business connected (with its keys’ names and scopes, never the keys). The owner and admins can delete connected business data, and revoke Data API keys, at any time. The owner can close the business’s account. Your name and email come from WorkPair; change them there and they update the next time you sign in.
11.1aDecision dataset. Contributing your reviewed decisions is off unless your business’s owner or an admin allows it and you opt in. You can stop at any time; stopping deletes every record you contributed. If your business stops allowing it, every record it contributed is deleted and each person must opt in again if it is turned back on.
11.2By request. Email hello@enemo.ai with the subject “Privacy request”, saying what you want. We verify requests by asking you to write from, or confirm through, the email address on your account, or to sign in with WorkPair. An authorized agent may act for you with your signed permission; we may ask you to confirm your identity directly.
11.3Timing. We respond within 45 days (or one month where the GDPR applies), and tell you if we need longer as the law allows. Requests are free, unless they are manifestly unfounded or excessive.
11.4What deletion means. Deleting your account information means we de-identify your user record (content you created is handled under Section 11.5): your name, email address, WorkPair identifiers, photo and preferences are deleted, and the record itself remains, labelled “former team member”, because the wallet ledger and the security log point to it. The security log entries remain too; they hold no content.
11.5Content that belongs to your business. Your questions and answers belong to your business. If you ask us to delete them, we will, and we may tell your business’s owner that we did so without revealing their content. Requests about another person’s content, or about the business’s data generally, are handled with the business under our Data Processing Addendum.
11.6Appeals. If we decline a request, you may appeal by replying with the subject “Appeal”. We will respond within 45 days (60 days where state law allows). If you are still not satisfied, you may contact your state attorney general.
12. Security
12.1We protect information with measures that include: encryption in transit (HTTPS) between your browser, our servers and our providers; row-level security in the database on the tables that hold each business’s content, wallet, watchlist, invitations, acceptances, security log, connected business data and Data API keys, and a further database rule that keeps each person’s questions, quotes, answers, documents and decisions private to them (account and sign-in records, and a small number of system operations such as sign-in, payments and monitoring, run outside these rules); sign-in only through WorkPair with signed identity proofs, with a fresh WorkPair sign-in required for sensitive actions; sessions that end when WorkPair or you sign out; an append-only security log; abuse limits per person, per business and per network; session tokens stored only as cryptographic hashes in secure, HTTP-only cookies, and app sign-in tokens likewise stored on our side only as cryptographic hashes; protections against cross-site request forgery; an application database login that cannot bypass those privacy rules (our deployment refuses to proceed otherwise); encrypted nightly backups kept for 30 days; and payment details handled only by Link and Stripe. We do not claim encryption of data stored on our servers’ disks. Our Security page and the security annex to our Data Processing Addendum describe our controls.
12.2No system is perfectly secure. If a breach affects your personal information, we will notify you and authorities as the law requires.
13. Children
EnemoAi is for businesses and is not directed to anyone under 18. Authorized Users must be 18 or older and identity-verified on WorkPair. We do not knowingly collect personal information from anyone under 18; if we learn we have, we delete it.
14. Changes to this Policy
We will post any change here with a new version and effective date. If a change materially affects how we handle personal information already collected, we will notify account owners by email and in the app before it takes effect and, where the law requires, ask for consent. The app asks Authorized Users to acknowledge a new version.
15. Contact and version history
Enemo Consulting Group, Inc., Attn: Privacy, 1412 Main St STE 609, Dallas, TX 75202, United States · hello@enemo.ai (subject “Privacy”).
- 2026-11-01: first version.
- 2026-11-01.3: business data a business connects through the Data API or imports: what we collect and refuse, who in the business sees it, how long it is kept, and that it is never used for training or for another business; the full list of public sources EnemoAi reads (Section 2).
- 2026-11-01.4: our apps: app sign-in records and push tokens (Section 2), push notifications and the services that deliver them (Sections 3 and 5), how long they are kept (Section 9), and no analytics or tracking software in the apps.
- 2026-11-01.5: signing in on Apple TV with a code approved on another device: what we keep while a TV waits and how long (Sections 2 and 9); abuse limits per network (Section 12).
- 2026-11-01.6: the decision dataset: with your business’s and your consent, anonymous records of the decisions you log and review help every business (Summary, Sections 3, 9 and 11).
- 2026-11-01.7: what EnemoAi knows about your business (its knowledge profile, built from your business’s data, its contracts, your decisions and earlier answers, and what you tell it), contracts EnemoAi reads, and follow-through drafts: what is kept, who in the business sees it, what Anthropic receives, and how long it is kept (Sections 2, 3, 4, 5 and 9).

