Trove

Privacy Policy

Last updated: November 2026

1. About Trove and This Privacy Policy

Trove (formerly CandleKeep) is an online service operated by Hey Trove Ltd. (company number 517408266) and its affiliates (collectively, “Trove”, “HeyTrove”, “we”, “us” or “our”). For any privacy-related questions or requests, you can reach our data protection contact at privacy@heytrove.ai.

Depending on the relevant processing activity, Trove may act as an independent controller or, where expressly agreed with an organizational customer, as a processor. This Privacy Policy applies to personal data that Trove processes as a controller. Where Trove processes personal data on behalf of an organizational customer as a processor, that customer determines the purposes and means of the processing, and its privacy policy applies to that processing.

2. What We Collect

We collect the following categories of personal data:

  • Account data — provided via our sign-in provider (Clerk): name, email address, profile image, and sign-in metadata such as IP address and device. If you sign up with a Google or GitHub account, that account shares your name, email address and profile image with Clerk.
  • Time zone — the time zone your browser reports, stored on your account and updated when your browser reports a different one. We use it to send our emails in your local morning and the weekly recap on your local day. It is deleted with your account.
  • Uploaded documents — PDFs, EPUBs, and Markdown files you add to your library, along with associated metadata.
  • Usage data — page views, reading records, API usage records, feature usage and interaction events. Before you answer the cookie banner, your browser sends PostHog only anonymous, cookieless counts; analytics linked to you run only with your consent. See Cookies & Analytics. Some events are sent by our servers instead, for example sign-up and onboarding steps, plan and trial changes, signing in from the CLI, plan-limit hits, emails we send you and connecting an assistant. They follow the same choice.
  • Coding agent — when you use the Trove CLI, we record the name of the coding agent that runs it (for example “Claude Code” or “Codex”). We use the name to know which agents to support. Each call from the CLI also has a session key. The CLI makes this key on your computer with a one-way hash of the session ID of your agent. The session ID stays on your computer. We hash the key again with your account, so nobody can link it to the same session in a different account. We use the key to count the agent sessions that use Trove. The Trove dashboard in Claude Code also sends small counts, for example how many books it read for a task, how many notes it gave your agent, how many of these notes your agent used, which book pages your agent used, and the kind of each book it read (whether it is your own material, and its field of work). When an app connects to Trove through MCP, we record a short label for the type of app (for example “Claude” or “ChatGPT”), not the full name that the app sends. None of this data contains your prompts, files, commands or book text. To stop it for your account, turn off the “Share which coding agent you use” switch in Settings. To stop what the CLI sends from one computer, set TROVE_NO_CLIENT_TELEMETRY=1 (the older CK_NO_CLIENT_TELEMETRY=1 also works) in your environment. The “Usage data” switch in the dashboard’s Settings stops the session key and the dashboard counts.
  • Your machines — the Trove CLI reports each machine you use it on: a random machine ID it creates, the CLI version, which coding agents it found, whether Trove is installed in each and how, and when the machine last reported. The machine's hostname and operating system are stored only while the “Share which coding agent you use” setting is on; turning it off clears the stored hostname and operating system. You see this list on the Agents tab in Settings. We keep at most 20 machines per account.
  • How you heard about us — the answer you pick during onboarding, and any detail you type, stored on your account.
  • Survey answers — answers you gave to earlier in-app surveys (we no longer show them), kept on your account.
  • Newsletter and waitlist sign-ups — your email address, where you signed up, and any reason or comment you leave when you unsubscribe.
  • Trove Experts applications: when you apply on our Trove Experts page, your name, email address, what you create, and any links and notes you add. If you leave your email as a publisher, only your email address. We use it only to read your application and reply to you. Our team receives it by email, sent through Resend, and as an alert in our internal Slack. We keep it until you ask us to delete it or you delete your Trove account. The copies in our team's inbox and Slack are removed when you ask us (see Data Retention).
  • Error reports — when a page or request fails, the error, the page address (including any query string), the route and the request method. Billing errors are scrubbed of personal details first.
  • Session recordings — only if you accept analytics cookies, PostHog records how you move through the web app (clicks, scrolling, page changes) so we can find bugs. Everything you type into form fields is masked, and recordings are deleted after 30 days.
  • Support requests — what you send us through the in-app feedback form, trove report, or email: your message, any attachments, and your email address.
  • Assistant connections — if you connect Trove to an AI assistant, we store the connection details described in Connecting Trove to AI Assistants.
  • Device & browser info — browser type, operating system and screen size, sent with the anonymous counts before you choose and with your analytics after you accept.
  • How you signed up — whether you created your account on our website, with the trove command in a terminal, or through an AI assistant connection, and which assistant. We keep it with your account to understand how people start using Trove. It uses no cookie, so we record it whatever you answer on the cookie banner.
  • Technical identifiers — IP addresses and user agent strings may be collected for download tracking, abuse prevention and, if you accept analytics, analytics. IP addresses are not displayed in our admin interface and are used only for deduplication and security purposes. If you accept analytics, we derive your country from your IP address at sign-up; the IP address is not stored.
  • Billing data — email address and subscription status, processed by our billing provider (Polar). We do not store payment card details directly; these are handled by Polar's payment processor.
  • Service usage logs — records of which library items you access, pages read, and API calls made. These are used to enforce usage limits, provide reading history, and improve the service.
  • Book reading ledger — when your agent reads passages from a book for sale on Trove, we record which book, the passage reference (chapter and page), how many characters were served, the time, which agent client asked, and the research session. We use this to enforce plan limits, to prevent abuse, and in the future to price usage and pay authors. See Data Retention.
  • Research topics supplied by your agent — when you use Trove through a coding agent or through the Trove connector in a chat app such as Claude or ChatGPT, the agent writes three short pieces of text on your behalf:
    • A one-line topic for a research session — kept so we can group a run of reads together. Up to 500 characters. The topic is removed after 90 days; the record that a session happened stays.
    • The topic of a question your library could not answer — kept so we know which book to publish next. While the report is still linked to your account, we can tell you when a book on it exists; once the link is removed (see Data Retention), we cannot. Up to 1,000 characters.
    • The reason a book was suggested to you — kept so we do not suggest the same book twice. Up to 1,000 characters.
    We do not store your conversation with the agent: no transcript, no prompt stream, no message history. Research topics and book suggestions pass through a pattern-based, best-effort filter designed to identify and redact recognizable email addresses, API keys, access tokens and phone numbers before storage. The filter may not identify every item of personal data.

