Privacy Policy

This Privacy Policy explains what Clearly ("we", "us", "our") collects when you use our reporting service ("the Service"), why, how long we keep it and who else handles it. The Service is operated by Enviroware Ltd, trading as Clearly, a company registered in New Zealand. Plain version: we read your marketing data to show it back to you and to answer your questions about it. We never sell it, never use it for advertising and never use it to train AI models.

1. Information we collect

Your account

If you sign in with Google, we receive your name, email address and profile picture from Google and use them to create your account and show who is signed in. If you sign up with an email address, we store that address, your name and a securely hashed password. We also keep your plan, your role and when you joined.

Your business profile

During setup, on your Profile page and in a report's settings, you can tell us about your business: what it does, where it works, what counts as a win, what a customer is worth, your close rate, your budget and similar. We keep what you enter so reports and Ask Why answers fit your business. You can change or clear any of it on your Profile page.

Connections to your platforms

When you connect a platform (Google, Meta, LinkedIn or Reddit), it gives us credentials that let us read your data on your behalf. We store them on our servers, tied to your account; they never reach your browser. Google credentials are encrypted at rest (AES-256-GCM). We never see or store your password for any platform.

Your platform data

When a report loads, our servers ask the platform for the figures that report needs and pass them to your browser. We do not write that data to a database. The exceptions are Ask Why, which keeps the conversations you have with it (below), and weekly reviews you choose to receive by email.

Reports and share links

Your report layouts and settings (pages, blocks, sources, date ranges, filters, groups and theme) are stored against your account so they follow you between devices. When you create a share link, we store the report's configuration (not its data) against a random access token.

Ask Why

When you ask a question about a report, we keep the conversation so you can come back to it: your question, the answer, any chart in the answer and the figures behind it, and a record of which queries were run. Long conversations are condensed into a short summary of what was discussed. If you choose to save a note Ask Why suggests (for example "our busy season is November"), we keep that note for your account, your business or that report. We also keep a count of the questions you ask and their cost, to apply your plan's limits.

Weekly reviews

If you turn on a weekly review for a report, we read that report's data once a week without you being signed in, write a short review and email it to your account's address. The email contains the review's headline and points, which include figures from your report.

Billing

If you buy a plan, Stripe collects your payment details. We receive your subscription status and a customer reference, never your card number.

Usage analytics

We use Google Analytics 4 on our own website and app to understand, in aggregate, how the Service is used (pages viewed, sign-ups, features used). This is separate from the data we read from your accounts, and nothing from your connected platforms is sent to it.

Advertising

The Service shows no advertising, and no data from your connected platforms is ever used for advertising.

2. Google user data

Clearly asks for each Google scope only when you connect that source, and only for that source. Signing in asks for your identity alone. We use every scope for reading only, to fetch your data and show it back to you. We never create, edit or delete anything in your Google accounts.

• Sign in with Google (openid, .../auth/userinfo.email, .../auth/userinfo.profile): your name, email address and profile picture, used to create your account and show who is signed in.
• Google Analytics (.../auth/analytics.readonly): read-only access to the GA4 properties you choose, including sessions, channels, pages, events and revenue. Used to render your analytics report blocks. No narrower scope provides read access to GA4 property data.
• Google Search Console (.../auth/webmasters.readonly): read-only access to the Search Console performance data of the sites you choose, including clicks, impressions, average position, queries and pages.
• Google Ads (.../auth/adwords): reporting access to the Google Ads accounts you choose, including impressions, spend, clicks and conversions by campaign, ad group and keyword. We issue reporting queries only and perform no create, edit, pause or delete operations. The Google Ads API offers only this single scope; there is no separate read-only scope.
• Google Business Profile (.../auth/business.manage): the list of your Business Profile accounts and locations, and the Performance API metrics for the locations you choose (profile views, calls, website clicks and direction requests). We never edit your listing, reviews, photos or posts. The Business Profile APIs offer only this scope; there is no read-only alternative.
• Google Merchant Center (.../auth/content): the list of Merchant Center accounts you can access, and product performance and status from the Merchant API reports for the account you choose (clicks, impressions and product status). The first time you connect an account, the Merchant API requires us to make one registration call that links our Google Cloud project to it; that call does not change your products, feeds or settings, and we make no other write call. The Merchant API offers only this scope; there is no read-only alternative.
• Google Sheets (.../auth/drive.file): access only to the spreadsheets you pick yourself in Google's file picker. We cannot see any other file in your Google Drive, and we never change the sheet. To open the picker, your browser receives a short-lived token limited to this scope; it is used for the picker alone and every read of the sheet's values goes through our servers.
• BigQuery (.../auth/bigquery.readonly): the list of projects, datasets and tables you can access, and read-only queries on the table you choose for your report. Queries run as BigQuery jobs in the Google Cloud project you choose, so they count towards that project's BigQuery usage. We never write to, change or delete your data.

This data is read live and passed to your browser. It is not written to a database, except in your saved Ask Why conversations and weekly reviews, described in Section 1. The only other Google-derived information we keep is your encrypted credentials and your account details.

Limited Use disclosure

Clearly's use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, we do not:

