Privacy Policy

1. Introduction

Edition House ("we", "us", or "our") helps businesses review their marketing content for compliance and grow their search traffic. The Service reviews website pages, LinkedIn posts and advertising copy, connects to Google services you choose to connect, and uses AI to recommend, draft and improve content.

This Privacy Policy explains what data we collect, how we use it, who we share it with, and the choices you have. Section 6 describes exactly how we handle data we receive from Google. Please also read our Terms of Service.

2. Data We Collect

2.1 Account information

When you create an account we collect your name, email address and business details, such as your company name and website address. If you sign in with Google, we receive your name, email address and profile image from your Google account. We use this information to authenticate you and to associate your data with your organisation.

2.2 Website and social content

When you add a website, we crawl the publicly accessible pages of that website. We store page text, headings, claims, disclaimers and page structure so that we can analyse them. If you ask us to review LinkedIn content, we collect the publicly available posts from the LinkedIn pages you name.

2.3 Data from Google services you connect

If you connect Google Search Console, Google Analytics or Google Ads, we receive data from those services. If you open a brief or draft in Google Docs, we create that document in your Google Drive. Section 6 describes this data and how we use it.

2.4 Content you create with the Service

We store the briefs, drafts, edits, fact-check results and review decisions that you and the Service create, together with a history of changes, so that you can review, approve and measure your content.

2.5 Publishing destinations

If you connect a publishing destination, we store the details needed to use it:

• GitHub — our GitHub App has read-only access to the repositories you select. We read files to find and check your pages. We cannot write to your repositories; branches and pull requests are created by a runner that you operate under your own GitHub access.
• WordPress — we store your site address and an application password or authorisation token, encrypted, so that we can create drafts on your WordPress site.

2.6 Billing information

Payments are processed by Stripe. We store your plan, your subscription status and your billing history. We do not store your card number; Stripe holds your payment details.

2.7 Usage data, cookies and advertising measurement

We collect standard usage data, such as pages visited, features used, browser type and IP address, to operate the Service and to diagnose problems. Section 10 describes the cookies and measurement tools we use.

3. How We Use Your Data

We use the data we collect to:

• Provide the Service — analyse your content against regulatory rules, show search performance and opportunities, recommend improvements, and draft and improve content at your request.
• Deliver content where you choose — send drafts to the publishing destination you connect, according to the delivery settings you choose.
• Operate and secure the Service — authenticate you, take payments, prevent abuse and fix problems.
• Improve the Service — analyse aggregate usage patterns to improve features and accuracy. We do not use your content to train general-purpose machine learning models.
• Communicate with you — send account emails, results, service updates and replies to support requests.
• Measure our own marketing — understand which of our advertisements lead to sign-ups, as described in Section 10.

5. Data Sharing

We do not sell your data. We share data only in these circumstances:

• Service providers — companies that operate parts of the Service on our behalf, under contract: hosting (Vercel), database and authentication (Supabase), AI model access (OpenRouter and the model providers it connects to), web crawling (Firecrawl, Apify), search and keyword data (DataForSEO), image text recognition (Google Cloud Vision), image generation (Krea), email delivery (Resend) and payments (Stripe).
• Destinations you connect — we send content to the publishing destinations you choose.
• AI assistants you connect — if you authorise an outside AI assistant to use Edition House, we share the data covered by the permissions you approved with that assistant and its provider, as described below.
• Advertising measurement — limited sign-up and checkout events to Meta, as described in Section 10.
• Legal requirements — where the law, a regulator or a legal process requires us to disclose data.
• Business transfers — in connection with a merger, acquisition or sale of assets, subject to this policy.

5.1 Assistants you connect

Edition House publishes a connector that lets an outside AI assistant reach your account on your instruction. Nothing is shared until you sign in, see exactly which permissions are being asked for, and approve them. Each permission is shown and granted separately, so reading your pages and adding a draft to your queue are never one decision.

A connected assistant can act only on the businesses you approved it for — you choose them when you connect, and it loses a business as soon as you stop being a member of it — and only within those permissions. It cannot publish: the one permission that writes anything adds a draft to your Write queue for a person to review. You can disconnect an assistant at any time, and it stops working immediately for every business it covered.

Google data is shared with a connected assistant only under the permission that names it. “Read your Google Search Console data” shares the clicks, impressions, average positions and search queries described in Section 6.2. “Read your Google Analytics data” shares the visit, key event (goal) and AI-assistant visit totals described in Section 6.3; it starts unticked, and without it no Google Analytics figure is available to the assistant. We never share data about individual visitors.

What you share this way is handled by that assistant's provider under their own privacy policy, not ours. Read it before you connect.

Data we receive from Google is shared only as Section 6 permits.

6. Google User Data

This section describes how we access, use, store, share and delete data we receive from Google APIs. We access each Google service only after you authorise it through Google's own consent screen, and only for the account or property you choose.

6.1 Google sign-in

If you sign in with Google, we receive your name, email address and profile image. We use them only to create and authenticate your Edition House account.

6.2 Google Search Console (read-only)

We read search performance data for the Search Console property you choose: search queries, pages, clicks, impressions, average position and country, and the indexing status of your pages. We use it to show your search visibility, track rankings, find content opportunities and measure the effect of changes. We store this data with your account.

6.3 Google Analytics (read-only)