3. Lawful Basis for Processing (GDPR Art. 6)

  • Contract performance — processing your account data and documents is necessary to provide the Trove service you signed up for.
  • Legal obligation — we process personal data where necessary to comply with applicable legal obligations, including tax, accounting and regulatory requirements, and to respond to legally binding requests.
  • Consent — where required by applicable law, we will ask for your consent before using cookies or similar technologies: analytics cookies, session recordings, Google Analytics, the “how you found us” cookie, and server events linked to your account. Cookies that require consent will be activated only after you provide your consent.
  • Legitimate interest — security monitoring and abuse prevention; anonymous, cookieless counts from your browser and our servers before you answer the cookie banner; linking your CLI install to your account in our own database (see Cookies & Analytics); error reports that keep Trove working; and reading and replying to the Trove Experts applications you send us, which is what you ask us to do when you apply.

Where applicable, we rely on our legitimate interests to administer our business, communicate with users, maintain records, improve and secure the Service, prevent fraud and abuse, and establish, exercise or defend legal claims, provided that those interests are not overridden by your interests or fundamental rights and freedoms. Where consent is required for newsletters, waitlists or other marketing communications, we rely on your consent, which you may withdraw at any time.

4. How We Use Your Data

  • To provide and maintain the Trove service
  • To authenticate you and manage your account
  • To process, store, and serve your uploaded documents
  • To monitor and protect the security of our infrastructure
  • To improve the product through analytics (with your consent; before you answer, only anonymous counts)
  • To enforce usage limits and subscription tiers
  • To track downloads and prevent abuse
  • To answer support requests
  • To read and reply to Trove Experts applications
  • To keep the AI assistants you connect working (see Connecting Trove to AI Assistants)
  • To find and fix bugs (session recordings, with your consent)

5. Connecting Trove to AI Assistants

You can connect Trove to AI assistants such as Claude and ChatGPT, or to any other app that supports MCP. You sign in to Trove and approve the connection (OAuth). After that, the assistant can read and add to your library for you.

Where you choose and connect an AI assistant, that provider operates under its own terms and privacy policy and generally acts independently of Trove with respect to your interactions with that service.