• transfer or sell this data to third parties, except as necessary to provide or improve the user-facing features of the Service (such as Ask Why), for security purposes, or to comply with applicable law;
• use this data for serving advertisements, including personalised, retargeted or interest-based advertising;
• allow humans to read this data, unless we first obtain your affirmative agreement to view specific data, it is necessary for security purposes or to comply with applicable law, or the data has been aggregated and anonymised and is used for internal operations;
• use this data to develop, improve or train generalised or non-personalised artificial intelligence or machine learning models.

3. Other platforms

The same rules apply to every platform you connect: read-only, only what you choose, only to show it to you.

• Meta Ads (ads_read): reporting data for the ad accounts you choose (spend, reach, clicks, conversions and results by campaign, ad set and ad). If you connect a Facebook Page or Instagram account, we also ask for pages_show_list, pages_read_engagement, read_insights, instagram_basic and instagram_manage_insights, to read reach, views and follower figures for the Pages and accounts you choose. We never post, reply or change anything.
• LinkedIn Ads: reporting data for the ad accounts you choose (spend, impressions, clicks, leads and conversions by campaign and creative).
• Reddit Ads: reporting data for the ad accounts you choose (spend, impressions, clicks and conversions by campaign and community).

4. How we use your information

• To sign you in and read your connected platforms on your behalf.
• To build, save and share your reports.
• To answer the questions you ask with Ask Why, and to send weekly reviews you have turned on.
• To fit reports and answers to your business, using your business profile and saved notes.
• To apply your plan's limits and take payment.
• To send account emails: sign-up verification, password resets, billing notices and weekly reviews.
• To keep the Service secure and working, and to understand aggregate use so we can improve it.

We do not sell personal information. Our staff do not read your platform data, reports or Ask Why conversations, except when you ask us for support and agree to it, when it is needed for security or the law, or in aggregated and anonymised form to improve the quality of answers.

5. How long we keep it

• Platform credentials: until you disconnect the platform or delete your account.
• Platform data: not stored, apart from what is in your Ask Why conversations and weekly reviews.
• Ask Why conversations and saved notes: until you delete them or delete your account.
• Ask Why quality logs (a question and its answer, used to check answers are accurate): deleted automatically after 30 days.
• Question counts and costs: about 13 months, for billing and limits.
• Reports and business profile: until you delete them or delete your account.
• Share links: deleted after 12 months, or straight away when you turn a link off.
• Sign-in sessions: ended after 90 days without use.
• Backups: we keep weekly encrypted backups of our account store for 8 weeks, so a deleted item can remain in a backup until it ages out.
• Billing records: kept by Stripe as the law requires.

6. Who else handles your data

• The platforms you connect (Google, Meta, LinkedIn, Reddit): they hold your data; we read it at your request under their own terms and privacy policies.
• Cloudflare, Inc.: runs our servers and storage. Your account, credentials, reports, conversations and backups are stored with Cloudflare.
• Anthropic, PBC: writes Ask Why's answers. When you ask a question, Anthropic receives the question and the report figures needed to answer it, processes them on our behalf to return the answer, and does not use them to train its models.
• Stripe, Inc.: processes payments. It receives your billing details, never your platform data.
• Resend: sends our emails. It receives your email address and the email's content, which for a weekly review includes figures from your report.
• Google: besides being a data source, Google's favicon service shows a report's website icon, which means the report's website address is sent to Google.

We share personal information with no one else, except where the law requires it.

7. Where your data is processed

We are based in New Zealand. Cloudflare stores and processes data on its global network, and Anthropic, Stripe and Resend process data in the United States. When we send data overseas, we use providers bound to protect it to a standard comparable to New Zealand's Privacy Act 2020.

8. Cookies

We use one session cookie to keep you signed in. It is HttpOnly (scripts cannot read it), Secure (sent over HTTPS only) and SameSite=Lax (sent only to Clearly's own sites). Google Analytics may set its own cookies on our website; you can block them with Google's opt-out browser add-on.

9. Your rights

Under New Zealand's Privacy Act 2020 you can ask for the personal information we hold about you, ask us to correct it, and ask us to delete it.

• Disconnect a platform: open Sources and choose Disconnect. This deletes our stored credentials for it. You can also remove our access from the platform's own settings, for example your Google Account's third-party access page.
• Delete a conversation: delete it from the Ask Why sidebar.
• Clear your business profile or a saved note: on your Profile page.
• Delete your account: on your Account page. This cancels any subscription and permanently deletes your reports, sources, credentials, business profile, Ask Why conversations and notes, sign-in details and the account record. Billing records stay with Stripe as the law requires, and backups age out within 8 weeks.

For anything else, or to make a request under the Privacy Act, contact us at the address below.

10. Security

All data travels over HTTPS. Google credentials are encrypted at rest with AES-256-GCM, using a key held in our server secrets, never in source code or logs. We do not log the contents of your platform data. Access to our systems is limited to the people who run the Service.

11. Children

The Service is not meant for children, and we do not knowingly collect information from anyone under 16.

12. Changes to this policy

We may update this policy. We will tell you by email or in the Service about any material change before it applies. The "Last updated" date shows the current version.

13. Contact

Questions or requests about this policy:

Enviroware Ltd, trading as Clearly
New Zealand
admin@clearly.report