Privacy Policy
1. What we collect
To operate the service we collect and store:
- Account information — your email address, name, title, and password hash (bcrypt). If you sign in via Google OAuth, we receive your name and email address from Google but never see your Google password.
- Billing information — if you buy a plan or a token pack, you enter your card details on Stripe's hosted checkout page and they go to Stripe directly; they never pass through or sit on our servers. We keep your Stripe customer ID, your plan and subscription status, and a record of each payment (amount, currency, date, and the tokens credited).
- Manuscript content — the manuscript text, references, notes, author details, figure legends, and reviewer comments that you create within ScriptaDraft.
- Figure images — image files you upload as figures are stored on our servers so they can be displayed back to you and reviewed by the AI. See section 2.
- Usage telemetry — feature interactions, token consumption, and error events used to operate the service, maintain stability, and prevent abuse. Telemetry does not include the content of your manuscripts.
- Session data — secure session tokens and basic browser fingerprint information used for authentication.
2. How your manuscript content is stored
Text content (manuscripts, references, drafts, figure legends, reviewer comments, author details) is encrypted at rest using AES-256-GCM. Encryption keys are managed separately from the database and are not visible to standard database queries.
Figure images you upload are also encrypted at rest using AES-256-GCM, stored in a private location with non-guessable filenames, and served only to your authenticated account. They are deleted when you delete the figure or the paper. Do not upload figures containing personal or identifying information about research participants.
3. Regional data hosting
Application data is held in regional databases — for example, US users on US infrastructure. This is designed so that unpublished research stays under an appropriate jurisdiction. Region is determined at sign-up based on the instance you access.
4. How AI providers handle your content
ScriptaDraft sends the content you submit for AI assistance to third-party inference providers. Inference is provided by Amazon Web Services (Bedrock), Google Cloud (Vertex AI) and Microsoft Azure. Requests reach them through an API routing service, which directs each request to one of these providers.
All AI processing uses Zero Data Retention (ZDR), meaning:
- your content is processed transiently to generate the AI response, then dropped from the provider's systems;
- your content is not used to train AI models;
- your content is not retained by the AI provider after the response is returned.
Zero-retention routing is enforced at the account level with our routing service: requests can only be served by endpoints classified as zero-retention, and a request that cannot be served by such an endpoint fails rather than falling back to one that retains data.
We do not currently restrict inference to a particular country. If the geographic location of AI processing matters for your institution's data-governance requirements, contact us before uploading unpublished work.
ScriptaDraft updates this policy when the underlying providers or routing arrangements change.
5. What we don't do
We do not:
- sell or rent your data;
- share your data with third parties for marketing;
- use your application content to train or fine-tune AI models;
- read your manuscripts for any purpose other than serving the request you've made.
6. Cookies and analytics
ScriptaDraft uses a first-party session cookie to keep you signed in. We also use Google Analytics to understand how visitors find and use our website and application — for example, which pages are viewed and roughly where traffic comes from. Google Analytics sets its own first-party cookies and processes usage data on our behalf; it uses your IP address to estimate coarse, city-level location but does not log or store your IP address in Analytics. We never share your manuscript content or application data with Google or any other analytics provider. We do not use advertising cookies or cross-site tracking, and we do not sell your data.
You can opt out of Google Analytics by installing the Google Analytics opt-out browser add-on, or by blocking analytics cookies in your browser.
7. Your rights
You may at any time:
- access and export your application data from within the product;
- request correction of inaccurate account information by writing to [email protected];
- request deletion of your account and associated data — deletion is permanent and irreversible.
Depending on your location, you may have additional rights under local law (for example, GDPR for European users, or the Australian Privacy Act for Australian users). We will honour all applicable rights.
8. Data retention
Account and application data are retained while your account is active. On account deletion, all application content is permanently removed within 30 days. Anonymous usage telemetry may be retained beyond that point for service stability analysis but cannot be linked back to you.
9. International transfers
If you access an instance hosted in a different jurisdiction from your own, your data may be transferred internationally. Hosting regions are documented in the application interface and in section 3 above.
10. Security
We implement reasonable technical and organisational measures to protect your data, including encryption at rest, encrypted transport (TLS 1.2+), narrow access controls, and database isolation between regions. No system is completely secure; we will notify affected users of any material breach in line with applicable law.
11. Changes to this policy
This Privacy Policy may be updated. Material changes will be communicated via the application.
12. Contact
For privacy questions, data requests, or to report a concern, write to [email protected].