What we receive and keep:

  • An access token and a refresh token. We store only a scrambled form (a one-way hash), never the token itself. An access token stops working after 1 hour. A refresh token stops working after 30 days unless the assistant uses it, and each use replaces it with a new one.
  • The name the assistant app gives itself when it registers (for example, “ChatGPT”). We use it to show which assistants are connected.
  • A short label for the type of app, for example “Claude”, “ChatGPT” or “Cursor”. We make it from the name that the app sends when it connects, and we do not keep that name. While the “Share which coding agent you use” switch in Settings is on, we keep the label on your usage and reading records, and for an API key also with the key. If you turn the switch off, we clear the label on the key at your next call. We use it to know which apps to support.
  • The requests the assistant makes for you: which tool it used, which books and pages it read, what it saved, and when it last used its access. These are the same usage and reading records we keep when you use the Trove CLI.
  • Any short research topic, missing-topic note or suggestion reason the assistant writes, as described in What We Collect.

What we do not receive: your conversation with the assistant. We never get your chat history, your prompts, or the assistant’s answers. We only see the requests it sends to Trove.

The assistant’s own privacy policy (for example, OpenAI’s for ChatGPT, or Anthropic’s for Claude) covers your conversation and anything the assistant does with what it reads from Trove. These companies are not our processors when you connect them: you choose to connect them, and they act under their own terms. (Separately, our staff use Anthropic’s Claude for the internal tools described in Who Receives Your Data.)

To disconnect: remove or disconnect Trove in the assistant’s own settings. Settings in Trove shows which assistants are connected. The access token we issued expires within 1 hour. To end a connection right away on our side, email support@heytrove.ai and we will revoke it as soon as we can. Deleting your Trove account removes all connections.

6. No Model Training

We don't train models on your content and we don't use it to train anyone else's. The documents you upload, the books you write, and the text your agent reads from your library are never used to train or fine-tune any model — ours or a third party's. Our servers never send your documents or your agent's questions to any AI model provider. Your content is processed only to operate the service for you.

Authorized personnel may use third-party AI tools, including Anthropic Claude, to assist with limited support, engineering, operational and administrative activities. Depending on the task, those tools may access account or library records. We seek to limit the information disclosed to what is reasonably necessary, apply appropriate access controls and safeguards, and do not permit customer content to be used for model training (see Who Receives Your Data).

7. Cookies & Analytics

Cookies set before you choose — only sign-in cookies (set by Clerk), which the service needs to work, and a timezone preference cookie (ck-tz, 1 year). Once you answer the cookie banner we also keep a note of that answer in a cookie (ck-consent, 1 year), which the service needs to honour it. We set no analytics or marketing cookies before you accept.

Analytics cookies (client-side) — we use PostHog for product analytics. Until you answer the cookie banner, PostHog counts visits and product events (for example page views, which feature you opened, and when you leave a page) anonymously and without cookies: the page address (including campaign tags such as utm_source), the referring site, and browser and device type, with no profile. Your browser keeps only a note of your cookie choice and that analytics are not yet on, plus the per-tab note of how you found us described below. If you accept, we use cookie-based analytics, Google Analytics, session recordings and the “how you found us” cookie described below. If you reject, or your browser sends a Global Privacy Control signal, your browser sends no analytics at all. We ask again after six months, whatever you answered, and when this policy changes. Withdrawing consent is as simple as changing your cookie preferences — no account changes required.

Remembering how you found us — before you choose, the note of how you arrived stays only in your browser, in a per-tab value that disappears when the tab closes. It holds the campaign tags in the link (such as utm_source), the referring site and advertising click identifiers.

If you accept analytics, we store it in a first-party cookie called ck-first-touch (30 days, not readable by scripts). If your account is less than a week old and has no source yet, we also store it on your account.

If you reject, or your browser sends a Global Privacy Control signal, we receive and store nothing, and we remove the cookie. The per-tab value stays only in your browser until you close the tab. Older visits may carry a cookie called ck-utm; we delete it when we see it.

Events our servers send — some product events are sent by our servers rather than your browser. They follow your cookie choice:

  • if you accepted, they are linked to your account;
  • if you have not answered yet (or your answer is more than six months old, or was given under an earlier version of this policy), they are sent as anonymous counts, with a random identifier, no profile and no email address;
  • if you rejected while signed in, or your browser sends Global Privacy Control, none are sent.

Events from visitors who are not signed in, and steps reported by our install script, are sent only as anonymous counts, and none are sent if your browser sends Global Privacy Control. A Reject made while you are signed out is stored in your browser only, so it does not stop these anonymous counts; Global Privacy Control does. The install scripts say so on screen before they send anything. When you run them with DO_NOT_TRACK=1 or TROVE_NO_TELEMETRY=1 set, neither the scripts nor the Trove CLI they install send these events, and no install id is saved, so nothing links the install to your account.

