Privacy Policy — Wren

Privacy Policy

Last updated: August 31, 2026

1. Introduction

Wren is operated by Vantage Ventures, LLC, a North Carolina limited liability company doing business as Wren (“we,” “our,” or “us”). Vantage Ventures, LLC is the data controller for the personal data described in this policy. We operate an AI-assisted writing platform that helps founders and executives create LinkedIn content (the “Service”). This Privacy Policy explains what information we collect, how we use and share it, the choices you have, and your rights under applicable privacy laws including the EU General Data Protection Regulation (“GDPR”), the California Consumer Privacy Act as amended by the California Privacy Rights Act (“CCPA/CPRA”), and other US state privacy statutes.

By accessing or using the Service you acknowledge that you have read this Privacy Policy. If you do not agree with our practices, please do not use the Service.

2. Information We Collect

2.1 Information You Provide

2.2 Information Collected Automatically

2.3 Information from Third-Party Sources

3. How We Use Your Information

We use the information we collect for the following purposes:

3.1 Lawful Bases for Processing (GDPR)

If you are located in the European Economic Area (EEA), United Kingdom, or Switzerland, we rely on the following lawful bases under GDPR Article 6:

4. AI Processing & Third-Party Services

The Service relies on third-party providers to function. We share only the minimum data necessary with each provider.

4.1 AI Service Providers

To power text generation (drafts, outlines, critiques, idea scoring) and image generation features, we send your content to third-party AI model providers. The data sent may include your writing content, voice-profile context, chat messages, and image prompts. AI providers process this data as sub-processors on our behalf and may retain inputs and outputs for a limited period for trust and safety purposes. Each one is named on our subprocessor list.

We require that all AI providers we use do not use your data to train or improve their AI models. We enforce this through our commercial agreements and by selecting API tiers that contractually prohibit training on customer data. The specific AI models and providers we use may change over time as we improve the Service. Our current providers include Anthropic and OpenRouter. Each provider's own privacy policy governs their data handling practices.

4.2 Supabase

We use Supabase for user authentication (including Google OAuth) and as our primary database (PostgreSQL). Your account data, content, and application data are stored in Supabase's infrastructure. Data is encrypted at rest and in transit.

4.3 Railway

Our application is hosted on Railway's cloud infrastructure. Server logs may temporarily contain request metadata (IP addresses, timestamps, and endpoints) for operational purposes.

4.3a PostHog

We use PostHog for product analytics, hosted in the United States. It receives usage and interaction data — the events and pages that tell us how Wren is used — together with an identifier for your account and standard device and browser information. It does not receive the content you create or connect: your drafts, ideas, writing samples, voice profile, LinkedIn post text, or your LinkedIn analytics. See Section 8.

4.4 LinkedIn

If you connect your LinkedIn account, we use LinkedIn's official API for one thing only: publishing a post when you explicitly ask us to. We do not post to LinkedIn on your behalf without your explicit action.

Your post analytics do not come from an API. LinkedIn does not make per-post analytics available to us that way. If you install the optional Wren browser extension and turn on analytics capture, the extension reads those numbers from your own LinkedIn pages in your own browser — see Section 14, which describes exactly how that works and what it means for your LinkedIn account. If you do not install the extension, we have no analytics about your posts at all.

If LinkedIn grants us access to its member analytics API and you authorize it, we will retrieve your own post analytics through that API instead, and the commitments in this section apply to that data in the same way.

We use LinkedIn data solely to provide analytics and content performance features within the Service. Your LinkedIn data is subject to LinkedIn's Privacy Policy. Key commitments regarding your LinkedIn data:

4.5 Telegram Bot API

If you opt in to the Telegram integration, messages you send to our Telegram bot are relayed through Telegram's Bot API. Telegram's own privacy policy governs the processing of data on their platform. We store only the content necessary to save ideas from your messages.

4.6 Google OAuth

If you choose to sign in with Google, we use Google's OAuth 2.0 service. We receive your name and email address. We do not access your Google contacts, calendar, or other Google data.

4.7 Resend

We use Resend to deliver account and service messages and, when enabled in your preferences, lifecycle product emails such as onboarding help, recovery nudges, nurture, and product education. Resend receives your email address and the rendered message. For lifecycle mail we also send an opaque delivery identifier and category tag; we do not send your pricing tier, product history, lifecycle state, or achieved outcomes as provider tags. Open and click tracking is disabled unless we later enable it and update this policy first.

5. Data Sharing & Disclosure

We do not sell your personal information. We do not share your personal information for cross-context behavioral advertising. We disclose data only in the following circumstances:

6. Data Retention

We retain your data for as long as your account is active or as needed to provide the Service. Specific retention periods:

When you delete your account, we cancel pending lifecycle email and delete account-linked lifecycle preferences, delivery history, and measurement events within 30 days. We otherwise delete or anonymize your personal data within a reasonable timeframe, except where retention is required by law or for legitimate business purposes (e.g., fraud prevention, legal compliance). Backups containing your data may persist for a limited period before being overwritten.

7. Data Security

We implement appropriate technical and organizational measures to protect your personal data, including:

No method of transmission or storage is 100% secure. While we strive to protect your data, we cannot guarantee absolute security. If we become aware of a data breach that is likely to result in a risk to your rights and freedoms, we will notify affected users and relevant supervisory authorities in accordance with applicable law (within 72 hours under GDPR).

8. Cookies & Tracking Technologies

We use essential cookies for authentication and session management. These are strictly necessary for the Service to function and cannot be opted out of.

