What GrantAmp holds, and how you remove it.

What this page covers

GrantAmp is run by Artificial Intelligentsia LLC (DBA Agentsia). This page says what GrantAmp holds about you, for how long, and how you remove it. It is written from the code, so it changes when the code changes, and the date at the top is the date it was last checked against the code.

The checker

A PDF you upload to the checker is read once, in memory, checked, and discarded. It is never written to disk, never kept, and never sent to a language model or to any other service. The report goes back to your browser and nowhere else. GrantAmp does not log the file name, the contents, or the result.

Ask

A question you type into Ask is sent once to two services that answer it. Voyage AI turns the question into a search vector so GrantAmp can find the right NIH excerpts, and Anthropic writes the answer from those excerpts. Both are reached through API access, and API access at both does not use your question to train models. Each may hold a request for a short period under its own policy for abuse prevention. GrantAmp itself keeps nothing: the question and the answer are not stored or logged on our side.

Your account

Sign in is handled by Clerk. Clerk holds your email address, the sign in method you chose, the name and picture Google shares if you signed in with Google, the times you signed in, and the terms version you accepted at sign up in the account's unsafe metadata (GrantAmp reads it once into D1). When a provider shares a profile picture, Clerk may load it from img.clerk.com in the user menu. GrantAmp keeps your Clerk user id, your email address, the date your account row was created, and the date and version when you accepted the terms and privacy page. GrantAmp asks you to accept again when either page changes in a way that matters.

When you create an application in the app, GrantAmp stores its title and your intake answers against your account: the yes or no facts about the application (human subjects, animals, clinical trial, budget size, and the like), the NOFO, and two deadlines, so the requirements manifest can be rebuilt each time you open it. None of your science is stored with them. Without a plan you may hold one application and read its manifest; saved drafts, section status, the reviewer lens, reference check, SciENcv checklist, AI-use log, and readiness dashboard need a plan.

You may belong to a personal workspace and to shared organizations you create or join by invitation. GrantAmp stores each organization's name, your role in it (owner, Grants administrator, member, or viewer), pending invitations you send, a people roster you maintain for SciENcv checklist carryover, and which members are named as PI or MPI on each application. Viewers read applications shared with them and do not count as a seat. When you pick a workspace on /app, the app remembers your choice in your browser's local storage; GrantAmp's servers never receive it, and clearing site data for grantamp.com resets it.

When an owner or Grants administrator invites someone to a shared organization, GrantAmp sends the invitation through Resend to the address you type. The message includes your email address as the inviter and sets Reply-To to that address. Resend holds the invitee address and a delivery log under its own policy, the same way as notice alerts.

Each application keeps a change history: who performed an action in GrantAmp and when, such as updating intake, renaming the application, changing the PI list, saving or deleting a draft, or updating section status. The history names actions and section ids, not intake answers or draft text.

In a section workspace, the status you set for a section (not started, drafting, needs review, done) is stored against the application. Text you paste into a workspace stays in your browser and is stored only when you press Save draft. A saved draft is encrypted before it is written, with a key made for that application alone and kept wrapped under a server secret, so everyone with access to the application can open a shared draft, and it is unreadable at rest to anyone without access. It is removed when you delete the draft or the application. Delete my data removes your rows; applications that belong to a shared organization stay with that organization. A PDF you upload from a workspace goes to the checker, is read once in memory, and is discarded; it is never stored. A question you ask from a workspace is handled exactly as on the Ask page, and your draft is not sent with it.

The SciENcv readiness checklist stores the label you give each senior/key person, as you type it (a name, a role, or anything else), and which checklist items are ticked for them. Nothing from SciENcv is uploaded or kept.

For each AI-use log entry, GrantAmp stores the section, the level of help, the purpose, what material went into the tool, who reviewed the output, what was checked, the tool and model named, and the time. Prompts are stored only if someone chooses to record them, and they are encrypted with that application's key, like saved drafts. If someone adds evidence, their browser computes a SHA-256 fingerprint of each file, and GrantAmp stores only the file name and the fingerprint. The file never leaves their computer. Everyone who can open the application sees every entry and who made it, and each person can remove only their own entries. The attestation PDF is built when requested and is not stored.

Pre-flight on an application reads the assembled PDF you upload once, in memory, and discards it. GrantAmp stores the last pre-flight report for that application (counts and findings, not the PDF) so you can read it on the application page and download it as a PDF. Without a plan you may run pre-flight once per application; with a plan you may run it again. The readiness dashboard and the readiness report PDF need a plan; when you have one, they show the stored pre-flight report too.

The readiness dashboard stores which submission checklist items you ticked. Its countdowns, the standard due dates it lists from NIH's table, and the readiness report PDF are read or built from what you already saved when you open it, and the report is not stored.

The reference check in the Research Strategy and Bibliography workspaces reads the PDF you upload once, in memory, and discards it. It sends only the DOI, PMID, PMCID, or title and first author of each reference to CrossRef and to NCBI (PubMed and its ID converter), with hello@grantamp.com as the contact address those services ask for; nothing else from the PDF leaves GrantAmp. GrantAmp keeps the public record those services answer with for an identifier, for ninety days, keyed by the identifier alone, with nothing about who looked it up or which document it came from, and the entry as printed in your PDF is not stored.