Linking the CLI to your account — when you sign in to the Trove CLI, we link that install's anonymous install record to your account so we can see whether installs turn into use. We always record this link in our own database, under our legitimate interest. We also send it to PostHog, unless you rejected analytics or your browser sends Global Privacy Control. To object, email privacy@heytrove.ai.

Error reports — when something fails, our servers always send an error report to PostHog under our legitimate interest in keeping Trove working. It is linked to you only if you accepted analytics cookies.

You can change your choice at any time with the “Cookie preferences” link in the site footer (also at the bottom of this page), or with the “Product analytics” toggle in the Privacy card on the Account tab of Settings. If your browser sends Global Privacy Control, analytics stay off and the link only tells you so.

8. Automated Decision-Making

Trove does not use automated decision-making or profiling that produces legal effects or similarly significant effects on you. Document processing (e.g., PDF text extraction) is purely mechanical and does not involve profiling or algorithmic decision-making about individuals.

9. Your Rights (GDPR)

If you are located in the European Economic Area (EEA) or a jurisdiction that grants equivalent rights, you have the following rights under the General Data Protection Regulation:

  • Access (Art. 15) — request a copy of the personal data we hold about you.
  • Rectification (Art. 16) — request correction of inaccurate or incomplete data.
  • Erasure (Art. 17) — request deletion of your personal data ("right to be forgotten").
  • Restriction (Art. 18) — request that we limit the processing of your data.
  • Portability (Art. 20) — receive your data in a structured, machine-readable format.
  • Objection (Art. 21) — object to processing based on legitimate interests, including the CLI account link and the anonymous counts described in Cookies & Analytics.
  • Withdraw consent (Art. 7(3)) — withdraw consent for specific cookies at any time via the “Cookie preferences” link in the site footer or the “Product analytics” toggle in the Privacy card on the Account tab of Settings, and for marketing emails in the Email tab of Settings or with the unsubscribe link in any such email, when relevant.
  • Lodge a complaint — if the GDPR applies to the processing of your personal data, you have the right to lodge a complaint with a competent supervisory authority, in particular in the EEA country of your habitual residence, place of work or the place of the alleged infringement.

We will respond to all data subject requests within one calendar month. In complex cases, this may be extended by up to two additional months, in which case we will inform you of the extension and the reasons for the delay.

To exercise any of these rights, contact us at privacy@heytrove.ai.

10. Your Rights (CCPA)

If you are a California resident, the California Consumer Privacy Act grants you the following rights:

  • Right to know — request details about the categories and specific pieces of personal data we have collected.
  • Right to delete — request deletion of personal data we have collected from you.
  • Right to opt-out of sale — we do not sell your personal data to third parties.
  • Non-discrimination — we will not discriminate against you for exercising your CCPA rights.
  • Right to correct — request correction of inaccurate personal information we hold about you.

11. Data Retention

