Privacy Policy
This policy explains what information RankYourBrand collects, why, and the choices you have. RankYourBrand is an answer-engine analytics product: the data we process is overwhelmingly about brands and public AI answers, not about individuals.
1. Who we are
RankYourBrand (“we”, “us”) is operated by PickDeploy Solutions LLC, a Wyoming limited liability company, at 5830 E 2nd St, Ste 7000 #38765, Casper, WY 82609, USA. For any privacy question, contact privacy@rankyourbrand.ai.
For the purposes of the GDPR, we act as a data controller for account and marketing information, and as a data processor for the workspace data you configure us to collect on your behalf (see our DPA).
2. Information we collect
Account information: your name, work email, password (stored only as a salted hash), and workspace settings, provided when you sign up.
Product data you configure: the brands, competitors, questions, and domains you ask us to track. This is business data, not personal data.
Answer and citation data: the answers AI platforms give to the questions you configure, and the citations within them. We collect these directly from the platform or through a data provider named in our list of subprocessors. We do not access private chat sessions or purchase session logs.
When you ask the assistant for a roadmap, we send that fix's question, the engines' answers to it, the addresses of the pages they cite, the names of the competitors you track, your business name, website, category and description, and the fix's suggested steps to our AI provider to produce the draft. A refinement also sends your instruction and the previous roadmap. Nothing else is sent.
First-party telemetry: when you install our snippet or server integration, we record AI crawler and referral activity on your own properties — the referring hostname, campaign tag, and path. No cookies, no cross-site tracking.
Usage and device information: standard server logs (IP address, browser type, pages viewed) used to operate and secure the service.
Website analytics: on our own site we count page views and visitors using a cookieless analytics service run by our hosting provider. It records the page, referrer, country, and device type. There are no cookies and no persistent identifier — visitors are counted using a value derived from the request that is discarded the same day — and no tracking across other sites.
How you found us: when you create an account, we keep where that visit came from — the campaign tags on the link you followed (such as utm_source), the website that referred you, and the first page you landed on. It is read from that visit only, never stored in your browser, and kept with your account so we can tell which of our marketing works. We also pass the channel to our customer relationship provider with the rest of your account record.
Website chat and cookies: when you first visit our site we ask whether you accept cookies. Essential cookies keep you signed in and are always on. If you accept, our chat assistant loads and stores a visitor ID and your conversation in your browser so it can continue it; it is run by our customer messaging provider. If you choose only essential, the chat does not load. You can change your choice at any time from “Cookie settings” at the bottom of every page.
3. How we use information
To provide the service — asking your questions, computing your metrics, and rendering your dashboards.
To secure and improve the service, diagnose problems, and prevent abuse.
To communicate with you about your account, and — where you have opted in — to send product updates. You can unsubscribe at any time.
We do not sell personal information, and we do not use your workspace data to train models.
4. Legal bases (GDPR)
We process account data to perform our contract with you; usage and security data under our legitimate interest in operating a safe service; and marketing communications on the basis of your consent.
6. Google Search Console data
Connecting Google Search Console is optional, and nothing in the product requires it. Unlike the subprocessors in section 5, which we engage on your behalf, this is a connection you make to your own Google account and can withdraw at any time.
What we ask for: read-only access to Search Console (the webmasters.readonly scope), plus your email address and your Google account identifier. The access is read-only — we cannot add, change or remove anything in your Search Console. We ask for the email and identifier so the product can show you which Google account a workspace is reading through, record that connection in your workspace's audit log, and recognise a later reconnection as the same account rather than a new one.
What we store: for the one property you choose, the per-day totals Google reports — clicks, impressions, click-through rate and average position — and the search terms Google reports for that property with the same figures. The first sync fetches up to sixteen months, which is as far back as Google keeps. It is held against your workspace and nothing else.
What we use it for: a timeline of search performance beside your answer-engine figures, and a ranked shortlist of which of your real search terms are worth tracking as questions. That ranking is computed on our own servers — no Google data is sent to an AI model to produce it. If you then choose to track one of those terms, the question you save is asked of the answer engines like any other question you write, because that is what tracking a question means.
How the credentials are held: the refresh token Google issues is encrypted in a secrets vault and can be decrypted only by the server component that refreshes it. It is never sent to a browser, never shown anywhere in the product, and never included in an export.
Who else sees it: nobody. We do not share Google user data with third parties, do not use it for advertising, and do not use it to train models. No person reads it except where you ask us to in support of a request you have made, where it is necessary to investigate a security incident, or where the law requires it.
Withdrawing: Settings › Integrations › Disconnect asks Google to revoke our access first and then deletes the connection and the stored credentials, in that order, so a failed revoke can never leave a live grant behind. You can also revoke it yourself at myaccount.google.com/permissions. The figures already synced stay with your workspace, so disconnecting does not erase your history; they are deleted when the workspace is deleted, or sooner if you ask us at privacy@rankyourbrand.ai.
RankYourBrand's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
7. Data retention and location
Account data is retained for the life of your account and deleted within 30 days of closure.
Your workspace's questions, sampled answers and reports are kept for the life of the workspace, and are deleted when you delete it. Raw crawler and referral events, and any conversion events you send us, are kept for 13 months; the daily summaries built from them are kept for as long as the workspace exists, because they carry no request-level detail.
Data is stored in the United States. Additional regions are on the roadmap.
8. Your rights
Depending on your location, you may have the right to access, correct, export, or delete your personal data, and to object to or restrict certain processing. To exercise these rights, email privacy@rankyourbrand.ai.
California residents have additional rights under the CCPA/CPRA, including the right to know and to delete; we do not sell personal information.
9. Security
We serve everything over HTTPS, store passwords only as salted hashes, and restrict access to production data. No system is perfectly secure; report any concern to security@rankyourbrand.ai.
10. Changes
We will post any changes here and update the date above. Material changes will be communicated to account holders.