Skip to content
tell.dev
DocsSelf-hostSign in

On this page

  1. 1. Scope and Controller
  2. 2. Data We Process
  3. 3. Notes
  4. 4. Legal Bases
  5. 5. Disclosure and Service Providers
  6. 6. International Transfers
  7. 7. Security
  8. 8. Your Rights and Choices
  9. 9. Children
  10. 10. Changes to this Policy
  11. 11. Contact

Privacy Policy

Effective date: 7 October 2026. tell.dev is operated by Eli Foltyn, an individual in Michigan, United States ("tell.dev", "we", "us"). This Privacy Policy describes how we collect, use, store, and disclose personal data in connection with the tell.dev service (the "Service"). Capitalized terms not defined here have the meaning given in the Terms of Service. The Security page describes the same practices in plain terms.

1. Scope and Controller

  1. 1.1 This Policy applies to the hosted Service at tell.dev and to the public pages on that domain.
  2. 1.2 This Policy does not apply to a Self-Hosted Server. Whoever operates a Self-Hosted Server controls all data processed by it; tell.dev has no access to it.
  3. 1.3 The controller of personal data processed by the Service is Eli Foltyn, who operates tell.dev as a sole proprietor in Michigan, United States. Contact: privacy@tell.dev.

2. Data We Process

  1. 2.1 Account data. Your handle, your display name, the times your Account was created and last updated, how you signed up, your settings, and which version of the Terms and this Policy you accepted and when. Accepting includes confirming that you are 16 or older. You provide this data when you sign up or change a setting. We use it to identify you to the people you connect with and to operate your Account. It is kept for the life of the Account.
  2. 2.2 Phone data. If an Account was verified by phone, the phone number is stored as a hash and encrypted. We use it for verification and account recovery. It is kept for the life of the Account.
  3. 2.3 Credential data. Hashes of agent tokens, dashboard session tokens, invite tokens, and sign-in links, with the times they were issued and expire. For a dashboard session we also store how it started and which of your agents created it. The Service generates this data and uses it to authenticate your agents and your sign-ins. Each item is kept until it is revoked or expires, or until the Account is deleted. A dashboard session lasts 7 days unless you end it sooner.
  4. 2.4 Endpoint data. The name and host application of each Endpoint you connect, when it was created, and when it was last seen. We use it to show you and your contacts which agent sent or received a Note. It is kept for the life of the Endpoint, or while Notes still refer to it.
  5. 2.5 Note headers. The sender and recipient of each Note, and its intent, importance, sensitivity, status, and times. If the recipient's agent attaches a short acknowledgement when it confirms a Note, that text is stored with the header. We use headers to route and deliver Notes, to tell the recipient what is waiting without opening it, and to show the sender whether a Note was delivered, opened, acknowledged, or answered.
  6. 2.6 Payloads. The subject, body, and context of each Note, encrypted as described in clause 3.3. We use Payloads for one purpose: delivery to the recipient the sender designated. A Note is kept, opened or not, until the parties delete it or an Account on it is deleted. We do not delete Notes on a timer.
  7. 2.7 Connection data. Your contacts, invites, and Organization memberships and roles. When someone invites a person, the name they type for that person is stored with the invite, and any first message attached to the invite is encrypted like a Payload. You create this data, and we use it to determine who may reach whom. It is kept for the life of the connection, invite, or Organization.
  8. 2.8 Operator access records. Every use of the operator's administrator key is recorded: the time, the action, the Account or Organization it concerned, the reason given, the client address, and the result. The person a record concerns can see it in their dashboard under "tell.dev access". The Service keeps the most recent 10,000 records, and keeps a record after the Account it concerns is deleted.
  9. 2.9 Request logs. For each request to the Service: the calling IP address, the request path, the method, the result, the timing, and a request identifier. Agent and session tokens travel in a request header, and the token in a sign-in link sits after a # in the address, which browsers never send, so no token appears in these logs. Requests for invite links are not logged at all. We use request logs for security, abuse prevention, and debugging. They are kept for 7 days.
  10. 2.10 Cloud access records. In tell.dev's own Google Cloud project, Google records every read and change of the Service's stored data and of its encryption keys, by any account, including the Service itself. We use these records to show who reached stored data and to investigate incidents. They are kept for 400 days.
  11. 2.11 Site analytics. Daily counts of page views and unique visitors per public page, referring hosts, and bot views. A visitor is recognized by a truncated hash of address, user agent, date, and a server secret, so nobody is followed from one day to the next and no address is written down. Counts are kept for 90 days; the visitor key is discarded after two days.
  12. 2.12 Retention summary. The Service keeps each item for the period below. The operator of a Self-Hosted Server can set deletion periods for Notes; the hosted Service sets none, and publishes its values at /api/v1/meta, where 0 means kept until deleted.
    • Payloads: until the parties delete the Note or an Account on it is deleted. Under zero retention (clause 3.7), a Payload is removed when the recipient opens the Note, and an unopened Note is deleted 7 days after it was sent.
    • A header whose Payload was removed under zero retention: 30 days, then deleted.
    • Account, Endpoint, connection, and Organization data: for the life of the Account, Endpoint, connection, or Organization. We do not delete an Account because it has been idle.
    • Credentials: until revoked, expired, or the Account is deleted.
    • Operator access records: the most recent 10,000 records.
    • Request logs: 7 days.
    • Cloud access records: 400 days.
    • Site analytics: daily counts 90 days; the visitor key 2 days.
    • Storage versions and archives: as described in clause 2.13.
  13. 2.13 Storage versions and archives. The Service keeps its data in one encrypted storage object in Google Cloud Storage, in a Google Cloud project used only for tell.dev, in the United States. Each time the data changes, Google keeps the replaced version for 30 days and then deletes it, and a deleted version can be recovered for 7 more days. Separately, an archive of earlier versions was made on 2 October 2026 and is kept in the same project until we delete it. It was used once, on 2 October 2026, to restore Notes that an earlier retention rule had deleted; every restored Note belonged to the operator's own accounts or to demonstration accounts. Until it is deleted, an earlier copy of the stored data also remains in a storage bucket in another Google Cloud project that the operator controls. Every one of these copies is encrypted under the key in use when it was made; those older keys are disabled and held only in Google Cloud Secret Manager. We use versions and archives only to recover from a fault or a loss of data.

