Privacy Policy.

Rendix reads Google data only when you connect a Google account inside the app, and only with read-only access. Rendix cannot change anything in your Google accounts.

What Rendix accesses.

• Google Search Console (read-only scope webmasters.readonly): the list of Search Console properties your Google account can read, with your permission level, and - for the pages of the site you audit in Rendix - the URL Inspection result for each page: whether it is in Google's index, its coverage state, when Google last crawled it, the canonical URL Google chose, its robots and indexing state, and how many sitemaps and referring pages Google lists for it.
• Google Analytics (read-only scope analytics.readonly): the names of the Analytics accounts and properties you can read, and for the property you choose, aggregate session counts (sessions, engaged sessions and key events) by date, traffic source and landing page. Rendix does not request data about individual visitors.

How Rendix uses it.Only to show you, inside your own Rendix workspace, which of your pages are in Google's index (Foundation) and how many visits AI assistants send to your site (Traffic), and to turn those facts into findings about your site. Google user data is not used for advertising, is not sold, is not used to train artificial intelligence or machine learning models, and is not sent to any AI model provider.

Who it is shared with. Nobody, except the infrastructure providers that run Rendix and store its data - Supabase (database), Vercel (hosting) and Trigger.dev (background jobs) - or when the law requires it.

How it is protected.Access tokens and Search Console results are stored in Rendix's database on Supabase, which encrypts data at rest (AES-256) and in transit (TLS). The tokens are read only by Rendix's server code and are never sent to your browser.

How long it is kept and how to delete it.A token is kept while the connection is active. When you disconnect Search Console or Analytics in Rendix, Rendix revokes its access at Google and deletes the token; you can also remove Rendix's access at any time at myaccount.google.com/permissions. Search Console results stay with your audit history while your account exists. Analytics figures are not stored in the database: they are fetched when you open the dashboard and kept in a server cache for a few minutes. To delete your account and all its data, write to hi@rendix.io.

Rendix's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

• Account data: your email address, used to sign you in and to send service email.
• Brand data you give us: your domain, brand name, competitors, audience and the prompts you track.
• Public web content: pages of your site and of sites cited by AI engines, fetched to build your brand profile and audits.
• AI answers: the responses of ChatGPT, Gemini, Perplexity and Google AI Overviews to your tracked prompts, with their citations.
• Crawler logs, only if you connect a log source: for requests made by known crawlers - host, path, crawler name, user agent, IP address, HTTP status and time. Log lines from other visitors are dropped on receipt and never stored.
• Connected accounts, only if you connect them: access tokens for Vercel, Google Search Console, Bing Webmaster Tools or Google Analytics. The Vercel token is stored encrypted. What Rendix reads with a Google account is described under Google user data.
• Site analytics: rendix.io loads Google Analytics and DataFast to measure visits.

To run the product: scanning AI engines, computing your visibility metrics, auditing your site, showing crawler activity, generating recommendations and content drafts, and sending you service email. We do not sell personal data.

Rendix runs on third-party infrastructure. Depending on the feature, data passes through:

• Supabase - database and sign-in.
• Vercel - hosting. Trigger.dev - background jobs. Resend - email.
• OpenAI, Anthropic and Google Cloud - language models that analyse AI answers and brand content.
• Perplexity, Bright Data and DataForSEO - retrieving AI engine answers. Firecrawl - fetching web pages.
• Google Analytics and DataFast - site analytics.

The app sets a session cookie to keep you signed in. The analytics scripts listed above may set their own cookies.

You can disconnect any connected account inside the app. To get a copy of your data, correct it, or have your account and its data deleted, write to hi@rendix.io.

When this policy changes, the date at the top changes with it.