Limited collection
The product asks for one supported telecom statement and only optional reading hints—not unrelated documents.
Security
A telecom bill can contain names, contact details, account references, and usage information. Our design starts by treating that context as sensitive.
How the system is designed
Security is a continuing operational responsibility—not a badge, buzzword, or single encryption claim.
The product asks for one supported telecom statement and only optional reading hints—not unrelated documents.
Source bill files are designed to be removed after processing, with short-lived technical copies limited to retries, security checks, and deletion workflows.
Structured reports are kept separate from source files. Access requires a protected, expiring link; anyone who receives that link may be able to use it.
Stripe supports payment and OpenAI supports document interpretation and report drafting. Information is shared only as needed for those functions.
Access restrictions, environment separation, protected transport, credential controls, logging, and monitoring are used to reduce avoidable exposure.
No online system is risk-free. We avoid absolute claims and provide a direct path to report a suspected security problem.
Data lifecycle
Keeping those artifacts separate makes it possible to remove the source while preserving the useful result you paid for.
A supported statement enters a private processing flow.
Relevant content is read, structured, and returned with source evidence to review.
The structured report is stored independently from the source document.
The source file is deleted after processing and short-lived operational needs end.
You can reduce exposure, too
Report a concern
Use Support and choose “Security concern.” Describe what happened, the approximate time, and the private report reference. Do not include the access token, passwords, full account numbers, card details, or a copy of the bill.