1. Roles
- Account data (your sign-in, team and billing contacts): Logthread decides why and how it is used.
- Telemetry data you send (logs, traces and metrics): you are the data fiduciary under India's Digital Personal Data Protection Act, 2023, and Logthread is your data processor. See the Data Processing Addendum.
2. What we handle
| Data | Why |
|---|---|
| Email address, display name, workspace name and your role | To run your account and team. |
| Password, stored only as a salted scrypt hash | To sign you in. |
| Sessions: IP address, browser user agent, last-seen time | To keep you signed in and let you review and end sessions. |
| Audit log: action, actor, target, IP address and time | To show account and key changes to workspace admins and to protect the service. |
| Invitation email addresses | To invite people to a workspace. |
| Ingest keys, stored only as hashes; saved searches; alert rules and channel settings | To provide the service. |
| Usage counters (volume, queries) per workspace | To enforce plan limits, show usage and, later, bill. |
| Telemetry data you send, and queries you run on it | To store, search and alert on it for you. |
We use one session cookie to keep you signed in, and your browser's local storage remembers your theme choice. We do not use advertising or analytics cookies. The public pages load fonts from Google Fonts, so your browser contacts Google when you open them.
3. Where data is kept
Telemetry data is stored in the Mumbai region, India, through our storage provider. Telemetry passes through Logthread's ingest pipeline and may wait in its queue briefly before it reaches storage. Account data is held in Logthread's control-plane database. Hosting details for the control plane are to be confirmed before publication. Providers that handle data for us are listed under Subprocessors.
4. Retention
- Telemetry data is kept for the retention period of your workspace: it is limited by your plan, and an owner can choose a shorter period from the values the plan allows. Shortening requires confirmation because older logs are deleted.
- Account data is kept while your account exists.
- Used and expired sign-in and verification tokens and sent email records are cleaned up automatically.
5. Deleting data
Workspace. An owner requests deletion in Settings. Ingest stops at once. After a 7-day grace period (an owner can cancel until then), Logthread revokes all ingest keys, sets log retention at the storage provider to its minimum of 7 days, deactivates the workspace's storage sub-organization, and deletes keys, saved searches, alerts, invitations, correlation settings and memberships. Owners and admins are emailed when deletion is scheduled and when it completes.
Kept after deletion. Usage and billing records are kept for 7 years as legal and billing records; the workspace name in them is replaced by a keyed hash. The audit log, including the final deletion event, is kept. These retained records do not contain log content.
Account. You can delete your account in Settings with your password. You cannot do this while you are the only owner of a workspace that still exists; make another member an owner or delete the workspace first.
Deletion from backups: to be confirmed before publication.
6. Your rights
Under the DPDP Act you can ask to access, correct or erase your personal data and to nominate a representative, and to raise a grievance with us and, if it is not resolved, with the Data Protection Board of India. Write to us at the contact address, which is to be confirmed before publication. If your data is in logs that a customer sent, the customer is the data fiduciary and we will pass your request to them.
7. Security measures
- HTTPS for the web app and API in production, and HTTPS to the storage provider. Email is sent over TLS where the mail server offers it.
- Passwords stored as salted scrypt hashes; session tokens, ingest keys and email tokens stored only as hashes.
- Credentials we hold for the storage provider are encrypted with AES-256-GCM under a key held outside the database.
- Ingest keys can send logs, traces and metrics, never read them.
- Role-based access checked on the server for every request, and an audit log of account and key changes.
- Rate limits on sign-in and other sensitive actions.
No system is perfectly secure. We have no third-party security certification at this time.
8. Changes
We will update this notice as the service changes and will tell account owners about material changes by email.