Legal
Privacy Policy
Last updated
The short version
- We store what the service needs: your account, your projects, your scans and roasts, and your encrypted DataForSEO key.
- Your DataForSEO credentials are encrypted. Card numbers never reach us.
- One sign-in cookie. No advertising trackers. One page-view counter without cookies, for a contest we take part in.
- Report and roast links are public to anyone who has them. You can turn them off.
- Email us from your account address to get a copy of your data or delete it.
On this page
01Who is responsible
RankLLM.to is operated by its owner, who is responsible for the personal data described here. Write to support@rankllm.to for anything about your data.
02What we store
This is everything RankLLM.to keeps in its database about you and your work.
- Account
- Your email address, the name you enter, and a hash of your password. The password itself is never stored.scrypt, salted per password
- Pass and payment
- Which pass you own, the amount you paid, and the ids Stripe gives your customer record and your checkout.no card data
- DataForSEO credentials
- Your DataForSEO login and password, encrypted before they are saved. They are decrypted only on our server, right before a request to DataForSEO, and never sent to your browser.AES-256-GCM, key kept outside the database
- API key
- A hash of your key and its first characters, so you can recognise it in settings. The full key is shown to you once.SHA-256
- Projects
- Project name, domain, brand aliases, competitors, location, language, engines, schedule, sharing settings and your prompts.
- Scan results
- The answers each engine gave, the sources it cited, what we worked out from them (mentions, ranks, sentiment), the organic Google rank, the DataForSEO cost and the time of each scan.
- Prospect Roasts
- The prospect's name and domain, the competitor you chose, the generated prompts and the answers collected for them.
- White-label branding
- Agency name, logo address, brand colour, call-to-action text and link.
03What we never store
- Card numbers or bank details. They go straight to Stripe.
- Your password, your DataForSEO login or password in readable form, or your full API key.
- Password-reset links. They are signed, expire after 30 minutes and are not saved anywhere on our side.
04How we use it
To run the service you bought: sign you in, run the scans and roasts you start or schedule, show your reports, take your payment, reset your password and answer your emails.
We do not sell your data, show ads, or use your data to train AI models.
When you ask for prompt suggestions or create a Prospect Roast, our server opens the public homepage of the domain you entered and reads its title, description and headings. No other page of that site is requested.
05Who processes it
We use a few providers, each for one job. They only get what that job needs.
- Payments
- Stripe runs the checkout page and processes your card. It receives your email address and payment details under its own privacy policy. We only receive the result.stripe.com
- Data collection
- DataForSEO, on your own account, receives your prompts with their location and language settings, sends them to ChatGPT, Gemini, Perplexity and Google, and returns the answers.dataforseo.com
- Hosting and database
- Our hosting provider runs the app and keeps short-lived request logs. A managed PostgreSQL provider stores the database.
- Transactional email
- Only when email is enabled: Resend delivers password-reset emails and receives the address it sends to. We send no newsletters or marketing email.resend.com
- Revenue verification
- TrustMRR has read-only access to our Stripe account to publish our verified revenue. That access can include Stripe's payment records, such as the email on a payment. It does not include your projects, prompts or scan results.trustmrr.com
- Contest traffic check
- RankLLM.to takes part in the $100K Hackathon. Its organiser, Ship or Die, checks where each entrant's visitors come from. On our own pages a small script tells it which page was opened, the site the visit came from (its address only, never the full link), the utm_source and utm_medium of the link, and whether the link came from an ad click. It gets no account data and sets no cookie. It does not run on client report or roast pages, and it does nothing when your browser sends a Global Privacy Control signal.ship-or-die.com
Some of these providers work from the United States or other countries outside yours, under their own data-transfer safeguards.
07Images from other sites
Next to a domain, the app shows that site’s icon. Your browser loads it from Google’s favicon service, which receives the domain name and, like any web request, your IP address. No referrer is sent, so Google does not see which page you were on.
An agency logo on a client report or roast page is loaded by the visitor’s browser from the address the agency entered, in the same way and without a referrer.
08Public reports and roast pages
Every project has a client report link (/r/…). Sharing is on by default when you create a project. Anyone with the link can see the project name, domain, competitors, scan results, the full answers and the sources, and the agency branding. Turn sharing off in the project settings and the link stops working at once.
A Prospect Roast page (/roast/…) can be opened by anyone with its link until you delete the roast. It shows the prospect’s name and domain, the competitor, the prompts, the answers and your call to action.
Each link ends in a random code and is not listed anywhere, and we ask search engines not to index these pages. Anyone you send a link to can pass it on, so share it only with people who should see it. You can also replace a report link with a new one: the old link stops working.
09How long we keep it, and deletion
We keep your data while your account exists. You can delete parts of it yourself:
- Deleting a project removes its prompts, scans and results at once.
- Deleting a Prospect Roast removes it and its page.
- Removing your DataForSEO key or API key in settings deletes the stored credentials or hash.
To delete your whole account, email support@rankllm.to from the address on the account. We delete the account and everything linked to it within 30 days and confirm by email. Stripe keeps its payment records for as long as the law requires. Backups kept by our database provider roll over and drop deleted data after a short period.
10How we protect it
- All traffic uses HTTPS.
- Passwords are hashed with scrypt, a slow, memory-hard function, with a random salt for each password.
- DataForSEO credentials are encrypted with AES-256-GCM under a key that lives in the server environment, not in the database, and are decrypted only for the request that needs them.
- API keys are stored as SHA-256 hashes, so a copy of the database does not reveal them.
- Every request checks that the project, scan or roast belongs to the account asking for it.
- DataForSEO result callbacks are signed, so a forged callback is rejected.
11Your rights
You can ask to see the data we hold about you, get a copy of it, correct it, delete it, or object to how we use it. Email support@rankllm.to from the address on your account, so we know the request is yours. We answer within 30 days. You can change your name in the app yourself.
You can also complain to the data protection authority of your country.
RankLLM.to is a business tool and is not meant for children.
12Changes to this policy
When this policy changes, the date at the top changes too. If a change affects how your data is used, we tell you by email before it applies.