Data & Security
Your customers trusted you with their words. We treat them that way.
A plain account of what we collect, how long we keep it, what the automation does and does not do, and how access is controlled.
Collection
What is connected, and how.
Source types
Reviews, support tickets, survey responses, social mentions, chat transcripts and files you upload. Only sources you explicitly connect are read. Nothing is gathered from elsewhere.
Read-only access
Connections request read access to feedback content and its metadata. Tellusglint never posts, replies or changes anything in your connected tools.
Customer text only
For tickets and chat, only the customer-written parts are clustered. Agent replies and internal notes are excluded from analysis.
Personal details masked
Email addresses, phone numbers and card-like numbers found inside feedback text are masked before comments are shown on boards and in digests.
Retention
Kept for as long as it is useful, then gone.
Feedback and theme history are retained according to your plan. You can shorten retention, delete a single source, or delete the whole workspace.
Honest disclosure
Automated, reviewed periodically, not verified line by line.
Theme clustering and sentiment scoring are automated. The models behind them are evaluated periodically against sampled feedback, but individual comments are not manually checked one by one. That means a comment can occasionally land in the wrong theme or receive a score a person would disagree with. Every theme links to the comments inside it so your team can see exactly what it is built from, and you can rename, merge or split themes whenever the grouping does not match your understanding.
Protection
Encryption and access control, stated plainly.
Encrypted in transit
All traffic between your browser, connected tools and Tellusglint uses TLS.
Encrypted at rest
Stored feedback, theme history and connection credentials are encrypted at rest.
Role-based access
Admins decide who can view boards, edit themes, manage sources and export data.
Credentials isolated
Connection tokens are stored separately from feedback and never shown after setup.
Activity history
Source changes, exports and permission updates are recorded for workspace admins.
You can leave cleanly
Export everything, then delete the workspace. Nothing is kept for other uses.
Your customers already wrote the roadmap.
Connect your first source and see this week's themes resolve out of the noise.