Legal
Privacy policy
This policy explains what personal data GeoRush, a service operated by Spitares, LLC (United States), processes, what it uses it for, who it shares it with, how long it keeps it, and how you can exercise your rights. It applies to the georush.si website, the app and the API. Last updated: November 16, 2026.
Updated on
1. Who is responsible
The data controller is Spitares, LLC, a limited liability company organized in the United States that operates GeoRush (“GeoRush”, “we”, “us”).
For any privacy question or to exercise your rights, write to us through the contact form and choose the topic “Privacy and data”. It is our official channel for these requests.
2. Who this policy applies to
- Visitors to the georush.si website.
- Users who create an account or are invited to a workspace.
- People who use the free check or write to us through the contact form.
- Visitors to our customers' websites that install GeoRush web analytics, and other people whose data we process on a customer's behalf (see section 6).
3. What data we process
| Category | Data | Source |
|---|---|---|
| Account | Name, email, password (stored only as a bcrypt hash, never in plain text), sign-up date, last login, the workspaces you belong to and your role | You, when you sign up or accept an invitation |
| Billing | Plan, subscription status, trial and renewal dates, credit purchases, and Stripe customer and subscription IDs. We do not store your full card details: Stripe handles them | You and Stripe |
| Brand data and service usage | Brands, domains, aliases, competitors, official facts, tracked questions, answers collected from AI engines and their analysis, tasks, drafts, Ask GeoRush conversations, reports, credit usage | You and the service itself |
| Google Search Console (optional) | The email of the Google account you connect, a refresh token stored encrypted, and performance data for your properties (queries, pages, clicks, impressions, positions). Access is read-only | Google, when you authorize the connection |
| Integrations | Alert destinations (Slack or other webhook URLs), API keys you create, and recipients of scheduled reports | You |
| Free check | Email, brand, domain, category and language, plus the check result | You, when you use the check |
| Contact form | Name, email, company (optional), topic, message, language, the page you wrote from, and a salted hash of your IP address, not the IP itself, to limit abuse | You, when you write to us |
| Technical and security data | IP address and browser data that reach our servers with each request, used for security, abuse prevention and troubleshooting | Your browser or app |
We do not ask for or need special categories of data (health, beliefs, etc.). Please don't include them in questions, brand facts or messages.
4. Why we use data and on what legal basis
Legal bases are stated under the EU General Data Protection Regulation (GDPR); if other laws apply to you, we process your data for the same purposes.
| Purpose | Legal basis |
|---|---|
| Creating and managing your account and providing the service (collecting answers, analyzing them, producing metrics, plans, reports and drafts) | Performance of a contract (Art. 6(1)(b) GDPR) |
| Charging subscriptions and packs, issuing invoices, and meeting tax and accounting obligations | Performance of a contract and legal obligation (Art. 6(1)(b) and (c)) |
| Sending service emails: billing notices, alerts, scheduled reports you set up | Performance of a contract (Art. 6(1)(b)) |
| Connecting Google Search Console and showing its data | Performance of a contract, at your request; you can disconnect at any time |
| Running the free check and showing you the result | Steps taken at your request before entering a contract (Art. 6(1)(b)) |
| Contacting you about GeoRush after the free check | Legitimate interest (Art. 6(1)(f)), with the right to object at any time; where the law requires consent, only with it |
| Replying to your contact form messages | Legitimate interest in handling your request, or pre-contractual steps (Art. 6(1)(f) and (b)) |
| Security, fraud and abuse prevention, usage limits, technical support and service improvement | Legitimate interest (Art. 6(1)(f)) |
| Responding to authorities and defending legal claims | Legal obligation and legitimate interest (Art. 6(1)(c) and (f)) |
5. How we use artificial intelligence
To provide the service, GeoRush sends the questions you track to the AI engines you choose and receives their answers. It then sends the answers, your brand data (name, domains, competitors, official facts) and, when you ask, your Ask GeoRush messages to Claude (Anthropic) to analyze them or generate text.
These requests contain information about companies and markets, not about people, unless you include personal data in your questions, brand facts or chat; so please don't. GeoRush does not train its own models on your data. AI engine answers are third-party generated content and may contain errors (see the terms).
6. Data we process on behalf of our customers
In some cases it's not us who decide how data is used, but the customer using GeoRush. The customer is then the controller and Spitares, LLC acts as processor, following the customer's instructions. This applies to:
Web analytics. If a customer installs the GeoRush analytics script on their website, we process data about their visitors on the customer's behalf. The analytics works without cookies. To count unique visitors we compute an identifier as a hash of the IP, the browser and the site key with a salt that changes every day and is deleted the next day, so the same person can't be linked across days. IP addresses are not stored: they are used in memory to estimate country, region and city with a local geolocation database. We strip URL parameters that often contain personal data (email, token, phone…). If the browser sends Do Not Track or Global Privacy Control, by default only an aggregate counter is incremented. The customer can enable an optional persistent identifier (stored in the visitor's localStorage) and set retention between 1 and 36 months (13 by default). The customer is responsible for informing their visitors and, where their law requires it, obtaining consent.
Contacts for getting cited. The Get cited module looks for contact details published on third-party websites (for example, an editorial email address) at the customer's request. GeoRush does not email those contacts; if the customer decides to write to them, they do so through their own means and under their own responsibility.
Report recipients and invited members. The customer decides which people are invited or receive reports.
If you are a visitor to a customer's website or someone contacted by a customer, please contact that customer first to exercise your rights; if you write to us, we will pass your request on to them.
7. Who we share data with
We do not sell your personal information or share it for cross-context behavioral advertising. We only disclose it to providers that help us run the service (processors or subprocessors), under contracts requiring them to protect it, and to authorities when the law requires it.
| Provider | Purpose | Data |
|---|---|---|
| Stripe | Payments, subscriptions, invoices and the billing portal | Billing data, email, payment method (handled directly by Stripe) |
| Anthropic (Claude) | Answer analysis, diagnoses, drafts, pitch emails, prompt maps, the Ask GeoRush chat, and one of the measured engines | Questions, answers, brand data and chat messages |
| OpenRouter and AI model providers (OpenAI, Google, Perplexity, xAI, DeepSeek, Mistral AI), directly or through OpenRouter | Getting answers from the measured AI engines | The questions you track and the language or market |
| SerpApi | Reading real Google AI Overviews and Google AI Mode results | The questions you track and the market |
| Google (Search Console API and OAuth) | Read-only connection to Search Console | Your authorization and the Google account email |
| Hosting provider | Servers and databases where GeoRush runs | All service data |
| Email delivery provider | Sending service emails and scheduled reports | Recipient email and message content |
| Destinations you configure (Slack, webhooks) | Delivering the alerts you set up | The alert content |
Authorized GeoRush staff may access your workspace when needed to support you, resolve issues or keep the service secure.
8. International transfers
Spitares, LLC is located in the United States, and several of our providers process data in the United States or other countries outside the European Economic Area. When we transfer personal data from the EEA, the United Kingdom or Switzerland, we rely on appropriate safeguards: the recipient's certification under the EU-U.S. Data Privacy Framework where available, the Standard Contractual Clauses approved by the European Commission, or other mechanisms provided by law. You can ask us for more information about these safeguards through the contact form.
9. How long we keep data
| Data | Retention |
|---|---|
| Account and service data | While your account or workspace is active. If you ask us to delete it, we delete or anonymize it, except what we must keep by law |
| Billing | As long as applicable tax and accounting obligations require |
| Search Console connection | Until you disconnect it or delete your account; you can also revoke access from your Google account |
| Customer web analytics | According to the retention each customer sets (1 to 36 months, 13 by default). Daily salts are deleted every day |
| Free check | As long as needed to show you the result and follow up commercially, unless you object earlier |
| Contact messages | As long as needed to handle your request and follow up |
| Technical and security data | As long as needed for service security and troubleshooting |
We may also keep data in restricted form for the limitation periods of potential legal claims.
10. How we protect data
- Encrypted connections (HTTPS) between your browser and GeoRush.
- Passwords stored only as hashes (bcrypt).
- Google Search Console tokens stored encrypted, with read-only access.
- In analytics and the contact form, IP addresses are turned into salted hashes instead of being stored.
- Data access limited by workspace and permissions, and usage limits against abuse.
11. Your rights
If the GDPR applies to you (for example, if you are in the European Economic Area), you can exercise your rights of access, rectification, erasure, objection, restriction of processing and data portability, and withdraw consent where processing relies on it, without affecting prior processing. You may also lodge a complaint with a supervisory authority, such as your local data protection authority.
If you are a California resident (CCPA/CPRA), you have the right to know what personal information we collect, to access it, to correct it, to delete it, and not to be discriminated against for exercising your rights. We do not sell personal information or share it for cross-context behavioral advertising. You may act through an authorized agent. Residents of other states or countries may have similar rights under their laws.
How to exercise them: write to us through the contact form with the topic “Privacy and data”, giving the email linked to your data and the right you want to exercise. We may ask you to verify your identity. We will reply within the legal deadlines (under the GDPR, one month, extendable for complex requests).
12. Children
GeoRush is a service for businesses and professionals. It is not directed at children under 16, and we do not knowingly collect their data. If you believe a child has given us personal data, contact us and we will delete it.
13. Cookies and local storage
GeoRush does not use advertising cookies or third-party analytics cookies. It only uses technical storage in your browser (for example, to keep you signed in or remember light or dark mode). Details are in the cookie policy.
14. Changes to this policy
We may update this policy when the service or the law changes. We will publish the new version on this page with its date and, if the changes are significant, notify you by email or in the app before they take effect.