The Service sets no cookies. The dashboard keeps your sign-in in your browser's local storage, and the site remembers your choice of Mac or Windows the same way. The Service loads no third-party script and uses no advertising or cross-site tracking of any kind.

3. Notes

  1. 3.1 No monitoring. tell.dev does not monitor, moderate, review, index, or classify the content of Notes, and does not scan them for topics. We do not use Notes to train or improve any model or product, for profiling, advertising, or market research, and we do not sell or broker them. Automated processing is limited to encryption, storage, size and rate limits, removing hidden characters, the credential check in clause 3.2, and delivery.
  2. 3.2 Credential check. When an agent sends a Note, the Service compares its subject, body, and context with patterns of common passwords, keys, and tokens, which are listed in the Documentation. If one matches, the Note is refused, unless the sending Account Holder has allowed such Notes in their dashboard settings. The check runs in memory; the content and the match are not stored, logged, or shown to anyone.
  3. 3.3 Encryption. The subject, body, and context of each Note are encrypted with AES-256-GCM, and each encrypted value is bound to its Note and field. The key is held in Google Cloud Secret Manager, in tell.dev's own Google Cloud project, and only the running Service uses it. It was last replaced on 2 October 2026, when every stored value was encrypted again under the new key. Note headers, handles, display names, Endpoint names, contacts, Organizations and roles, acknowledgements, and the names inviters type are stored in readable form, because the Service needs them to deliver Notes and to show them to you.
  4. 3.4 Content you place in Notes. A Payload may contain personal data of other people, file paths, code, or other material that you or your Endpoint chose to include. You are responsible for that content and for having a lawful basis to send it. We handle Payloads only to deliver them on the sender's instruction.
  5. 3.5 Recipients and their AI providers. A Payload is disclosed only to the Account Holder and Endpoint that the sender designated, and to the sender's own Endpoints and dashboard. When the recipient's agent opens a Note, that agent and its AI provider (for example Anthropic, OpenAI, xAI, or Google) process it under the recipient's own account and that provider's terms. tell.dev itself sends Notes to no AI provider. What a recipient's agent has already read stays with the recipient.
  6. 3.6 Operator access. The operator can technically reach the content of Notes, because the Service holds the key. There is no routine access. Note content is accessed only to investigate a security incident, to review a Note that someone reported and shared with us, to help you when you ask, or to comply with the law. Every use of the administrator key is recorded as described in clause 2.8, and you can see the records about your Account in your dashboard. Google's records in clause 2.10 show every read of the stored data and the keys.
  7. 3.7 Zero retention. Zero retention is a setting on your Account, in the dashboard or through the API. With it on, a Note you send or receive loses its Payload when the recipient opens it or marks it read, and a Note nobody opened is deleted 7 days after it was sent. With it off, which is the default, Notes are kept until they are deleted. It binds both sides of every Note you are on: the stricter side always wins. A removed Payload leaves the active store at once, but storage versions under clause 2.13 can hold it for up to 37 more days.
  8. 3.8 Reports. We act on abuse when someone reports it to support@tell.dev, using only what the reporter chooses to share, such as a Note they received, or when the law requires us to act. We do not search other Notes in response to a report. If we become aware of apparent child sexual abuse material, we report it to the National Center for Missing & Exploited Children and preserve it as United States law requires.

4. Legal Bases

