Privacy policy
Effective October 8, 2026. Papers by Ouroboros Apps (ouroborosapps.com) is operated by Ouroboros Apps. Privacy, export, and deletion requests go to ouroborosplugins@gmail.com.
Information we process
Connecting an assistant does not ask for your name or email. Papers creates a random account id. Tool calls send the arguments the assistant submitted, and only those arguments. Do not put passwords, payment card details, or unrelated personal information in a query.
Anonymous account id
A random id is stored in a signed HttpOnly cookie and in the OAuth access and refresh tokens. Papers uses it to tell one connection from another and to attach a trial or subscription. The cookie lasts 90 days. An access token lasts 1 hour. A refresh token lasts 30 days. Papers does not keep a separate copy of the token beyond the signature check.
OAuth client registration
The client name and redirect addresses are carried inside a signed client id so the connection can finish. That registration lasts 1 year. It is not a database row.
Authorization codes
Each authorization code is single-use. Papers stores the code id until it expires so the code cannot be replayed. The code lasts 5 minutes. The stored id is dropped on the next store write after it expires.
Connection form cookie
A CSRF cookie lasts 30 minutes and is cleared when you approve, cancel, or submit reviewer sign-in. It exists so the connection form cannot be posted from another site.
Queries, identifiers, and citation styles
A search, a DOI, PMID, arXiv id, or OpenAlex work id, and a citation style are sent to the scholarly source that answers the tool. Papers uses them to return the record that source actually sent. Papers does not keep a database of queries. There is no query history to export later.
Scholarly polite-use address
If the operator set a scholarly contact address, that address is sent to OpenAlex, Crossref, and PubMed in the User-Agent or mailto parameter, because those services ask for one. It is an operational header. It is not the public support address, and this page does not print it. Optional API keys for PubMed and Semantic Scholar stay on the server and are sent only to those services.
Subscription snapshot
When you start a trial, Papers stores the account id, Stripe customer id, subscription id, status, current period end, and plan interval (monthly or yearly). Stripe receives the account id as metadata and collects the payment method. Papers does not receive or store a full card number. The snapshot is how Papers decides whether a tool call is entitled.
Rate-limit counters
The request IP and a count are held in memory for the limit window, about one minute for tool calls and about ten minutes for sign-in and token requests, then discarded. They are there to slow abuse. They are not written to the account store.
Reviewer sign-in
When the operator has configured store-reviewer sign-in, the reviewer email and password hash are read from the server environment. They are not written to the account store and they are not in the source repository. A successful sign-in uses a stable account id derived from that email. Complimentary access has no end date. The environment values remain until the operator removes them.
Email you send us
A message you send to the public contact includes the reply address and whatever you write. Papers uses it to answer support, billing, privacy, export, and deletion requests.
Why and where
We use this information to run Papers, complete OAuth, enforce a trial or subscription, answer support, prevent abuse, and meet legal obligations. We do not sell it, and we do not use queries to train our own models. These pages do not include advertising trackers.
Third parties
OpenAlex, Semantic Scholar, PubMed (NCBI), Crossref, and arXiv receive the query or identifier needed to answer the tool. Stripe processes the subscription. Vercel hosts the service and, when blob storage is selected, holds the private account snapshot. The MCP client you connect, including ChatGPT, Claude, Gemini, Grok, Cursor, and any other host you authorize, receives the tool results it asked for and applies its own terms. Service providers may process information outside your country.
Control and retention
- Anonymous account id: cookie 90 days, access token 1 hour, refresh token 30 days.
- OAuth client registration: 1 year.
- Authorization code ids: 5 minutes, then dropped on the next store write.
- Connection form cookie: 30 minutes.
- Queries, identifiers, and citation styles: not retained by Papers after the response is sent.
- Scholarly polite-use address and server API keys: kept in the operator’s environment until the operator removes them. Papers does not store a copy in the account snapshot.
- Subscription snapshot: kept until you ask us to delete it or a newer Stripe event replaces it. Stripe may keep billing records for accounting and dispute handling under Stripe’s own schedule.
- Rate-limit counters: about one to ten minutes, in memory only.
- Reviewer email and password hash: server environment only, until the operator removes them. The complimentary entitlement does not expire.
- Support email: kept while we resolve the request, and longer when security or a legal obligation requires it.
Email ouroborosplugins@gmail.com to export, correct, or delete what we hold. Include the account reference from the trial page if you have one. An export is the subscription snapshot: account id, Stripe customer id, subscription id, status, period end, and plan interval. Papers has no query log to include. Deletion removes that snapshot from the store we operate. Backups held by a provider, Stripe’s records, logs at the scholarly sources, and the copy your AI host kept follow those providers’ retention. Disconnecting the assistant stops new tool calls. Canceling a subscription does not by itself delete the snapshot.
Children's privacy
Papers is not directed to children under 13, and we do not knowingly collect personal information from them. A connection creates a random account id and does not ask for a date of birth. If you believe a child has used Papers, email ouroborosplugins@gmail.com and we will delete the snapshot we can tie to that request.
Security and changes
Tokens are signed, and the account cookie is HttpOnly. No service can promise absolute security. We publish changes to this policy on this page with a new effective date. If local privacy law gives you additional rights, you may exercise them by emailing ouroborosplugins@gmail.com.
Contact
Papers by Ouroboros Apps
ouroborosapps.com
ouroborosplugins@gmail.com