We keep each kind of data only as long as below. Where there is no fixed period, we say what decides it.

  • Account data (name, email, profile image) — until you delete your account. When you delete it, we delete your account record and everything linked to it straight away. Files (documents, covers, support attachments) are deleted right after; an account with a very large number of files can take longer, and we keep deleting until all are gone. If a deletion fails we retry automatically.
  • Sign-in data (Clerk) — until you delete your account. You delete your account from the Account tab in Settings, which removes your Clerk user (our sign-in provider) and erases your data with us. Clerk keeps sign-in data under its own privacy policy and sets no fixed period of its own.
  • Books and documents — until you delete them or your account. When you delete your account, we delete your files from storage, including covers you set and covers we generated, and your library from our database.
  • Reading and usage records (API usage, research sessions, reads, session keys and dashboard task counts, the pages your agent used and the kind of each book) — until you delete your account. Research topics are removed after 90 days. Reads of books owned by other people (for example, marketplace books) are kept as anonymous counts after you delete your account, with your identity, the session key and the app label removed.
  • Book reading ledger — kept for 24 months, then deleted. When you delete your account, your ledger is deleted at once. It is not kept as anonymous counts.
  • Missing-topic reports — reports of topics your library could not answer are kept so we can plan new books. After 90 days we keep the topic text but remove the link to you, except for reports in a book we are still planning, which stay linked until that work closes. Once the link is removed, we cannot tell you when a book on that topic exists. Deleting your account removes the link straight away.
  • Book suggestions — the reason a book was suggested to you is deleted after 90 days. The suggested title and author are kept until you delete your account.
  • Analytics (PostHog) — session recordings are deleted after 30 days. Analytics events are kept for up to 7 years, the limit of our PostHog plan, so we can compare how Trove is used over time. PostHog stores IP addresses in anonymised form.
  • Before you answer the cookie banner — visitors are counted without cookies; session recordings and cookie-based analytics start only after you accept. You can stop analytics at any time with the “Cookie preferences” link in the footer.
  • Analytics after you delete your account — we ask PostHog to delete your analytics profile with its events and recordings. This normally completes within days. Anonymous counts cannot be linked to you and are kept.
  • Machines and onboarding answers — your machine list, your “how did you hear about us” answer and past survey answers are deleted with your account.
  • Newsletter and waitlist — deleted when you delete your account, together with any unsubscribe feedback given with the same email address.
  • Trove Experts applications: kept until you ask us to delete your application or you delete your Trove account (we then delete the applications sent with that account's email address). Deleting an application also empties it from our email log. When you ask us, we also delete the copies in our team's inbox and in our internal Slack alert. Resend, our email provider, keeps its own delivery records for its own retention period. To ask, email privacy@heytrove.ai.
  • Google Analytics — kept for 14 months, then deleted by Google, and only collected if you accept analytics cookies.
  • Server logs (Railway) — deleted automatically by our hosting provider within 30 days.
  • Database backups (Railway) — Railway keeps daily backups of our database. Deleted data stays in a backup until that backup expires.
  • Billing records (Polar) — Polar is the seller of record for Trove subscriptions. Polar keeps billing records under its own privacy policy and for as long as tax and accounting law requires. We delete our copy of your subscription when you delete your account.
  • Assistant connections and API keys — tokens and keys are stored only in hashed form. Access tokens stop working after 1 hour; refresh tokens after 30 days without use; API keys when you revoke them. The hashed records are deleted with your account.
  • Support messages — requests you send in Trove are deleted with your account. Copies in our support tools (Linear, and our internal team alerts) and emails sent to support@heytrove.ai are kept so we can follow up on your request, and deleted within 30 days of you asking us to delete them.
  • Email records — we keep a record that an email was sent and whether it was delivered. When you delete your account, your address and the email's content are removed from these records; the record keeps the template name, delivery status, timestamps and our email provider's message ID. Our email provider (Resend) keeps its own delivery logs under its own terms. If you unsubscribed, or our emails to you bounced or were marked as spam, your address stays on our email provider's do-not-send list after you delete your account, so we never email you again.
  • Install and download records — new records are stored with an anonymised IP address; some older download records may hold the full address, and we delete them if you ask. Your account link is removed when you delete your account.
  • DMCA records — records of copyright takedown notices and counter-notices are retained for a minimum of 3 years to support repeat infringer tracking and legal compliance.

Certain audit, security, compliance, fraud-prevention, billing, operational and legal records may be retained after account deletion where reasonably necessary to maintain the security and integrity of the Service, comply with legal obligations, establish or defend legal claims, or prevent abuse.

When you delete your account, we also delete your marketplace listings and the books you shared with a team. We keep:

  • the administrative audit log;
  • anonymous reading counts on books owned by other people;
  • missing-topic reports, without any link to you;
  • email delivery records, with your address and the email content removed;
  • billing-issue records, with your billing email removed (they keep internal account and payment-provider IDs);
  • payment-webhook records, with your account and payment-provider customer IDs removed;
  • CLI install records, without the link to your account;
  • team-invite records that are no longer pending;
  • copies our vendors keep under their own terms (see above);
  • Railway logs and backups, until they expire.

12. Your Choices

  • Analytics and session recordings — change them with the “Cookie preferences” link in the footer or the “Product analytics” toggle in the Privacy card on the Account tab of Settings. We honour Global Privacy Control.
  • Coding agent name, session key and dashboard counts — turn them off for your account with the “Share which coding agent you use” switch in the Privacy card in Settings. This switch also keeps the app label off your MCP usage records. On one computer, set TROVE_NO_CLIENT_TELEMETRY=1. The “Usage data” switch in the Trove dashboard in Claude Code stops the session key and the dashboard counts.
  • Product emails — manage them in the Email tab in Settings.
  • Connected assistants — disconnect in the assistant, or email support@heytrove.ai and we will end the connection on our side.
  • Books — delete any book from your library.
  • Account — delete it from the Account tab in Settings. If you cannot find the control, email privacy@heytrove.ai.
  • Access, export or correction — email privacy@heytrove.ai. We answer within one month.

13. International Data Transfers

Your data may be processed outside your country of residence. Each transfer relies on the provider's standard data processing terms and transfer mechanisms:

  • PostHog — EU (Frankfurt). Data is stored in the EU. PostHog is a US company, so any access from outside the EU is subject to PostHog's data processing terms.
  • Clerk — US. Transfers are subject to Clerk's data processing terms and transfer mechanisms.
  • Railway — EU (Amsterdam, Netherlands). Our servers and database run in Railway's EU region. Railway is a US company, so any access from outside the EU is subject to Railway's data processing terms and transfer mechanisms.
  • Tigris Data — EU (Amsterdam, Netherlands). Stores uploaded files behind Railway Buckets. Tigris is a US company, so the same applies.
  • Polar — merchant of record for subscription billing. Payment data is handled by Polar's payment processor under Polar's terms.
  • Cloudflare — Global. DNS, reverse proxy, CDN and TLS for all traffic to Trove, and email routing. It sees IP addresses and the content of requests and responses in transit.
  • Resend — US. Transactional email delivery.
  • Google Analytics — US. Website analytics, only with your consent.
  • Linear — US. Support request tracking.
  • Slack: US. Internal team alerts about signups, billing, support requests and Trove Experts applications (see the Vendor List page).
  • Anthropic — US. Used for certain internal operational, support, engineering and administrative functions (see Who Receives Your Data).

Where applicable, international transfers are made subject to transfer mechanisms made available by the relevant provider, which may include adequacy decisions, the EU-US Data Privacy Framework, or Standard Contractual Clauses. For details, contact privacy@heytrove.ai.

14. Data Storage & Security

We implement appropriate technical and organizational measures to protect your personal data:

  • Encryption in transit — TLS 1.2 or higher, terminated at Cloudflare.
  • Encryption at rest — the database and file storage are encrypted at rest by our hosting providers.

For more details on our security practices, see our Security page.

15. Who Receives Your Data

  • Service providers (processors) — we share data with a limited number of third-party service providers who process data on our behalf, including for hosting and storage, authentication, analytics, billing, email delivery, support tracking, infrastructure, communications, and internal administration. Most are bound by their standard data processing terms; the Vendor List shows the ones that are not yet. For the full list, including purposes and locations, see our Vendor List page. Our servers never send your documents or your agent's questions to any AI model provider. Text extraction runs on our own servers.
  • Anthropic, for staff tools — our staff use Anthropic's Claude in internal admin tools to review books submitted to the marketplace and to analyse reports of topics libraries could not answer. Staff also use Claude Code for engineering and support work, which can read production data, including account and library records. Staff use Claude on an individual Claude Max plan with the setting that lets Anthropic train on chats turned off. Anthropic's consumer terms apply, which do not include a data processing agreement. We plan to move to Claude Team, which does.
  • People you share with — members of a team you share books with can see those books. If your assistant reports that a marketplace book is missing a topic, that book's author sees the topic (not who you are).
  • Trove Experts applications: each application reaches our team by email, sent through Resend, and as an alert in our internal Slack.
  • AI assistants you connect — these are not our processors. You choose to connect them (see Connecting Trove to AI Assistants).
  • Legal requests — when the law requires it.

16. Children's Privacy

You must be at least 16 years old, or the minimum age required in your country to consent to use the Service and accept the Terms of Service, whichever is higher. If you are under 18, you must have your parent or legal guardian's permission to use the Service. We do not knowingly collect personal data from children. If we learn that personal data was collected from a child contrary to applicable law, we will take appropriate steps to manage this data.

17. Changes to This Policy

We may update this Privacy Policy from time to time. For material changes, we will tell you by email or in the app before the changes take effect. Continued use of the service after the effective date constitutes acceptance of the updated policy.

18. Data Provision Requirements

Providing the data, including your email address and document uploads, is a contractual requirement necessary to create and maintain your Trove account. Without this data, we cannot provide the service.

Applying to Trove Experts is optional. To consider your application and reply, we need your email address and, for an expert application, your name and what you create.

19. Contact

For any privacy-related questions, data requests, or concerns, contact us at privacy@heytrove.ai.

For help with your account, email support@heytrove.ai.