Privacy
How Scientize handles your data
A plain description of what we store, where it is kept, who processes it for us, how long it stays, and what you can do about it. It describes the platform as it is built and changes when the platform does.
What we store
The records that make up your account
Scientize keeps only what the product needs to work. Everything below is yours to download from Account → Security as one file.
- Account and profile
- Your name, email address, password (stored as a one-way hash, never readable), headline, links, country, ORCID, the contact details you choose to add, and the profile entries you write: education, affiliations, awards, presentations, services, publications and research fields.
- Research content
- The proposals, polls and expert requests you post; the projects you own or join, with their tasks, milestones, resources and progress updates; your comments, reactions, interest and applications; the grant applications you write and the opportunities you save.
- Messages
- Project chat and direct messages, with their edits and deletions. A conversation belongs to both people in it; your export carries your own words only.
- Files
- Attachments, profile pictures, cover images and publication documents you upload, stored privately and served only to people the owning record lets in.
- Activity and security
- Notifications and your notification preferences, saves, follows and connections, the people whose profiles you visited, matching and AI drafting usage, and the security events of your account (sign-ins, password changes, two-step verification, sessions ended).
- Billing status
- Your plan and subscription state. Card details never reach our servers — Stripe holds them and we store the identifiers needed to recognise the subscription.
Where it lives
One database, one file store
Records are kept in a single PostgreSQL database on our hosting provider. Uploaded files are kept in an S3-compatible object-storage bucket when one is configured for the deployment; otherwise they are kept on the application server's private disk. Neither is reachable from the public internet except through the application, which checks who you are and what the record allows on every request. Connections to and from the application use TLS.
Who processes it for us
A handful of processors, each for one job
No data is sold or shared for advertising. The following services process data on our behalf, and only for the purpose named.
- Resend
- Delivers the email we send you: verification codes, password resets, invitations and the notifications you have turned on. Resend receives your address and the message content.
- Stripe
- Handles payment for Pro and institutional subscriptions. Stripe receives your email address and payment details directly; we receive the subscription state back.
- OpenAI or Anthropic
- Provide the optional drafting assistance in the proposal editor and the short "why this fits" sentences next to grant and project suggestions, when the deployment has a key configured (OpenAI is used when both are). The text you ask the assistant to work on, and for the sentences your research fields and the suggestion's public description, are sent at the moment you use the feature. Nothing is used to train their models under the API terms we use.
- OpenAI (matching vectors)
- When an OpenAI key is configured, your research fields, interests and bio — and the text of grants and public listings — are turned into numeric vectors that rank suggestions. The vectors are stored with your profile and recomputed only when it changes; without a key, matching falls back to deterministic rules.
- Cloudflare Turnstile
- Checks that a signup comes from a person, not a script. Your browser completes the challenge with Cloudflare; we receive a pass or fail token.
How long
For as long as the account exists
Your records are kept while your account exists. Deleting the account anonymises it: the name and address are replaced, the profile is emptied and the sessions are ended, while the institution's records you contributed to stay with the institution with your name removed.
Audit rows — who did what, when — are kept for the retention period each organization sets for its own trail (between 30 days and ten years, or indefinitely when none is set); platform and personal security events are kept with the account. Anonymous usage counters for the public Marketplace are purged after thirteen months.
Institutions
When you work inside an organization
Projects, proposals and listings created inside an organization are that organization's records: its administrators manage access to them and can export them, and they remain the institution's after you leave or delete your account. Your membership, role and the access you were granted are part of its audit trail.
Scientize's own administrators can read tenant and personal data to run the platform — moderation, support, provisioning. Every such read is recorded in the audit trail, and an organization sees those reads in its own export.
Your rights
Export, correct, delete, ask
- Export
- Download everything above as one JSON file from Account → Security → Your data, up to three times an hour. Each export is recorded in your security events.
- Correct
- Edit your profile and account settings at any time; the change applies at once.
- Delete
- Delete your account from Account → Security. You will be asked to confirm who you are first; if you are the only owner of an organization, you will be asked to hand it over before the account can go.
- Ask
- Questions about your data, or a request we have not covered here, go through the contact page.