didaiwriteWhat happens
to your writing?
DidAIWrite keeps account data separate from text checks. These details describe the implemented system and the services that still require configuration.
Accounts and sign-in
Accounts use Supabase Auth. You can sign up with an email address and password, or Google when the Google provider is enabled. Passwords are handled by Supabase Auth; DidAIWrite does not store them in its profile tables. Session cookies keep you signed in. Email confirmation and password-reset messages are account-security features, not passwordless sign-in.
Text you paste
Text is sent to DidAIWrite’s server only when you press Check. If live detection is not configured, the server returns an unavailable message without scoring or saving it. When detection is enabled, the server sends the text to the configured detection provider. Request bodies are not intentionally written to application logs.
Detection-provider handling
The current integration targets Sapling. Its general published privacy policy describes content storage and use to improve its services, and its API documentation describes detector caching. DidAIWrite therefore does not promise zero provider retention or no provider training. Live scoring is disabled until commercial-use permission and the applicable data-processing terms are confirmed. Review the provider’s API agreement before submitting sensitive material.
Reports you save
With an eligible paid plan, you can explicitly choose Save report. The text, score, sentence offsets, provider details, and report date are stored in your Supabase account. Database access rules restrict reports to their owner. Delete a report from My reports to remove it from the active database; infrastructure backups may retain copies under the hosting provider’s backup policy.
Uploaded files and batches
Uploaded bulk documents use a private storage bucket. Text extracted for queued checks and temporary batch results are stored for processing, with an expiry of 24 hours. A scheduled cleanup worker must be enabled before bulk processing is opened to users; actual removal depends on that worker completing successfully. Saved reports are retained until you delete them. Do not put student names or other identifiers in file names.
Hosting region
The connected Supabase project is in AWS us-east-2 in the United States. It is not an EU-region project. Account data and saved reports may be processed in the United States. The final production privacy notice must cover any applicable international-transfer safeguards.
Usage limits
When live checking is enabled, DidAIWrite uses salted hashes of the request IP and a random browser cookie to enforce the free daily allowance. The application does not use a canvas or audio fingerprint. Usage counters contain counts and word totals, not the submitted text. Expired counters are removed by the scheduled cleanup worker.
Before launch
Google OAuth, the detection agreement/key, payment credentials, background scheduling, transactional email, and operator contact details still need final verification. No accuracy benchmark, data-residency certification, or regulatory-compliance certification is claimed.