Data handling and retention
This page is the inventory. The HIPAA, BAAs and PHI page covers the agreements and the identifier policy; the Privacy Notice (version PRECISION-PRIV-2026-08-31-v0.9) is the governing document.
What is stored
| Data | Purpose | Where | Retention |
|---|---|---|---|
| Account: name, email, role, specialty, institution, password hash | Running your account | Application database | While the account exists |
| Terms and Privacy acceptance records (version, time, typed name) | Evidence of acceptance | Application database | Retained after account deletion, as the notice states |
| Trial and subscription state | Billing | Application database and Stripe | While the account exists; Stripe per its own policy |
| Report history | Your recent reports under History | Encrypted per-account storage on the application server | Until you delete them or the account is deleted |
| Personal templates, macros, corrections, preferences | Your settings | Application database | While the account exists |
| Feedback on a dictation | Improving the product | Application database and an operations spreadsheet | Metadata only; see below |
| Email log (recipient, subject, status, time) | Delivery auditing | Application database | Operational period, then purged |
| Usage counters per account | Abuse detection and capacity | Application database | Aggregated; never block a user |
What is processed but not stored
- Dictation audio is streamed to the transcription service and is not recorded by GigHz Precision AI.
- Each sentence and the report state are sent to the placement and composition models for the duration of the request. The application keeps the resulting report in your history; it does not keep the prompts.
- Content sent to OpenAI's API is not used to train models under the API terms.
What is never collected
- Patient identifiers: the product does not ask for them and the Terms prohibit entering them.
- The text of your report inside feedback: the feedback payload carries a character count, never an excerpt, and the test suite enforces that.
- Advertising or third-party analytics identifiers: there are none on the application.
Where it lives
Everything above except Stripe's billing records and the operations spreadsheet lives inside GigHz LLC's AWS account, on encrypted storage, in the United States. Stripe receives payment details and the account email; the spreadsheet receives signup and feedback metadata, never clinical text.
Deleting your data
- Individual reports can be deleted from History at any time.
- To delete your account, email signal@gighz.com from the account's address. We respond within 30 days, as the Privacy Notice states. Account records and report history are removed; acceptance records are retained.
- Cancelling a subscription does not delete the account; the account remains readable until you ask for deletion.
Access to your data by GigHz LLC
Operational access is limited to the owner and is used for support and incident response. We do not read reports in the course of normal operation, and we do not use report content to train models. If a support case requires looking at a specific report, we ask you first.
This page is generated from documentation that ships with the application (docs v1.2.2). Version numbers, prices and trial lengths on this page are read from the running system, not typed by hand.