Privacy Policy

Last updated 9 November 2026

• 1. Who we are
• 2. What we collect and why
• 3. Google user data
• 4. Google API Services User Data Policy
• 5. How the service uses AI models
• 6. Who else handles your data
• 7. Cookies
• 8. How long we keep it
• 9. Export, deletion and revoking access
• 10. Your rights
• 11. Security
• 12. Children
• 13. Changes and contact

1. Who we are

remake (the "service", previously called hyperfind.ai) is operated by Gabi ("we", "us"), reachable at gabi@tryremake.com. We are responsible for the personal data described here. This policy covers www.tryremake.com, the app at app.tryremake.com, and the service's earlier addresses on hyperfind.ai.

2. What we collect and why

Your account

Your email address, and either a password (stored only as a one-way hash we cannot read) or your Google sign-in details (section 3). We also keep the account settings you choose, such as your name, a profile picture you upload, your team members and their roles. We use this to run your account, keep it secure and send you the emails the service needs, such as sign-in codes, receipts and the alerts you switch on.

The websites, brands and prompts you add

The website addresses, brand names, rivals, topics, countries and prompts you add or that the service suggests for you. The service reads the public pages of the websites you add, the same way any visitor could, and keeps the results of its website checks. This is the service you ask for.

AI answers and reports

The answers AI assistants give to your prompts, the scores and reports built from them, and the fixes the service writes for your website. Reports you share live at a private, hard-to-guess link; anyone you give that link to can read that report.

Credit and usage

A record of the credit you load, spend and are refunded, and of each piece of work it paid for. Payment card details are handled by our payment providers; they never reach our servers. We receive only what we need to add the credit to your account, such as the amount, the date and a reference.

Technical data

Your IP address is recorded with a new sign-up and with free website checks, so we can limit free use per network and stop abuse. Our servers also keep ordinary request logs for security and troubleshooting; sign-in links and access keys are removed from those logs. If something breaks, an error report with the failing request's details (with sign-in links, keys and values removed) goes to our error-tracking service so we can fix it.

Website analytics

This website (www.tryremake.com) loads no analytics, tracking scripts or cookies. The app uses Google Analytics to measure overall visits; it is never used for advertising, and you can block it in your browser without losing anything.

Our legal bases

For readers who need them named: we process account, website and usage data to provide the service you signed up for; technical data on our legitimate interest in keeping the service secure and available; and Google Search Console or Google Analytics data on your consent, which you can withdraw at any time (section 9).

3. Google user data

remake uses Google in up to three ways, each only when you choose it:

Feature	Google permissions requested
Sign in with Google	openid, email, profile
Connect Google Search Console (optional, per website)	openid, email, https://www.googleapis.com/auth/webmasters.readonly
Connect Google Analytics (optional, per website)	openid, email, https://www.googleapis.com/auth/analytics.readonly

All of this access is read-only. remake never changes anything in your Google account, Search Console or Analytics.

Sign in with Google

• What we receive: your Google account ID, your email address (we accept it only if Google has verified it), your name and a link to your profile picture.
• How we use it: to create your remake account or sign you in to it, and to show your name and picture in the app.
• What we keep: the account ID, email address, name and picture link, stored with your account. The access Google grants for sign-in is used once to read those details and is not stored.

Google Search Console

• What we read: the list of your Search Console properties, so we can pick the one that matches the website you are connecting; then, for that property only, the clicks and impressions of up to 1,000 of its pages and its top 10 search queries over the last 28 days. We also read the email address of the Google account you connect with.
• How we use it: to show, in that website's dashboard, how much Google search traffic reaches the pages AI assistants cite, and your top queries. Nothing else.
• What we keep: the chosen property's address, the connecting Google account's email address, the dates of the connection, and an encrypted refresh credential so the dashboard can update. The numbers themselves are read from Google when you open the dashboard and held only in our server's memory for about 15 minutes; they are not saved to our database. Short-lived access credentials are kept in memory only and never written to disk or logs.

Google Analytics

• What we read: the list of your Analytics properties, so we can pick the one that matches the website you are connecting; then, for that property only, the number of sessions over the last 28 days that came from AI assistants (for example chatgpt.com or perplexity.ai), grouped by source. We also read the email address of the Google account you connect with.
• How we use it: to show, in that website's dashboard, how many visits AI assistants sent you. Nothing else.
• What we keep: the same as for Search Console: the property reference, the connecting account's email, connection dates and an encrypted refresh credential. The session counts are held in memory for about 15 minutes and not saved to our database.

Who sees Google data