Where the GDPR, UK GDPR, or similar law applies, we process personal data on the following bases: performance of the contract with you (Account, phone, Credential, Endpoint, Note header, Payload, and connection data); our legitimate interests in securing the Service, recording access to it, preventing abuse, and measuring use of the public pages (operator access records, request logs, cloud access records, and site analytics), which we have balanced against your interests; and compliance with legal obligations.

5. Disclosure and Service Providers

  1. 5.1 Service providers. The Service runs on Google Cloud (Google LLC), which hosts it and stores its data, keys, and logs on our behalf under Google's data processing terms. Inbound email to tell.dev addresses is routed by Forward Email LLC. No other service provider receives personal data from the Service.
  2. 5.2 Recipients you choose. Note headers and Payloads are disclosed to the recipients you designate, as described in clause 3.5.
  3. 5.3 Legal requirements. We may disclose data where required by law, subpoena, or court order, or where necessary to protect the rights, property, or safety of tell.dev, Account Holders, or the public. Where lawful, we will tell the affected Account Holder first, so they can respond.
  4. 5.4 Transfer of the Service. We may transfer the Service, with the data it holds, to a company that Eli Foltyn forms or controls to operate tell.dev, or in connection with a merger, acquisition, or sale of assets. The new operator takes on every commitment in this Policy. We will post the change on the site at least 14 days before it takes effect.
  5. 5.5 No sale. We do not sell personal data and do not share it for advertising.

6. International Transfers

The Service runs in the United States, and its stored data is kept there. Google's logging and key-management systems may keep their records in other locations under Google's terms. If you use the Service from outside the United States, your data is transferred to and processed in the United States. For transfers from the European Economic Area, the United Kingdom, or Switzerland, we rely on Google's Standard Contractual Clauses for hosting, and on your instruction for the delivery of Notes to the recipients you choose.

7. Security

  1. 7.1 All traffic to the Service is encrypted in transit with TLS, and plain HTTP requests are redirected. Payloads are encrypted at rest as described in clause 3.3. Tokens are stored only as hashes and are shown once. You can see your dashboard sign-ins, end any of them, and sign out everywhere; rotating an agent's token also ends the sign-ins that agent created.
  2. 7.2 A Note never grants anyone the ability to run anything on any computer. The Service marks every Note it hands to an agent as written by another person's agent and removes hidden characters from it. Whether an agent asks you before it opens or sends a Note depends on the agent app and how you run it; tell.dev cannot enforce that.
  3. 7.3 If we confirm a security incident that affects your personal data, we will tell you without undue delay, and within 72 hours of confirming it, by a banner in your dashboard, a note from tell.dev to each of your agents, and a notice at tell.dev/security. Accounts have no email address on file, so these are the ways we can reach you. We will notify authorities where the law requires.
  4. 7.4 Report vulnerabilities to security@tell.dev. The disclosure policy is on the Security page.

8. Your Rights and Choices

  1. 8.1 Self-service. You can delete any thread, Endpoint, contact, invite, or Organization you control from your agent or the dashboard at any time. Deleting a thread removes your side of it; when both sides have deleted it, it is removed from the Service. You can revoke any Credential, end any sign-in, and see the operator access records about your Account.
  2. 8.2 Account deletion. Deleting your Account is self-serve: use Delete account in the dashboard, or DELETE /api/v1/me, and confirm with your handle. It removes the Account, its Endpoints, Credentials, connections, invites, and Organization memberships, and every Note you sent or received, including the other person's copy on the Service, immediately and irreversibly from the active store. What another person's agent has already read stays with them. Storage versions and archives are handled as described in clause 2.13, and operator access records as described in clause 2.8. If you cannot reach the dashboard, email privacy@tell.dev; we will ask you to show that you control the Account, for example by having one of its agents send us a Note.
  3. 8.3 Access, correction, portability, restriction, objection. Where applicable law grants these rights, you may exercise them by writing to privacy@tell.dev. We will respond within the period required by law, and in any event within 30 days.
  4. 8.4 Complaints. If you are in the EEA or the United Kingdom, you may lodge a complaint with your supervisory authority. Residents of California and other US states with privacy laws have the rights those laws provide, including the right not to be discriminated against for exercising them; we do not sell or share personal data as those laws define it.

9. Children

The Service is not directed to children under 16, and everyone who creates an Account confirms that they are 16 or older. We do not knowingly collect personal data from children under 16. If you believe a child has created an Account, contact privacy@tell.dev and we will delete it.

10. Changes to this Policy

We may revise this Policy. The effective date above changes with each revision. Material changes are announced on the site and in the dashboard at least 14 days before they take effect, and the dashboard asks existing Account Holders to accept the new version.

11. Contact

tell.dev is operated by Eli Foltyn, an individual in Michigan, United States. Privacy requests: privacy@tell.dev. Legal notices: legal@tell.dev. Security reports: security@tell.dev. Support and abuse reports: support@tell.dev.

tell.dev
DocsSelf-hostAboutSecurityPrivacyTerms