Last updated: March 22, 2026
Privacy
This is the beta privacy notice for VeriPrep. It is written to be practical and truthful about the current product, including the limits of the current implementation. It is not legal advice and should still receive legal review before any broader public launch.
The current beta is designed around minimal personal data. In normal test use, users should not need to provide personal details beyond account or login identifiers. Testers should avoid entering personal, special-category, or confidential information into prompts, uploads, notes, or feedback unless they have been specifically instructed to do so for a controlled test.
Beta privacy summary
VeriPrep currently mixes hosted storage with local browser storage. Hosted account-linked data can be stored in Supabase-backed systems, while some study history, weak-bank data, and preferences may remain locally in the browser or device you used.
For normal beta use, the main personal data categories are login or account identifiers, study activity, saved study materials, deletion-request details, and limited device or service logs used for security and troubleshooting.
We do not currently offer BYOK in this beta. If a future live subscriber tier introduces BYOK, that will be described separately in updated product and privacy terms.
We do not currently publish a registered business address or legal entity details — those will be added after incorporation. For support or privacy enquiries, email veriadmin@veri-prep.com.
What data the current build can handle
Account and profile data: if you sign in, account-linked profile and progress records can be stored in hosted systems.
Uploaded study materials: document uploads and related retrieval metadata can be stored in hosted storage when that feature is configured and used.
Local-only data: browser storage can contain topic history, weak-bank state, BYOK preferences from older code paths if separately enabled outside this launch scope, and other session data. Clearing local browser storage removes those local copies from that device, but does not remove hosted records already stored on the backend.
Retention schedule
This is the practical retention schedule intended for the beta launch. It is designed to be conservative, usable, and consistent with the current deletion-intake flow. It may be tightened or clarified after legal review.
Account and login identifiers: Kept while the beta account is active, then deleted or anonymised within 12 months of the last meaningful activity unless a shorter deletion request is verified and actioned earlier.
Study profile and saved study progress: Kept while the account is active. If the account becomes inactive, the target retention window is up to 12 months before deletion or anonymisation.
Generated study content and user-saved materials: Kept while needed to provide the beta service and removed on verified deletion request or within 12 months of inactivity.
Temporary uploads or transient processing data: Target deletion within 90 days if not deliberately saved as part of an active account workflow.
Security and service logs: Usually retained for up to 30 days, and kept longer only where reasonably necessary for abuse prevention, incident review, or legal claims.
Backups: Retained on a rolling basis for up to 35 days before overwrite or deletion. Deletion from backups may lag until the next backup cycle completes.
Support, feedback, and privacy request records: Retained for up to 24 months after the issue or request is closed so that we can evidence handling and prevent duplicate processing.
Aggregated or anonymised analytics: May be retained longer if they no longer identify a user or reasonably allow a user to be singled out.
Deletion requests
If you want hosted data reviewed for deletion, use the intake flow below where available. We aim to respond to valid privacy requests within one month, subject to identity checks and any lawful reason to retain limited records.
The form below creates a deletion request record for manual review. Submitting it does not instantly erase hosted data, and this repo does not fabricate a support queue or legal workflow beyond recording the request.
Use this for hosted account/profile data or uploaded documents. For local-only browser storage on a test device, clear the site data in that browser as a separate step.
Further information
For upload rights, AI accuracy notices, and acceptable use, see the Terms of Use.