The reviewer lens in a workspace sends, when you run it, the section name, the review factor, the requirement card, the NIH excerpts GrantAmp retrieved, and the draft text in the box (if there is one) to Anthropic once, through API access that does not use it to train models; Voyage AI receives only the factor query used to find the excerpts, never your draft. Each run adds one entry in that application's AI-use log at the critique level, with the exact model id, a SHA-256 fingerprint of the draft text sent (not the draft itself), and the questions returned, encrypted with that application's key. The questions appear in the workspace and in the log.

When someone marks an application as submitted, GrantAmp stores the time in UTC and who marked it. The mark can be undone. The AI-use record ZIP is highlighted on the application page after a submission mark is set.

The what changed page stores the time you last opened it, so the next visit can mark what is new. Everything it lists is GrantAmp's own record of the NIH pages it holds, the same for everyone.

Nothing else about you is stored until you use a feature that stores something, and each such feature says so on its page before you use it.

Delete my data

The Delete my data button on your application page removes every row GrantAmp holds for you and deletes your Clerk sign in account, right away, in one step. It does not ask why. While a plan is active, you can wait until it ends, cancel in Manage billing, or choose cancel my plan now and delete my data, which ends the plan immediately with no refund for remaining days. While you own a shared organization that still has applications in GrantAmp, delete is blocked until those applications are gone or ownership is transferred. If Clerk cannot remove the sign in account after GrantAmp rows are gone, the site tells you and you can delete the Clerk account from the user menu or contact hello@grantamp.com. Listed admin accounts cannot use Delete my data.

Delete my data removes applications in your personal workspace, their application_draft_keys rows, and any legacy per person draft_keys rows. Applications in a shared organization stay, with their keys. Your organization memberships and application_pis rows go with everything else. On shared applications, application_events, applications.created_by, and ai_use_log entries that named you replace your user id with a fixed former member marker so the history stays readable and holds no identifier for you.

Leaving a shared organization removes your membership and your PI links on that organization's applications, but it does not delete the organization's applications or change history. A member who leaves takes nothing from the organization.

The owner of a shared organization may delete it from organization settings after typing the organization's exact name. That step removes the organization, its memberships and invitations, its people roster, and every application stored under it, including drafts, keys, change history, pre-flight reports, readiness marks, and AI-use log entries. It does not delete member accounts or their personal workspaces.

Pending organization invitations you sent are removed when you delete your data. Invitations past their expiry date are deleted by the daily cleanup job.

Rate limiting

To keep the free checker and Ask open to everyone, GrantAmp counts requests per address: the checker per hour, and Ask three questions a day without a plan, including when you are signed in without one. The address itself is not stored. The counter is keyed by a one way hash of the address and the day, which cannot be turned back into the address, and the rows are deleted after two days. With a plan, Ask is counted per account the same way, by a one way hash of the account id and the day. Organization invitation emails are limited to twenty per organization per UTC day and fifty per sender per UTC day, using the same counter table and the same two day retention.

Site counts

GrantAmp also counts how often public pages are opened and how often certain features are used: the checker, Ask, new account rows, requirements manifests built, pre-flight runs completed, checkouts started and completed, and alert confirmations. Each total is stored by feature name, UTC day, and sometimes a public route or plan name. Nothing in that table identifies a person, an address, or a referrer. The counts help GrantAmp see whether the site is working; they are not sold and are not sent to a third party analytics service.

Notice alerts

If you sign up for the Guide Notice alerts at /alerts, GrantAmp stores your email address, the time you signed up, the time you confirmed, and whether you chose to include funding opportunities, and nothing else about you. Nothing is sent to an address until the link in the confirmation email is opened, and a sign up that is never confirmed is deleted after seven days. Every email carries an unsubscribe link, and unsubscribing deletes the address. The emails carry no tracking pixel and no rewritten links. Guide Notices come from NIH's weekly feed; when you include them, the digest lists funding opportunities that are new on Grants.gov since the last digest.

The emails are sent through Resend, which holds the address and a delivery log for each message under its own policy. The address is not used for anything else and is not shared with anyone else.

Hosting and logs

GrantAmp runs on Cloudflare. Cloudflare keeps request logs for GrantAmp for a short period for operations. Those logs carry the address and the path requested, not the contents of an upload or a question, which GrantAmp never writes to a log.

Payments

Payments are handled by Stripe on Stripe's page. Stripe holds your card, your billing address if it asks for one, and your invoices, under its own privacy policy. GrantAmp never sees a card number. GrantAmp holds your Stripe customer id, the plan you chose, Stripe's status for it, the date the period you paid for ends, and a ledger of the ids of the events Stripe sent, which is kept for thirty days so a repeated event is applied once. A team plan for a shared organization and a Submission Pass for one application are stored the same way in separate rows, scoped to that organization or application, and written only from Stripe events.

When Delete my data runs, GrantAmp removes your personal subscription row and the link to the Stripe customer. Stripe keeps its own payment and invoice records as financial record keeping requires; GrantAmp does not delete those. Organization and application scoped rows stay until that organization or application is deleted. You can cancel a plan in Manage billing on Stripe's page and delete when the period ends, or use cancel my plan now and delete my data to end the plan immediately with no refund for remaining days and remove GrantAmp's rows in one step.

Cookies

Clerk sets session cookies when you sign in, which sign in needs to work. GrantAmp sets no analytics or advertising cookies and loads no tracker. The site's fonts ship with the site bundle from GrantAmp's own host, not from a third party font service.

Children

GrantAmp is for people preparing research funding applications. It is not directed at children under 13 and does not knowingly hold their data.

Changes

When this page changes, the date at the top changes. A change that matters to account holders is also sent to the email address on the account.

Contact

Questions about this page go to hello@grantamp.com.