Legal
Privacy Policy
Last updated: 2026-11-05
Summary
- ✓We collect only what's necessary to provide the service
- ✓Your citations and library data belong to you
- ✓We don't sell your personal data
- ✓You can export or delete your data at any time
- ✓LGPD (Brazil) and GDPR (EU) compliant
CiteMe ("we", "us", or "our") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our website, ChatGPT app, browser extension, Google Docs™ add-on, and related services.
This policy complies with the Brazilian General Data Protection Law (LGPD - Lei 13.709/2018) and the European General Data Protection Regulation (GDPR).
1. Data Controller
CiteMe is operated by DANIEL JYOJI NICHIATA LTDA, the data controller responsible for your personal data, based in Marília, São Paulo, Brazil.
Data Protection Contact: privacy@citeme.app
2. Data We Collect
2.1 Information You Provide
- Account Information: Email address, name (optional), profile picture (if using Google OAuth)
- Library Data: Citations you save, projects you create, formatting preferences
- Payment Information: Processed securely by Paddle; we do not store credit card numbers
- Communications: Support requests, feedback, and emails you send us
2.2 Information Collected Automatically
- Usage Data: Search queries, citation styles used, features accessed
- Purchase Attribution: When you open a checkout, we send Paddle and record with the purchase the kind of site your visit came from (for example a search engine, an AI assistant or a course platform) and the type of page it started on. We never record the address of either, and nothing is stored on your device for this
- Device Information: Browser type, operating system, screen resolution
- Log Data: IP address (hashed for privacy), timestamps, error logs
- Cookies and similar storage: Essential cookies for sign-in and preferences, and analytics cookies only if you accept them (see Section 7)
2.3 Browser Extension Data
The CiteMe browser extension (available for Chrome, Edge, Firefox, and Safari):
- Does NOT read or store your browsing history
- Does NOT access page content except when you explicitly invoke it on the current page (the popup's DOI/ISBN detector, "Cite this page", "Check these references" on selected text, or "Check the references in this document" on a Google Doc). Detected identifiers and text you select for checking are processed only for that action.
- On a Google Doc, "Check the references in this document" reads the document open in your tab, with your own Google session, and keeps only its reference list (the lines after its References or Bibliography heading, up to an appendix). The rest of the document is discarded in the extension and never stored or sent.
- A reference list you check (pasted in the extension, selected on a page, or taken from a Google Doc) is handed to the CiteMe reference checker in a new tab through the extension's temporary storage, which is cleared when the checker receives it or after five minutes, and is then checked like a list pasted on our website.
- Stores local data on your device: recent searches, preferred style, quota usage, settings
- Sends citation queries to our servers only when you initiate a search or check
- Product analytics: the extension sends usage events from a fixed allowlist (e.g. popup opened, search performed, citation copied, style selected) together with the extension version and browser name. Each installation is identified by a random UUID generated on install. Events never include search query text, page content, citation content, or any content you select. If you are signed in to a CiteMe account, usage events may be associated with that account so we can understand product usage across devices; if you are not signed in, they remain pseudonymous.
- Your choice: on Chrome, Edge, and Safari analytics is ON by default, and you can turn it off at any time via "Share usage statistics" in the extension's Settings. On Firefox, analytics is OFF by default and only enabled if you opt in (via Firefox's data-consent prompt or the same setting). Turning the setting off stops analytics on every browser, including after a Firefox data-consent grant.
2.4 PDF Import & Reader
- PDF Identifier Scan (client-side): When we only need to identify a paper (DOI, ISBN, PMID, or title), the scan runs entirely in your browser. Only the extracted identifier is sent to our API.
- PDF Bibliography Extraction (server-side, not stored): For the PDF-to-BibTeX, PDF-to-RIS, PDF Citation Generator, Reference Checker, and the free
/readreader, your PDF is uploaded to our servers so our extraction service can parse the bibliography section. The PDF is discarded immediately after extraction — we never store the file itself. We do retain the extracted reference text in a processing cache for up to 90 days (so re-uploads of the same document are instant), and a SHA-256 fingerprint of the file — which cannot reconstruct it — for up to 12 months for quota accounting. For Word (.docx) files uploaded to the Reference Checker, the extracted text of the document is kept in a processing cache for up to 6 hours; the file itself is not stored. - PDF fallback processing: If our extraction service returns no references after a longer processing attempt (for example, for a scanned, image-only, or unusual-layout document), or if you explicitly request OCR, the file may be sent to Google's Gemini API solely for structured text extraction. The file is not stored afterwards. See our File Security page for the full file lifecycle.
- PDF Reader (Pro — stored upload): If you opt in to attach a PDF to a library item for in-app reading on a Pro plan, the file is uploaded and persisted in our secure cloud storage (Supabase Storage, encrypted at rest) against your monthly page quota. You can delete uploaded PDFs at any time from your library.
- Annotations and reading history you create are stored in your account and are never shared with third parties.
- When you delete your account, all uploaded PDFs are permanently deleted.
2.5 ChatGPT App Data
When you explicitly invoke CiteMe in ChatGPT, ChatGPT sends only the tool input needed for the task: a citation search query and style, citation metadata you ask us to format, or bibliography text you ask us to verify.
- The CiteMe app does not request your full ChatGPT conversation history, ChatGPT account credentials, payment information, or precise location.
- Search terms and bibliographic identifiers may be sent to scholarly data providers to find and verify sources. When local parsing is insufficient, bibliography text may be sent to Google's Gemini API or OpenAI's API for structured parsing.
- Reference-check results may be cached in our Redis infrastructure for up to six hours to improve reliability and avoid repeating the same processing. They are not published or added to a CiteMe account by the ChatGPT app.
- Anonymous abuse controls use a trusted network IP and MCP application or session identifiers. Tool-quota counters expire within 24 hours.
2.6 Google Docs™ Add-on Data
The CiteMe add-on for Google Docs™ checks the reference list of the document you open it in. It is a Google Apps Script™ add-on that sends data only to citeme.app. It requests these Google permissions:
- Current document (documents.currentonly): The add-on reads only the document you open it in, never your other documents or files. It reads that document's text inside Google Docs™ to find your reference list and show how many paragraphs it holds: when you open the sidebar, when you sign out, when you press "Try again" after the sidebar could not load, and again after each check. Nothing is sent to CiteMe at those times. It never edits, creates or deletes anything in your document.
- External requests (script.external_request): Document text is sent to citeme.app only when you run a check: when you click "Check references" or "Check selected text", or "Try again" after a check that did not finish. What is sent is the reference section the add-on found, or the text you selected (at most 48,000 bytes), plus your document's title, which becomes the label of the saved report. Nothing else from your document is sent.
- Your Google account (userinfo.email, openid): The first time, you choose "Continue with Google" in the sidebar. Google gives the add-on an identity token, which it sends to CiteMe to confirm who you are; it does the same later, when it needs a new CiteMe access token. We verify the token through Supabase's Google sign-in and do not store or log it. Your Google account's email address links the add-on to your CiteMe account: if you do not have one, a free account is created with that address, and we record that it was created through the add-on. The add-on does not request your name, profile picture or contacts.
- Menu and sidebar (script.container.ui): Shows the add-on's menu and sidebar in the document. This permission does not read or send any data.
What happens to your data, and how to disconnect:
- Kept in Apps Script: After you sign in, the add-on keeps a CiteMe access token, its expiry date and your account's email address in Apps Script's storage for your Google account, so every document you open shares one sign-in. Your document's text and Google's identity token are never kept there.
- Kept by CiteMe: The result of each check is saved as a private report in your CiteMe account, like every signed-in check on citeme.app. Only you can open it, from the link in the sidebar or under Recent checks, signed in to the same CiteMe account. The report's content (the references you sent and the results) is deleted after 30 days. A history entry (its label, which for the add-on is your document's title, the score, the number of references and the date) and a usage record of the check (when it ran and counts, never the text) are kept for up to 365 days. A copy of the result may stay in our cache for up to six hours. CiteMe also keeps a record of the add-on's access token, which expires after 180 days and is listed in Settings > Account (Integrations section) as "Google Docs add-on".
- Who processes it: A check from the add-on is processed like a check on citeme.app, by the service providers listed in Section 4 (hosting, database and sign-in, caching, parsing the reference text, the scholarly databases used to look references up, Brave Search for references that look like grey literature, and Typesafe for a second check that a matched record is the work you cited). The add-on adds no provider of its own. We do not use this data for advertising and we do not sell it (see Section 3).
- Disconnecting: Choose "Sign out" in the sidebar and the add-on forgets the stored session, in every document. Then revoke the token in Settings > Account (Integrations section) on citeme.app; if you do not, it stops working on its own when it expires. Sign out first: while the add-on is still signed in, a check made after you revoke the token signs it in again and issues a new one. The same applies if you delete your CiteMe account (see Section 6): sign out in the add-on first, or the next check signs in again and creates a new account. To remove the add-on, uninstall it from Google Docs™ (Extensions > Add-ons > Manage add-ons); you can also withdraw its access in your Google account's settings for third-party apps.
CiteMe's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Our specific commitments are listed under "Google API Services User Data Policy" at the end of this page.
3. How We Use Your Data
We process your data based on the following legal grounds (LGPD Art. 7 / GDPR Art. 6):
3.1 Service Delivery (Contract Performance)
- Searching academic databases and formatting citations
- Saving and organizing your citation library
- Processing subscription payments
- Providing browser extension functionality for Chrome, Edge, Firefox, and Safari
- Providing citation search, formatting, and reference checking through the CiteMe ChatGPT app
- Providing reference checking through the CiteMe add-on for Google Docs™, when you ask for it
3.2 Legitimate Interest
- Improving search quality and citation accuracy
- Detecting and preventing abuse, fraud, and security threats
- Counting anonymous, aggregated interactions without cookies or any identifier (for example, how many visitors answer the cookie banner); PostHog discards the IP address of these events
- Recording account and purchase events on our servers (sign-up, checkout, payment, search summaries shown to signed-in users) to run and improve the service; you can object at privacy@citeme.app
- Error monitoring with Sentry, including a replay of the moments before an error on app pages with all text and media hidden
- Enforcing usage quotas and rate limits
3.3 Consent
- Sending optional product updates or feature announcements (you can opt out at any time)
- Analytics cookies and session recordings (Google Analytics, PostHog), only after you accept them in the cookie banner (see Section 7)
We do NOT use your data for advertising, profiling, automated decision-making, or selling to third parties.
4. Data Sharing & Third Parties
We share your data only with service providers necessary to operate CiteMe. We do not sell, rent, or trade your personal data.
| Provider | Purpose | Data Shared |
|---|---|---|
| Supabase | Database & authentication | Account info, library data |
| Vercel | Hosting & CDN | Request logs, IP addresses |
| Hetzner | Hosting for our PDF bibliography extraction server and our reference parser | Uploaded PDFs, and the reference text sent for parsing, during processing (transient, not stored) |
| Paddle | Payment processing; payment recovery and cancellation flows (Paddle Retain, loaded only for signed-in users and when you open a Paddle payment link to pay) | Email, payment details (handled by Paddle) |
| Upstash | Rate limiting & caching | Hashed IP addresses, usage counters, extracted text of Word uploads (up to 6 hours) |
| Google (Gemini API) | Search term extraction, bibliography parsing, result ranking & fallback PDF text extraction | User-submitted search or reference text; for PDF extraction fallbacks, the uploaded PDF file (not stored) |
| OpenAI (API) | Bibliography parsing & reference clean-up | Reference text you paste or that we extract from your upload; never the file itself |
| Academic APIs (OpenAlex, PubMed, etc.) | Citation data retrieval | Search terms, identifiers, and bibliographic metadata needed for lookup |
| Brave Search | Web search fallback when matching references (signed-in users only) | A reference's title, first author and year as a search query, only for references that look like grey literature (reports, theses, web pages) and were not found in the scholarly databases |
| Typesafe | Second identity check of matched references in the reference checker (signed-in users only) | A reference's text and the matched record's title, authors, year, venue, volume, issue, pages and identifiers (for a book, its publisher and page count), only for references found in the scholarly databases; processed in the United States under zero data retention (deleted as soon as it answers, not used for training) |
| Google Analytics (GA4) | Usage analytics (with consent) | Pages viewed and actions taken, device and browser data; never your account ID |
| PostHog | Product analytics and session recording (with consent); cookie-free aggregate counts | Pages viewed and actions taken, device data, session recordings on app pages with typed text hidden, and your account ID if you are signed in. The cookie-free counts carry no identifier and their IP address is discarded |
| Resend | Transactional email delivery | Email address |
| Sentry | Error monitoring (legitimate interest) | Error logs, stack traces (PII redacted); on app pages, a replay of the moments before an error with all text and media hidden |
| Cloudflare | Bot protection (Turnstile) on sign-in, sign-up and password-reset forms | Browser and device signals needed to tell people from bots |
| Google Sign-In | Signing in with Google, only if you choose it | Google loads its sign-in script and sets its own cookies on google.com |
We may also disclose your data if required by law, court order, or to protect our legal rights.
5. Data Retention
- Account data: Retained while your account is active. Deleted within 30 days of account deletion request.
- Library data (citations, projects): Retained while your account is active. You can delete individual items at any time or export your entire library.
- Usage logs: Aggregated usage statistics are retained indefinitely. Individual request logs (containing hashed IPs) are retained for up to 90 days.
- PDF extraction data: References extracted from an uploaded PDF are cached for up to 90 days. A SHA-256 fingerprint of the upload (which cannot reconstruct the file) is kept for up to 12 months for quota accounting. The uploaded file itself is never stored.
- Word (.docx) uploads to the Reference Checker: Extracted text is kept in a processing cache for up to 6 hours; the file itself is not stored.
- ChatGPT app reference checks: Tool inputs are not added to an account or published. Successful check results may remain in a performance cache for up to 6 hours.
- Saved reference reports (website and Google Docs™ add-on): Each signed-in check is saved as a private report. Its content (the references you submitted and the results) is deleted after 30 days. A history entry (label, score, number of references, date) and a usage record of the check (counts, never the text) are kept for up to 365 days, and a cached copy of the result for up to 6 hours. The add-on keeps its session in your Google account's Apps Script storage until you sign out; its access token expires after 180 days.
- Payment records: Retained as required by tax and accounting regulations (typically 5 years).
- Rate limit data: Hashed identifiers in Redis expire automatically within 1 hour to 30 days depending on the counter type.
6. Your Rights
Under LGPD (Art. 18) and GDPR (Arts. 15–22), you have the following rights:
- Access: Request a copy of all personal data we hold about you.
- Rectification: Correct inaccurate or incomplete personal data.
- Deletion: Request deletion of your account and all associated data. Available via Settings > Delete Account, or by emailing us.
- Portability: Export your citation library in BibTeX or RIS format at any time via Settings > Export.
- Restriction: Request that we limit processing of your data in certain circumstances.
- Objection: Object to processing based on legitimate interest.
- Consent withdrawal: Withdraw consent at any time where processing is based on consent (e.g., marketing emails or analytics cookies).
To exercise any of these rights, contact us at privacy@citeme.app. We will respond within 15 days (LGPD) or 30 days (GDPR).
You also have the right to lodge a complaint with your local data protection authority. In Brazil, this is the ANPD (Autoridade Nacional de Proteção de Dados). In the EU, contact your national supervisory authority.
7. Cookies and Similar Storage
We use essential cookies and browser storage that the service needs, and optional analytics cookies that are only set after you accept them in the cookie banner. Nothing optional loads before you answer.
7.1 Essential Cookies (always active)
| Cookie | Purpose | Duration |
|---|---|---|
| sb-*-auth-token | Supabase authentication session | Session / 1 year |
| preferred_locale, preferred_locale_source | Your language, so sign-in and payment pages keep it | 30 minutes; 1 year when you pick a language |
| citeme-cookie-consent | Stores your cookie preferences (localStorage) | 12 months (auto-expires) |
| citeme_*, citeme:* | Settings you choose and work in progress kept on your device (for example citation style, theme, recent searches, unsaved checks, and the page you were on before signing up so we can bring you back), in localStorage and sessionStorage | Until you clear them or they expire |
| __cf_bm (paddle.com) | Set by Paddle for bot protection when checkout or Paddle Retain loads | 30 minutes |
7.2 Analytics Cookies (consent required)
These cookies are only set if you accept analytics via our cookie banner. You can change your preference at any time.
| Cookie | Purpose | Duration |
|---|---|---|
| _ga, _ga_* | Google Analytics (GA4): page views and usage patterns | 2 years |
| ph_* | PostHog: product analytics and session recording (cookie and browser storage) | 1 year; the session part ends with the tab |
GA4 runs with Google Consent Mode v2 and advertising storage always denied. If you refuse or later withdraw consent, Google Analytics and PostHog stop sending data and we delete their cookies from citeme.app. You can change your choice at any time through the "Cookies" link in the footer or Settings → Privacy. We do not use advertising cookies.
8. International Data Transfers
CiteMe is operated from Brazil by DANIEL JYOJI NICHIATA LTDA (Rua Santa Cecilia 733, Marília, SP, Brazil; privacy@citeme.app). The providers in Section 4 process personal data on our behalf, only for the purposes listed there and for the periods in Section 5; none of them may use it for its own purposes. Several of them are outside Brazil. For each group, this is where the data goes and the mechanism of LGPD art. 33 that allows the transfer:
| Providers | Destination | Mechanism |
|---|---|---|
| Hetzner | Germany (European Union) | Adequacy: the ANPD recognizes the European Union as adequate (Resolution CD/ANPD 32/2026; LGPD art. 33 I) |
| Supabase, Vercel, Upstash, Resend, Paddle, Cloudflare (Turnstile), Google (Sign-In and Gemini API), OpenAI, Brave Search | United States and other countries where these providers operate | Necessary to perform our contract with you: the service you ask for cannot run without them (LGPD art. 33 IX, with art. 7 V). For the Gemini API, also the ANPD standard contractual clauses (Resolution CD/ANPD 19/2024) |
| Google Analytics, PostHog (analytics and session recording) | United States | Your specific consent in the cookie banner (LGPD art. 33 VIII). This section is the prior notice that these services process data in the United States; without your consent they do not load |
| Sentry (error monitoring), PostHog (cookie-free counts) | United States | The ANPD standard contractual clauses (Resolution CD/ANPD 19/2024), which we are putting in place with these providers. Neither stores your IP address nor receives your account ID |
Our providers also protect the data with encryption in transit (TLS) and at rest, access control, and certifications such as SOC 2 or ISO 27001. For visitors in the European Union, the European Commission recognizes Brazil as adequate (January 2026), and our providers in the United States rely on the EU standard contractual clauses in their data processing agreements.
You can ask for a copy of the standard contractual clauses we use, and we answer within 15 days. To exercise your rights (Section 6), write to privacy@citeme.app; you can also petition the ANPD.
9. Security
We implement industry-standard security measures to protect your data:
- All data transmitted over HTTPS (TLS 1.2+)
- Database-level row-level security (RLS) policies
- IP addresses are hashed before storage (never stored in plain text)
- Authentication tokens are securely managed via Supabase Auth
- Payment data is handled exclusively by Paddle (PCI DSS compliant)
- Rate limiting and abuse detection at multiple layers
No system is 100% secure. If you discover a security vulnerability, please report it responsibly to privacy@citeme.app.
10. Children's Privacy
CiteMe is not directed to children under 13 (or under 16 in the EU). We do not knowingly collect personal data from children. If you believe a child has provided us with personal data, please contact us at privacy@citeme.app and we will promptly delete it.
11. Changes to This Policy
We may update this Privacy Policy from time to time. When we make material changes, we will:
- Update the "Last updated" date at the top of this page
- Notify registered users via email for significant changes
- Display a notice on the website for at least 30 days
Continued use of CiteMe after changes take effect constitutes acceptance of the updated policy.
Google API Services User Data Policy
CiteMe's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically, CiteMe:
- Only uses Google user data to provide and improve user-facing features visible and prominent in the CiteMe application
- Does NOT transfer Google user data to third parties, except as necessary to provide the service, for security purposes, or to comply with applicable laws
- Does NOT use Google user data for advertising purposes
- Does NOT sell Google user data to any third party
- Does NOT use Google user data to train machine learning or AI models unrelated to providing the CiteMe service
Google Docs™ and Google Apps Script™ are trademarks of Google LLC.