We also use analytics cookies and similar technologies through PostHog, our product-analytics provider, to understand how Wren is used so we can improve it. On our public marketing pages this includes an identifier stored on your device so we can recognise a returning visit. Inside the product, analytics are recorded on our servers against your account, not through anything stored on your device.

We do not record session replays or screen recordings of your use of Wren, and we do not use PostHog’s autocapture — the events we record are the specific ones we have chosen and documented, not everything you click.

What we never send to our analytics provider is the content you create or connect: your drafts, ideas, outlines, writing samples, voice profile, LinkedIn post text, or your LinkedIn analytics.

We do not use advertising cookies, advertising pixels, or third-party ad networks, we do not track you across other websites, and we do not sell or share your personal information with advertisers or data brokers.

We honor Global Privacy Control (GPC) and Do Not Track (DNT) signals. We do not sell or share personal information, and we do not engage in cross-site tracking or cross-context behavioral advertising — so there is nothing for these signals to switch off. They do not disable the product analytics described above, which we use only to operate and improve Wren.

9. International Data Transfers

Our Service is operated from the United States. If you are located outside the United States, your data will be transferred to and processed in the United States and potentially other countries where our service providers operate.

For transfers from the EEA, UK, or Switzerland, we and our sub-processors rely on applicable lawful transfer mechanisms, which may include Standard Contractual Clauses (SCCs) and the EU-US Data Privacy Framework. You may contact us for more information about the safeguards in place for international transfers.

10. Your Privacy Rights

10.1 Rights for All Users

Regardless of where you are located, you may:

10.2 Additional Rights — EEA, UK & Switzerland (GDPR)

If you are located in the EEA, UK, or Switzerland you also have the right to:

10.3 Additional Rights — California (CCPA/CPRA)

If you are a California resident, you have the following additional rights under the CCPA/CPRA:

To exercise any of these rights, contact us at legal@writewithwren.com. We will respond to verifiable requests in accordance with applicable law — generally within 30 days for GDPR requests and 45 days for CCPA/CPRA requests, with extensions permitted where reasonably necessary. We will not charge a fee for responding to your request unless it is manifestly unfounded or excessive.

10.4 Additional US State Privacy Rights

Residents of other US states with comprehensive privacy laws may have similar rights, including the right to access, correct, delete, and port personal data, and to opt out of targeted advertising and profiling. To exercise these rights, contact us using the information in Section 15.

11. AI-Specific Disclosures

Wren uses artificial intelligence to generate content suggestions, drafts, outlines, critiques, and idea recommendations. Key facts about our AI processing:

12. Children's Privacy

The Service is not directed to individuals under the age of 16 (or the applicable age of digital consent in your jurisdiction). We do not knowingly collect personal information from children. If you believe we have inadvertently collected data from a child, please contact us immediately and we will promptly delete it.

13. Changes to This Policy

We may update this Privacy Policy from time to time to reflect changes in our practices, technology, legal requirements, or other factors. When we make material changes, we will:

We encourage you to review this page periodically. Your continued use of the Service after changes become effective constitutes acceptance of the revised policy.

14. Analytics Browser Extension

Wren offers an optional Chrome browser extension (“Wren LinkedIn Analytics”) that you install yourself and connect to your own Wren account. The extension is entirely opt-in: it does nothing until you install it and enter your personal Wren analytics-ingest token. This section describes exactly what the extension does, the data it handles, and why it requests each permission. We describe the mechanism candidly so you can make an informed choice.

14.1 What It Does

The extension works in two modes, and you choose them separately. When you install it, it can do a one-time read of your own profile and recent posts to set up your account faster. Keeping your analytics up to date on an ongoing basis is a separate step you turn on deliberately, and can turn off at any time — it is off until you choose it.

The extension reads your own LinkedIn post analytics — the impression, reaction, comment, and reshare metrics that LinkedIn shows you for posts on your own account, on the LinkedIn analytics and recent-activity pages you are already logged in to. It then sends those metrics to your Wren account so your content performance is available inside Wren. It only ever reads the analytics of the logged-in LinkedIn account using the browser; it does not access other members' private data.

So that it does not interrupt what you are doing, the extension opens those pages in a small background window rather than in the tab you are using. Browsers pause rendering for windows that are not on screen, so the extension signals to the page that it is visible — otherwise your own analytics would never load there and there would be nothing to read. That signalling is limited to LinkedIn analytics pages and affects only whether the page draws its contents in that background window.

Versions of the extension released before August 2026 also opened the audience-demographics breakdown on each post and recorded it. Current versions no longer collect that, and Wren links you to LinkedIn's own page for it instead. If you have an older version installed, it will continue to collect demographics until it updates.

14.2 Where Your Data Goes

The captured analytics are sent only to your own Wren account, over HTTPS, to Wren's analytics-ingest endpoint on app.writewithwren.com (or, for local development, a localhost endpoint you configure yourself). The data is authenticated with the personal ingest token you enter in the extension's options. We do not share this data with any third party, and we do not sell it. Once in your Wren account it is handled under this Privacy Policy like any other LinkedIn analytics data (see Section 4.4).

14.3 Permissions and Why They Are Needed

These are every permission the published extension requests, and why. If a future version needs another one, it appears here.

14.4 Your Control

The extension runs only while it is installed and configured with your token. You can pause it, clear its token, or uninstall it at any time from Chrome's extensions page, which immediately stops all capture. Uninstalling removes its locally stored settings. To remove the analytics already synced to your Wren account, see your LinkedIn data rights in Section 4.4 and your general rights in Section 10.

15. Contact Us

If you have questions, concerns, or requests related to this Privacy Policy or your personal data, please contact us:

If you are located in the EEA and believe we have not adequately addressed your concern, you have the right to lodge a complaint with your local data protection supervisory authority.