DRAFT. Not legal advice. For review by counsel before public launch.
This Privacy Policy explains how Telonyte LLC ("Telonyte," "we," "us") handles information in connection with B.R.A.I.N. (Bot Recall Artificial Intelligence Network), our hosted shared-memory service for software agents, its website, dashboard, client software, and support (the "Service"). It should be read with the Terms of Service.
Summary
- B.R.A.I.N. stores the notes your bots send it and returns matching notes when your bots ask. It is recall-only: it returns what is stored and does not guess or fill gaps.
- The hosted add and find steps do not send your notes to any third-party AI model.
- We do not use your notes to train AI models, and we do not sell personal information.
- Each team's memory is kept separate. Other teams cannot see yours.
- Google Drive is optional. If you connect it, we read only the files you pick and keep extracted text, not the original files.
- Payments go through Stripe. We do not store full card numbers.
- You can download an export of your team's data or delete your team from the dashboard, or ask us through the Contact us form.
Two roles: your account and your bots' notes
Account and website information. For information about you as a customer, dashboard user, or website visitor (such as your email and billing details), Telonyte decides how it is used and is responsible for it (a "controller" under laws such as the GDPR).
Customer Data (your bots' notes). For the notes and other content your bots store in B.R.A.I.N., you (the customer) decide what goes in and why. Telonyte processes that content on your behalf to provide the Service (a "processor" or "service provider"). If a note contains personal information about someone else, such as one of your own users, that person should contact you first; we will help you respond to their request.
Information we collect
- Account information: team name, contact email, the plan you choose, number of active bots, bot names or labels you set, and dashboard sign-in identifiers (such as your email for a sign-in link, or your Google account identifier if you sign in with Google where offered).
- Billing information: Stripe customer and subscription identifiers, plan, invoice and payment status, and billing contact details. Card details are collected and processed by Stripe; Telonyte does not receive or store full card numbers.
- Customer Data: the notes, tags, timestamps, and bot names your bots submit, related index data used to find notes, and the history kept when a newer note replaces an older one. If your bot sends an optional end-user identifier ("user" or "user_id") with a note, we store it with that note and use it only to narrow lookups that pass the same identifier; it is not a separate access control, and any bot key on your team can still read all of the team's notes.
- Google Drive content (optional): if you connect Google Drive, the names and identifiers of the files and folders you pick, the extracted text of supported files, and the access tokens Google issues so the Service can read those files.
- Technical and usage information: API request metadata such as timestamps, response times, error codes, client version, active-bot activity (last seen), and IP address and other network metadata handled by our hosting provider, used for security, reliability, abuse prevention, and billing. We redact keys and sign-in tokens from logs.
- Support communications: what you send us through the Contact us form, a support ticket or the help chat.
We do not ask for, and our Terms prohibit storing, passwords, payment card numbers, government ID numbers, or other secrets in B.R.A.I.N.
How we use information
- To provide the Service: store your bots' notes, find and return matching notes, run the dashboard, and keep each team's memory separate.
- To create and manage your team, install links, and bot keys.
- To bill your plan through Stripe once billing is open, and to send receipts, payment reminders, and suspension or restoration notices.
- To secure the Service: detect and prevent abuse, fraud, and unauthorized access, and enforce our Terms.
- To operate and improve reliability and performance, using technical and usage information (not the text of your notes).
- To respond to support requests and send important service notices, such as changes to the Terms or this policy.
- To comply with law and respond to lawful requests.
What we do not do. We do not use Customer Data to train or fine-tune AI or machine-learning models. We do not sell or rent personal information, and we do not share it for cross-context behavioral advertising. We do not read the content of your notes except as needed to provide the Service, to fix a problem you report, to investigate abuse or a security issue, or where required by law.
Legal bases (EEA/UK visitors). Where the GDPR or UK GDPR applies, we rely on: performance of our contract with you (providing the Service and billing); our legitimate interests (securing, operating, and improving the Service, and communicating with customers), balanced against your rights; compliance with legal obligations (tax and accounting records); and your consent where we ask for it (such as connecting Google Drive), which you may withdraw at any time.
Google Drive (optional)
If you connect Google Drive:
- We request only Google's per-file access (the "drive.file" scope). We can read only the files and folders you pick in Google's file picker, not the rest of your Drive.
- We import supported files (such as Google Docs, plain text, Markdown, and text-based PDF and Word files) as extracted text into your team's memory. Original files stay in Google Drive; we do not store copies of the original files.
- We skip files whose names look like credentials, scanned files without text, and very large files.
- We use Drive data only to provide the import feature you asked for. We do not use it for advertising, do not sell it, do not use it to train AI models, and do not let people read it except as described in "How we use information."
- You can stop future imports at any time by removing B.R.A.I.N.'s access in your Google Account settings. Text already imported stays in your team's memory until you delete it or ask us to.
Telonyte's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
How we share information
We share information only as described here.
Service providers (subprocessors). These companies help us run the Service under contracts that limit their use of the data to providing services to us:
- Cloudflare, Inc. (United States and Cloudflare's global network): hosting, storage, networking, and security for the Service, the website, and the dashboard. Customer Data is stored on Cloudflare.
- Stripe, Inc. (United States): payment processing and billing, once billing is open.
- Google LLC (United States): optional Google Drive import and optional Google sign-in, only if you use them.
- An email delivery provider for sign-in links and service and billing notices. [To be named before launch.]
We will update this list before adding a new subprocessor that processes Customer Data. [Counsel to decide whether to commit to advance notice, such as thirty days, and a way to object.]
Other sharing:
- Legal and safety: when we believe in good faith that disclosure is required by law, subpoena, or court order, or is necessary to protect the rights, safety, or property of Telonyte, our customers, or others, including to prevent fraud or abuse. Where lawful, we will tell you before disclosing Customer Data in response to a legal demand.
- Business transfers: if Telonyte is involved in a merger, acquisition, financing, or sale of assets, information may be transferred as part of that transaction, subject to this policy.
- With your direction: when you ask us to share information, for example by connecting a service.
Retention and deletion
- Customer Data is kept while your team is active. When a newer note replaces an older one, the older note may be kept in your team's history so it can still be found for past questions. Routine housekeeping moves older working notes to longer-term memory, where they can still be found; it does not erase them. Your bots can delete individual notes through the API. The signed-in team owner can download an export (notes, history, and facts) or delete the whole team from the dashboard, and you can ask us at any time to delete specific notes or all of your team's data.
- After termination, we keep your Customer Data for thirty (30) days so you can request an export, then delete it.
- Deletion requests. Deleting a team from the dashboard asks for confirmation, takes effect immediately in the live Service, and cannot be undone; a team with an active paid subscription must cancel it first. Requests sent to support are completed within thirty (30) days, or we will tell you if we need longer and why. Deleted data may remain in backups or logs for a limited period until it is overwritten. [Backup retention period to be confirmed before launch.]
- Google Drive tokens are encrypted at rest and kept until you disconnect or your team is deleted. Imported Drive text follows the Customer Data rules above.
- Billing records are kept as long as tax and accounting law requires.
- Technical logs are kept for a limited period for security and troubleshooting. [Period to be confirmed before launch.]
- Support emails are kept as long as needed to handle your request and keep a record of it.
Security
We use measures designed to protect information, including: separate storage for each team's memory; encrypted connections (HTTPS) between your bots and the Service; per-bot keys that you can revoke or pause; API keys stored only as one-way hashes, so a key is shown once when it is issued, cannot be retrieved later, and is replaced with a new key if lost; Google Drive tokens encrypted at rest (AES-256-GCM) with a key kept outside the database; redaction of keys and tokens from logs; signed client updates; and screening that skips content that looks like a credential. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
The B.R.A.I.N. client may keep a short-lived local cache on the machine where your bot runs so lookups keep working briefly offline. That cache is encrypted with a key that is also stored on that machine, so it is only lightly protected and is not a substitute for securing the machine; treat the machine itself as holding your team's notes.
If we confirm a security incident affecting your Customer Data or personal information, we will notify affected customers without undue delay and, where required, regulators or individuals within the time the law requires.
Your rights and choices
Depending on where you live, you may have the right to: know what personal information we hold about you and get a copy; correct it; delete it; receive it in a portable format; object to or restrict certain processing; withdraw consent; and not be discriminated against for exercising these rights.
To make a request, use the Contact us form. We may need to verify your identity (for example, by replying from your team's contact email). An authorized agent may make a request for you with proof of authorization. We will respond within the time the law requires, generally within thirty (30) days (forty-five (45) days for requests under U.S. state privacy laws, which we may extend where the law allows). If we decline a request, we will explain why, and where the law provides an appeal, you may appeal by replying to our decision.
California and other U.S. states. In the past twelve months, the categories of personal information we have collected are identifiers (such as name, email, and IP address), commercial information (plan and billing records), internet or network activity (API and dashboard usage), and any personal information contained in Customer Data. We collect them from you, your bots, your connected services, and our service providers, for the business purposes in "How we use information," and disclose them to the service providers listed above. We do not sell or share personal information as those terms are defined in California law, and we do not use sensitive personal information to infer characteristics about anyone.
EEA and UK. If you are in the European Economic Area or the United Kingdom, you may also lodge a complaint with your local data protection authority. [Counsel to decide whether an EU/UK representative is needed before offering the Service in those regions.]
Customer Data about others. If you are an end user of one of our customers and want to exercise rights over information a customer's bot stored about you, please contact that customer. If you contact us, we will forward your request or help the customer respond.
International transfers
Telonyte is based in the United States, and our service providers may process information in the United States and other countries where they operate, including through Cloudflare's global network. Those countries may have different data protection laws than where you live. Where required, we will use appropriate safeguards for transfers, such as standard contractual clauses. [Counsel to confirm transfer mechanism before offering the Service in the EEA or UK.]
Cookies
The dashboard uses cookies or similar storage that are necessary to keep you signed in and to secure your session. We do not use advertising cookies. [If analytics are added to the website before launch, this section and any cookie notice must be updated first.]
Children
The Service is for businesses and developers. It is not directed to children, and you must be at least 18 years old to create a team. We do not knowingly collect personal information from children under 16 [counsel to confirm the age threshold]. If you believe a child has given us personal information, contact us through the Contact us form and we will delete it.
Changes to this policy
We may update this policy. If we make material changes, we will notify customers by email or in the dashboard before the changes take effect, and update the date at the top of this page.
Contact
Telonyte LLC · the Contact us form on our Support page