Privacy Policy
Version 2026-10-01 · Effective 1 October 2026
This policy explains what Telos-IQ ("we", "us") collects when you use Telos-IQ ("the Service"), why, and what we do with it. It is written for the businesses that use the Service and for the people whose information passes through it.
Telos-IQ is a business-to-business tool. We act as a service provider (processor) for the data our customers bring into their workspaces, and as a controller for the account and billing information we need to run the Service.
1. What we collect
Account information (we are the controller).
- Company name, the owner's work email address, and the email addresses and roles of users the owner invites.
- Sign-in security data: a salted password hash, multi-factor authentication secrets, passkey public keys, and sign-in and audit events (time, IP address, action).
- The record of your acceptance of our Terms: the version accepted, the time, the account email and the IP address it came from.
- Billing information: your subscription status and Stripe customer and subscription identifiers. We never see or store card numbers. Payment details are collected and held by Stripe under its own privacy policy.
- Support correspondence and anything you post on the shared suggestions board, under the handle you choose.
Workspace data (we are the processor; you are the controller).
- Credentials, API keys and delegated tokens you supply for the tools you connect.
- Data read from those tools to produce coverage reports: device names, operating systems, last-seen times, last signed-in user names, site or client names, agent status, license assignments, administrator roles and multi-factor registration status, and similar operational data. This can include names and email addresses of your clients' users.
- Settings you create: client lists, tool mappings, exceptions, report preferences and branding.
Technical data. Standard server logs (IP address, user agent, requested URL, time) kept for security and troubleshooting.
We do not use tracking cookies or third-party analytics in the Service. The only cookies are those needed to keep you signed in and to protect forms against forgery.
2. How we use it
- To provide the Service: read connected tools, produce reports, send the emails you request (invitations, password resets, alerts).
- To secure the Service: detect abuse, investigate incidents, keep audit trails.
- To bill you and communicate about your account, including required notices such as changes to terms.
- To improve the Service using aggregated, de-identified usage information that does not identify a customer or a person.
We do not sell personal information, use Customer Data for advertising, or use Customer Data to train machine-learning models.
3. Where it lives and who can see it
- Each customer's workspace runs in its own isolated environment on Amazon Web Services in the United States. Workspace data is stored in per-workspace storage encrypted at rest. Data in transit is encrypted with TLS.
- Tool credentials are stored in an encrypted secrets store and are readable only by the workspace they belong to. Our operators cannot read them.
- Our operators can see account information, workspace health, and billing status. They can view the inside of a workspace only through a time-limited, audited support session that is recorded in your workspace's audit log.
4. Sharing
We share information only with the service providers we need to run the Service (our "subprocessors"), each under contract terms that restrict their use of it:
| Provider | Purpose | Location |
|---|---|---|
| Amazon Web Services | Hosting, storage, encryption key management, email delivery (SES) | United States |
| Stripe | Payment processing and subscription billing | United States |
| Microsoft (Microsoft 365) | Transactional email delivery where enabled | United States |
The tools you connect (your RMM, security, backup and identity products) receive requests from your workspace using the access you granted. We do not send your data to them beyond what is needed to make those requests.
We may disclose information if required by law, to protect the rights, safety or property of us, our customers or others, or as part of a merger or acquisition, in which case this policy continues to apply.
5. Retention
- Workspace data is kept for as long as your workspace exists. Reports are rebuilt from connected tools regularly and earlier snapshots are kept for a short rolling period for recovery.
- When a workspace is closed we delete its data, credentials and storage within 30 days. Encrypted backups age out within 35 days after that.
- Account and billing records are kept for as long as necessary to meet tax, accounting and legal obligations, typically seven years.
- Infrastructure and server logs are kept for between 30 days and 13 months depending on the log. The audit log inside your workspace is kept for the life of the workspace.
6. Your rights and choices
Depending on where you are, you may have rights to access, correct, delete, restrict or port personal information, and to object to certain processing. Because most personal information in the Service belongs to our customers' workspaces, we will usually refer an individual's request to the relevant customer and help them respond.
Workspace owners can export reports, delete users, disconnect tools and close the workspace from within the Service, and can ask us for a copy of their workspace data. For anything else, email support@telos-iq.com. We respond within 30 days.
If you are in the European Economic Area, United Kingdom or Switzerland, our Data Processing Agreement at https://app.telos-iq.com/dpa sets out how we process personal data on your behalf and the transfer safeguards we rely on. You may also complain to your local supervisory authority.
If you are a California resident, we do not sell or share personal information as those terms are defined under California law, and we do not use sensitive personal information other than to provide the Service.
7. Security
We use isolation between customers, encryption in transit and at rest, encrypted secrets storage with least-privilege access, multi-factor authentication for every workspace and operator account, egress controls that restrict where workspaces can connect, audit logging and monitoring of administrative actions, and staged rollouts of updates. If we learn of a breach affecting your data we will notify the workspace owner without undue delay and in any event within the time required by law and our Data Processing Agreement.
8. Children
The Service is for businesses and is not directed to children. We do not knowingly collect information from anyone under 16.
9. Changes
We may update this policy. We will post the new version at https://app.telos-iq.com/privacy with a new version and effective date and, for material changes, email workspace owners at least 30 days in advance.
Contact
Questions and requests: Telos-IQ · support@telos-iq.com