Loopy — Privacy Policy
Last updated: 7 October 2026 · Effective: 4 July 2026
Loopy (tryloopy.io) is a service operated by the individual proprietor trading as "Loopy", based in Australia. This policy explains what personal information we collect and how we use it. Questions or requests? Email info@tryloopy.io.
1. What we collect
- Account info: your email and profile.
- Your content: the website URL, brand assets, logos, and images you upload, and the ads we generate for you.
- Customer research evidence: reviews, support tickets, return reasons, survey answers, and interview transcripts you upload or paste, which may include information about your own customers (see section 4).
- Site data: we load the URL you submit and read its public colors, fonts, and text to build your ads.
- Billing info: your plan and transaction details (Stripe handles your card; we never store your full card number).
- Usage data: basic logs, IP address, and activity in the app, to keep Loopy secure and working.
- Connected accounts (only if you connect them): read-only Meta Ads and Google Analytics (GA4) performance data.
- AI assistant connection (only if you connect it): when you use Loopy inside an AI assistant such as Claude or ChatGPT, the requests your assistant sends us (for example a brand name, a website, or customer quotes it found) and a record of which assistant app is connected.
2. How we use it
We use your information to run Loopy — create your account, generate your ads, process payments, provide support, keep the service secure, and improve it. We send you service emails (like receipts and account notices), and only send marketing emails if you opt in.
3. AI providers
To generate your ads, we send your content to third-party AI providers. We don't use your content to train our own models, and we don't sell your data. Where a provider offers a no-training or no-retention option, we use it.
4. Customer research evidence
You can upload exports (product reviews, support tickets, return reasons, post-purchase survey answers, customer call or interview transcripts as text files) and paste quotes. These can contain personal information about your own customers. For that data, we process it on your behalf and on your instructions (as your processor or service provider), and you are responsible for having the right and a lawful basis to share it with us.
Before anything is stored, our code removes emails, phone numbers, order numbers, card-like numbers, street addresses, tracking parameters in links, and whole columns that look like names, emails, phones, addresses or customer IDs. It also removes names in ticket greetings and sign-offs. In transcripts it removes speaker labels and replaces speakers' names said aloud with [name]. Names written inside a sentence may remain. We don't keep the original uploaded files, and file names are cleaned too.
The stored statements are analysed by an AI model through OpenRouter, on routes we configure to require zero data retention and no training, relying on those providers' commitments, to produce research findings shown only in your account. We don't use them to train models.
Client request link (paid plans). You can create a private link (valid for 30 days, and you can turn it off any time) so your client can upload files without an account. Your client must confirm they are authorised to share the data. The link can only add data to your brand and never shows existing data. We email you a notification when new data arrives, using Resend. Uploads through the link belong to your account like your own uploads.
Public posts and comments (paid research). For paid research we use third-party data providers that collect publicly available posts, comments and ad-library listings related to your brand and category. We use them only for that brand's research, show findings with short quotes, and apply the same redaction.
On-site reviews (paid research runs). We read reviews publicly displayed on your brand's own online store product pages, including the store's public review-widget feed (for example Okendo), and use them only for that brand's research. We don't store reviewer names, and the same redaction applies.
We keep research evidence until you delete it (one quote, one upload, or all evidence for a brand), delete the brand, or close your account (backup copies clear within 90 days). Findings and briefs already made from evidence stay until you delete them. If one of your customers asks us about their data, we will refer the request to you, as the business that holds the relationship, and help you delete it.
5. Connected accounts
If you connect Meta Ads or Google Analytics, we access them read-only, only to show you your own performance data, and we store the connection securely. You can disconnect anytime. Loopy's use of information from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements — we never use Google data to train AI or share it for advertising.
6. Using Loopy in Claude or ChatGPT
If you connect Loopy to an AI assistant such as Claude or ChatGPT, what Loopy sends back (your research findings, briefs, hooks and reference ads) goes to the AI app you connected and is handled under that app's own terms and privacy policy, which we don't control. Customer quotes your assistant submits are treated exactly like quotes you paste: the same redaction applies, and you have the same responsibilities for your customers' data as in section 4. The connection is limited to Loopy's assistant features, and you can disconnect it any time in that app. Sign-in for the connection is handled by WorkOS. Our analysis method and prompts stay on our servers.
7. Who we share it with
We don't sell your personal information or use it for targeted advertising. We share it only with the providers that help us run Loopy — such as Supabase (accounts and storage, including research evidence), Render (hosting), Stripe (payments), Resend (transactional email), WorkOS (sign-in for AI assistant connections), third-party data providers that collect publicly available posts, comments and ad-library listings (for paid research), and our AI providers (including OpenRouter, which analyses uploaded and on-site evidence after personal details are removed, and public research text as published) — and only so they can perform their service for us. We may also disclose information if the law requires it, or in connection with a sale of the business.
8. Where your data is held
We're based in Australia, and some of our providers are overseas (including the United States), so your information may be processed outside your country. We take reasonable steps to keep it protected wherever it's held.
9. Security and retention
We protect your information with encryption and access controls, but no system is perfectly secure. We keep your information for as long as your account is active, and delete it (or de-identify it) when it's no longer needed — except where we must keep some records to meet legal or tax obligations.
10. Your choices
You can view, edit, export, or delete much of your content in the app. To access, correct, or delete your personal information — or close your account — email info@tryloopy.io and we'll action it. If you're unhappy with how we've handled your information, you can contact the Office of the Australian Information Commissioner (oaic.gov.au).
11. Cookies
Loopy uses the cookies needed to keep you signed in. We also use PostHog product analytics, which stores a cookie and local-storage entry on your device and, once you're signed in, records how you use Loopy (session recordings and heatmaps) so we can find and fix rough edges. On-screen text, anything you type, and images are always hidden in these recordings. We don't use advertising cookies.
12. Children
Loopy is for adults (18+) and isn't directed at children. We don't knowingly collect information from children.
13. Changes
We may update this policy. If we make an important change, we'll update the date above and let you know in-app or by email where appropriate.
14. Contact
Questions or requests about your privacy? Email info@tryloopy.io.