1. Scope and operator
This draft would apply to StringProof accounts, workspaces and public pages. The legal entity responsible for the service, its registered address, privacy contact and representative details remain publication blockers.
2. Data handled
- Account data such as name, verified email address, authentication identifier, workspace and role.
- Customer content including HMI images, translation tables, expected-text lists, recognition results, review decisions, comments and exports.
- Operational data including session, security, audit, error and usage records.
- Billing data would be handled by the selected payment provider. No payment provider is connected for public purchase yet.
StringProof does not receive your Google password when Google sign-in is used.
3. Why data is used
The application uses data to authenticate users, provide workspace permissions, receive files, recognize screen text, compare that text with a selected reference, support human review, create exports, secure the service, diagnose failures and maintain audit records. The lawful bases and any optional marketing uses must be completed for the actual launch jurisdictions.
4. AI and data flow
For AI recognition in the current Cloudflare pilot, the application sends the current image and target language to OpenRouter, which routes the request to Google Gemini. This is remote processing, not on-device inference. Translation references remain in StringProof’s comparison engine and are not included in the recognition request. Manual entry and review remain available without AI recognition.
The service operator, provider terms, account arrangement, data controls and applicable retention treatment must be confirmed for the final notice. It must identify all production processors and link to their applicable notices.
5. Storage, retention and deletion
Uploaded originals and derivatives are stored in Cloudflare R2; workspace records and metadata are stored in Cloudflare D1. Workspace settings currently control task retention and default to 30 days. This is an implementation default, not a public retention promise.
Deleting a task removes its stored original files, translation tables, task results and exports and cancels active runs. A minimal deletion event remains in the audit trail. Operator-created offline backups are separate and are not automatically erased by online task deletion. Production backup retention, restoration behavior, audit-log retention and deletion timelines remain to be specified.
7. Choices and rights
Workspace users can review their content and authorized roles can delete tasks. Depending on where a user is located, law may provide additional rights to access, correct, delete, restrict or export personal data, object to certain uses, or complain to a regulator. The final notice will explain how to submit and verify requests without limiting mandatory rights.
8. Security and children
Current safeguards include role-based access, authenticated file routes, audit records and restricted server-file permissions. No system is completely secure. The intended age requirement and any child-data restrictions must be set before launch.
9. Changes and contact
For pre-launch questions, email support@stringproof.app. A dated, effective notice identifying the operator and privacy contact responsibilities must replace this draft before public launch.
Menu