Privacy
Privacy information about your documents.
Draft privacy notice for review. The operator’s identity, contact details, service locations, retention periods and final provider list must be completed before this notice can describe a production service.
Policy draft — operator details pending
At a glance
- Your organisation chooses what it uploads and remains responsible for having permission to process it.
- Azure Document Intelligence and Azure OpenAI process document content. The public pages are hosted on Namecheap. Sites hosts the private application; Cloudflare D1 and R2 store workspace records and files. Exact residency and provider data-handling commitments still require operator confirmation.
- Processing may involve document content, requested-field descriptions and extracted results. The operator must disclose the actual request payloads, logs and recipients.
- Ask the operator about access, correction, export and deletion requests and the privacy authority relevant to your location.
The service operator.
Tracewise’s operator information has not been supplied for this build. The final notice must name the responsible legal entity and explain its role for account records and uploaded documents.
Operator contact details have not been published. Private demo requests are saved in the requester’s workspace. Open private demo requests
Information involved.
- Account information may include your name, work email and workspace details. The deployed authentication method determines how credentials are handled.
- Uploaded files may contain personal information such as names, phone numbers, addresses, signatures and tax identifiers.
- Processing produces extracted fields, source locations, warnings, review changes and export files.
- Operational records may include page usage, document status and activity history. The final notice must specify the telemetry collected, whether it contains document values and how long it is retained.
- Demo requests are saved in the signed-in user’s private workspace.
- Any files you choose to share for an agreed demonstration.
- If paid plans are enabled, the final notice must identify the payment provider and the billing information handled. No payment processor is confirmed here.
Purposes of processing.
Tracewise is intended to process documents into reviewable data, support workspace access and enable exports. The final notice must identify the purposes and legal basis for account administration, service logs, support, billing and any other data use. No sale, training-use or retention promise is made without a verified policy.
Services that may receive data.
The table lists the implemented service path and details that still need operator confirmation. Payment processing and outbound email are not connected.
| Service or recipient | Processing role | Location information |
|---|---|---|
| Azure Document Intelligence | Recognises text and layout in uploaded document content. OCR word references support source-box validation. Provider retention and contractual commitments depend on the configured Azure service. | Azure resource region to be confirmed by the operator. |
| Azure OpenAI | Extracts requested fields from document evidence and field definitions. The live synthetic evaluation used the deployed GPT-6 Astra model with high reasoning effort. Applicable provider data-handling terms must be confirmed. | Model deployment and processing geography to be confirmed. |
| Sites / Cloudflare hosting and storage | Hosts the application, stores workspace metadata in D1 and retains uploaded originals, checkpoints and revision snapshots in R2. | Hosting, storage and backup regions have not been established. |
| Billing provider — unconfirmed | A payment provider and billing flow must be identified before paid subscriptions are activated. | Provider and locations must be published when configured. |
| Email provider — unconfirmed | No outbound invitation or demo email service is connected. Inviters copy links manually; demo requests are saved in their workspace. | Provider and locations must be published when configured. |
Processing locations and transfers.
Azure processing and deployment storage locations must be verified for this installation.
Document analysis uses Azure Document Intelligence and Azure OpenAI. Application records and files use Sites with Cloudflare D1 and R2. Exact service routing, storage residency, backups and transfer safeguards must be documented by the operator. Processing is not represented as restricted to Nigeria, Africa or the EU.
Review the current terms and data-protection documentation for each configured Microsoft Azure service. The operator must describe relevant retention, access, deletion and model-use conditions rather than rely on another product’s provider statements.
Review the hosting and storage provider’s current data-protection terms, including backup copies and deletion behaviour. The deployed configuration determines which commitments apply.
Files shared for a demonstration.
Before providing demonstration files, agree on who will process them, which services will receive them, how long they will be retained and how deletion can be requested. Use redacted examples until these details are confirmed.
Privacy requests.
Depending on applicable law, you may have rights to obtain, correct, export or delete personal data and to object to certain processing. The final notice must explain how to submit and verify requests and identify the responsible contact.
You may also have a right to contact the relevant data-protection authority. The operator must identify the authority and complaint process applicable to its service. Nigeria Data Protection Commission
Security information.
The security page identifies the controls and deployment details that require confirmation. Review the final service configuration before uploading sensitive material.
Children’s information.
Tracewise is intended as a business document workflow. Do not upload children’s personal information without appropriate authority, safeguards and an agreed processing purpose.
Tracewise