We read the list of your Google Analytics properties and their website addresses, so that we can match a property to your website, and the property's name, time zone and currency. We also read the list of key events (the conversions you have set up, such as a form submission or a purchase), with each one's name, counting method, default value and the date it was created, and how often each one happened recently, so that you can see which ones fire before you choose one. From the property you choose, we read these daily totals:

• all sessions, and sessions, engaged sessions and key events for each traffic source;
• key events and their value for each traffic source;
• sessions, engaged sessions, key events and their value for each landing page on your website, for each channel (such as organic search).

We use these totals to:

• show how many visits reach your website from AI assistants such as ChatGPT, Perplexity, Gemini and Copilot, what share of all your sessions they make, and how many of your goals they lead to;
• show, for the key event you choose as your goal (for example leads or sales), how many goals each page earns from search and whether that number is changing;
• report what an SEO change did to your goal and, when there is enough volume to measure it, use your goal to decide the result of that change;
• put pages that turn visits into goals at a clearly higher rate than the rest of your website earlier in the list of suggested improvements, and do the same for new article ideas when your pages with the same search intent do so;
• estimate how many goals a search query or a suggested change could bring, always shown as an estimate;
• include these results in the emails we send you about your SEO changes, and, when report summaries are switched on for your business, write the short summary paragraph of that report (Section 4).

We store only these daily totals, the list of key events and the goal you choose. We do not read data about individual visitors, and we never change anything in your Google Analytics account. We send these totals to an AI provider only in the two cases Section 4 describes: an AI assistant you connect and give the “Read your Google Analytics data” permission, and the summary paragraph of your report, when report summaries are switched on for your business.

6.4 Google Ads (read-only)

If you connect Google Ads, we read campaign structure, performance metrics (such as impressions, clicks, conversions, cost and conversion rates) and your ad copy, including headlines and descriptions. We use this data to review your ad copy for compliance and to show performance reports. We do not change your campaigns. Our use of data from the Google Ads API also complies with the Google Ads API Terms of Service.

6.5 Google Drive (only to create documents you ask for)

If you choose “Save to Google Drive” for a brief or draft, we ask Google for permission to create files in your Google Drive. This permission lets us see and change only the files that Edition House creates. It does not let us see, read or list any other file in your Drive.

We use the permission once: to upload the brief or draft you chose, which Google turns into a new Google Doc, and then to send you to that document. We do not store the permission, it expires within an hour, and we do not open the document again after we create it. We do not keep the document's address or anything else from your Drive. The document is yours, in your own Drive, and you can move, share or delete it like any other file.

6.6 Limited Use

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

• We use Google user data only to provide and improve the features you see in the Service.
• We do not sell Google user data, and we do not use it for advertising, including personalised or retargeted advertising.
• We transfer Google user data to third parties only when it is necessary to provide a feature you use (for example, sending Search Console queries to an AI provider to produce a recommendation for you, or answering an AI assistant you connected and gave permission to read that data), to comply with the law, or as part of a merger or acquisition with notice to you.
• We do not use Google user data to train general-purpose AI or machine learning models.
• Our staff do not read your Google user data unless you give us permission (for example, when you ask for support), it is necessary for security, it is necessary to comply with the law, or the data is aggregated and anonymised for internal operations.

6.7 Storage, protection and removal

We store the access credentials Google issues to us encrypted (AES-256-GCM), and we make all Google API requests from our servers, so that credentials are never exposed to your browser. The Google Drive permission in Section 6.5 is not stored at all. Data is stored in our database, isolated to your organisation.

You can disconnect a Google service at any time in your Settings. When you disconnect, we delete the stored credential and stop collecting new data from that service. Google Drive has nothing to disconnect, because we keep no credential for it. You can also remove our access in your Google Account permissions. To delete Google data we have already collected, contact us at hello@edition.house; we delete it within 30 days of your request.

7. Data Retention

We keep your account information, content, analysis results and connected-service data for as long as your account is active, because the Service compares data over time. You can ask us to delete your account or any part of your data by contacting hello@edition.house. We delete your personal data within 30 days of your request, except where the law requires us to keep it. Stripe keeps payment records as its own obligations require.

8. Data Security

We protect your data with encryption in transit (TLS) and at rest, encrypted storage of connection credentials, isolation of each organisation's data, and access controls. No system is completely secure, and we cannot guarantee absolute security.

9. Your Rights

Depending on where you live, you may have the right to:

• Access the personal data we hold about you.
• Request correction of inaccurate data.
• Request deletion of your data.
• Object to or restrict certain processing.
• Receive your data in a portable format.
• Withdraw a consent you have given.

To exercise any of these rights, contact us at hello@edition.house.

10. Cookies and Advertising Measurement

We use essential cookies to keep you signed in. On our website and in the Service we also use:

• Google Analytics — to understand how visitors use our own website. This is separate from any Google Analytics account you connect under Section 6.3.
• Meta Pixel and Conversions API — to measure whether our Meta advertisements lead to sign-ups. When you start a registration, complete a registration, start a checkout or connect Search Console, our server sends that event to Meta with your email address and an account identifier, both hashed (SHA-256), together with your IP address, browser type and Meta cookie identifiers. We never send Search Console or Google Analytics data to Meta.

You can block or delete cookies in your browser settings, and you can manage Meta's use of your data in your Meta account's ad settings.

11. Changes to This Policy

We may update this Privacy Policy. If we make material changes we will notify you by email or with a notice in the Service before they take effect. The date at the top of this page shows when it last changed.

12. Contact

If you have questions about this Privacy Policy or how we handle your data, contact us at hello@edition.house.