Privacy Policy

RoyaltyMiner AI is the controller of the personal data described here. Contact us about anything on this page at support@royaltyminerai.com.

Your account. Your name, your email address, and your password — stored only as a cryptographic hash, never as text we could read. If you turn on two-factor authentication we store the encrypted secret and your encrypted recovery codes; if you register a passkey we store its public credential. Email verification is not currently required to use the Service.

What you put in your workspace. The books and keywords you track, your research projects, notes, pen names, series, alert rules, and reports.

How you use the Service. A record of metered actions — research requests, exports — with the time, what it cost us to serve, and whether it was answered from data already collected. This is how plan limits are enforced and how we know the business is viable.

Activity in a shared workspace. An append-only log of actions that change access, money, or data — who invited whom, who changed a role, who changed the plan — so a team can answer those questions months later. It never records credentials or payment details.

Technical data. Your session record holds your IP address and browser user agent. Our servers keep ordinary access and error logs, which may contain an IP address.

Billing. If you subscribe, we store a Stripe customer reference, your subscription status, and the card type and last four digits. Card numbers go directly to Stripe and never reach our servers.

• Your Amazon or KDP credentials. The Service never connects to your seller account.
• Your sales, royalties, or advertising data. We could not obtain it if we wanted to.
• Advertising or cross-site tracking data. There are no third-party analytics, no advertising pixels, and no tracking scripts on this site or in the application.

We do not sell personal data, and we do not share it for anyone else's marketing.

Most of what the Service stores is observations of public Amazon pages — titles, prices, ranks, ratings, review counts, and how they change. That record is about the market, not about you, and it is shared across customers: the same observation may answer another workspace's question. Which searches you ran is private to your workspace.

• To provide the Service — running your searches, tracking your books, sending the alerts and reports you asked for. This is necessary to perform our contract with you.
• To keep it secure and affordable — enforcing plan limits, detecting abuse, understanding collection cost. These are our legitimate interests, and we use the least identifying data that works.
• To meet legal obligations — keeping the tax and accounting records a business must keep.

We send transactional email only: password resets, security notices, workspace invitations, alert digests, and the weekly report. We do not send marketing email without asking first, and any such consent can be withdrawn at any time.

We use a session cookie to keep you signed in, a cross-site request forgery token to keep forms safe, and — only if you choose "remember me" — a long-lived sign-in cookie. All are strictly necessary, which is why you are not asked to consent to a banner full of things you would refuse.

Your light or dark theme preference is kept in your browser's local storage and is never sent to us.

We use a small number of processors, each bound to handle data only on our instructions:

• Stripe — payments and subscriptions. Stripe receives your card details and billing information directly.
• Our email provider — delivering the transactional messages above, which requires your email address.
• Our hosting and backup providers — running the servers and holding encrypted database backups.
• AI model providers — Anthropic, OpenAI, Google, or DeepSeek — when you use a feature that writes or reads text for you. Drafting a concept, planning or writing a book, analysing a transcript, and generating cover art each send the material that feature works from — your answers to the wizard, your manuscript or transcript, your cover brief — to one of these providers. Which one serves a given request is our routing decision, never based on who you are, and your name and email are not sent with it.
• Speech providers — Fish Audio and Speechify — when you have a passage read aloud. The provider receives the text of the passage, which for a book chapter is the chapter.

One thing worth knowing: the account menu shows a Gravatar avatar, which means your browser requests an image from gravatar.com using a hash of your email address. A hashed email address is still personal data, and that request also carries your IP address to Automattic, who operate Gravatar. It is the only third-party request any page makes.

Collecting market data involves requesting public Amazon pages through proxy infrastructure operated by Evomi. Those requests carry nothing that identifies you: which customer asked is never sent with them. The same is true when we fetch the public captions of a YouTube video you have linked — the request names the video, not you.

• Your account and workspace content — for as long as the account exists.
• Historical readings you can see — set by your plan, currently 30 days on Trial, 180 days on Author, 365 days on Publisher and 730 days on Studio. Changing plan changes how far back you can look; it does not delete what has been collected.
• Usage and activity records — kept while the workspace exists, because they are what a shared account and a disputed invoice are settled from.
• Encrypted database backups — the 14 most recent dumps, after which the oldest is destroyed. Data you delete can persist in a backup until it is pruned.
• Invoices and tax records — for as long as tax law requires, which is longer than your account.

Ask us to close your account and we will delete your personal data and workspace content within 30 days, apart from what we must keep by law. Observations of public Amazon pages are not personal data and remain part of the shared market record.

Depending on where you live, you have the right to see the personal data we hold about you, to have it corrected, to have it deleted, to object to or restrict how we use it, to receive a copy in a portable form, and to withdraw any consent you have given.

Email support@royaltyminerai.com and we will respond within 30 days. We will not charge you for exercising a right, and we will not treat you differently for having done so.

If you are in the UK or the EEA and you think we have handled your data badly, you may complain to your national data protection authority. We would rather you told us first.

• Passwords are stored as salted hashes and cannot be recovered, only reset.
• Two-factor authentication and passkeys are available to every account, on every plan.
• Traffic is encrypted in transit, and database backups are encrypted at rest.
• Workspace separation is enforced in the data layer rather than in the interface, so a query cannot reach another workspace's records by mistake.
• Changes to access, money, and data are written to an append-only log.
• Backups are restored into a scratch database weekly and checked, because a backup nobody has restored is only a hypothesis.

No system is perfectly secure. If we discover a breach affecting your personal data we will tell you and the relevant authority as the law requires, without hiding behind vagueness about what happened.

The hosting region for this deployment has not been published yet. Some processors, such as Stripe, operate internationally; where data leaves your region we rely on the safeguards those providers offer, including standard contractual clauses.

The Service is a business tool and is not intended for anyone under 16. We do not knowingly collect data from children, and will delete it if we learn we have.

The date at the top of this page always reflects the current version. We will tell you by email or in the application before a change that materially affects how we handle your data takes effect.