Only you and the people you add to your remake team see these numbers, in your dashboard. We do not send Google user data to AI models, use it to train any model, sell it, use it for advertising, or share it with anyone else, except where the law requires it.

4. Google API Services User Data Policy

remake'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. This applies to every permission listed in section 3, including the Search Console (webmasters.readonly) and Analytics (analytics.readonly) permissions. In particular:

• we use that data only to provide and improve the user-facing features described in section 3;
• we do not transfer it to others except as needed to provide those features, to comply with the law, or as part of a merger or acquisition with your notice;
• we do not use or transfer it for serving ads, including retargeting or personalised advertising;
• we do not use it to develop, improve or train AI or machine-learning models, and we do not send it to AI model providers;
• no person reads it unless you ask us to for support, it is needed for security or to comply with the law, or it has been aggregated and made anonymous for our internal operations.

5. How the service uses AI models

Measuring AI visibility means asking real AI assistants the questions your buyers ask. To do that, your prompts, your brand and rival names, and short excerpts from the public pages of the websites you add are sent to AI model providers, and their answers are stored as part of your results. The fixes the service writes for your website are produced the same way. We send them only what each task needs, and never Google Search Console or Google Analytics data.

When you ask for search demand on your prompts, the prompt phrases are sent to a search-data provider to look up how often people search for them.

6. Who else handles your data

We do not sell or rent personal data. We share it only with the services that run remake for us, each for its own task:

• our hosting provider, whose servers run the app (in Canada);
• the network provider in front of our servers, which protects them and delivers pages;
• AI model providers and a search-data provider, as described in section 5;
• our email delivery service, for the emails the service sends you;
• our payment providers, for loading credit;
• our error-tracking service, for crash reports;
• Google, for the sign-in and the connections you choose (section 3), and for the app's visit analytics.

Some of these process data outside your country; where they do, we rely on the transfer safeguards they offer. We may also disclose data if the law requires it. A current list of these providers is available on request.

7. Cookies

This website (www.tryremake.com) sets no cookies. The app uses only the cookies it needs to work:

• a signed sign-in cookie that keeps you signed in, for up to 30 days;
• short-lived cookies that protect the Google sign-in and Google connection steps from forgery, cleared when the step finishes;
• Google Analytics cookies, which measure overall visits to the app.

No advertising cookies are used.

8. How long we keep it

• Account, websites, prompts, answers and reports: for as long as your account is open, so your history and trends keep working.
• A brand you delete: its setup (prompts, rivals, settings) can be restored for 7 days and is then removed; its past results and reports stay in your account history until you delete your account or ask us to remove them. Any Google connections on it stop at once and are cancelled with Google at the same time.
• Credit and usage records: for as long as your account is open. Our payment providers keep their own payment records under their own rules.
• Google Search Console and Analytics numbers: about 15 minutes, in memory only.
• Server logs: a short rolling period.
• Backups: we take nightly backups so the service can recover from failure. Older copies roll off on a fixed schedule, and the oldest are removed after about 12 months; data you delete leaves the backups as they roll off.

9. Export, deletion and revoking access

• Export or delete: email gabi@tryremake.com from your account's address and we will send you a copy of your data or delete it. You can also delete your whole account yourself in the app under Settings. Deleting your account removes its data from our database and cancels its Google connections with Google.
• Disconnect Google Search Console or Analytics: on that website's connections in the app, choose Disconnect. remake stops using the connection straight away. Its encrypted refresh credential stays stored, unused, until you delete that website's brand or your account (we then cancel it with Google), or until you remove remake's access at Google as described next.
• Revoke at Google: visit myaccount.google.com/permissions, choose remake and remove its access. This works for sign-in and for both connections.

10. Your rights

Wherever you live, you can ask us for a copy of your data, ask us to correct it, ask us to delete it, object to how we use it, and withdraw consent you have given. Email gabi@tryremake.com and we will reply within 30 days. These match the rights in laws such as the GDPR and UK GDPR. You can also complain to your local data protection authority. For California residents: we do not sell or share personal information as the CCPA defines those terms.

11. Security

Everything travels over encrypted connections. Passwords are stored as one-way hashes, Google refresh credentials are encrypted at rest, access to our servers is restricted, and our servers accept web traffic only through our network provider. If you believe your account has been affected, email us and we will tell you plainly what we know.

12. Children

remake is a business tool and is not meant for children. We do not knowingly collect data from anyone under 16.

13. Changes and contact

We may update this page; the date at the top shows the latest version. Questions: gabi@tryremake.com.