Privacy Policy

Last updated October 25, 2026 · Version 2026-10-25

This policy explains what information Wrenhouse collects, why, how long we keep it, who helps us run the service, and the choices and rights you have. It covers our customers and the people on their teams, people who visit our website or use our chat, and businesses we contact about Wrenhouse.

1. Our promises

• Your data stays yours. Each customer's hub is kept separate. No customer can see another customer's information, and we never share one customer's data with another.
• Your content never trains AI. We don't use what's in your hub to train AI models, ours or anyone else's. The AI provider we use doesn't train on it either.
• We don't sell or rent information. We don't share it for advertising, and we don't build advertising profiles.
• Learning only reads. When your hub learns from a tool, it only reads. Nothing is sent, posted or changed in your tools unless a person on your team approves it, or your super admin switches that automation to run on its own.
• You can see what we did. You can see what your hub learned, and every time Wrenhouse staff opened your hub is logged with a reason.

2. Who is in charge of what

Information about your business and your clients. When your organization uses Wrenhouse, your organization decides what goes into its hub and which tools to connect. For that information, including details about your own customers and contacts, your organization is in charge (the "controller" under some laws) and Wrenhouse acts on its instructions to run the hub (the "processor" or "service provider"). We don't use it for any other purpose. If you are a client of one of our customers and want to make a request about your information, please contact that business first. We'll help them respond.

A data processing agreement (DPA) is available on request at support@wrenhouse.io.

Everything else. For our own records, such as account and billing details, website and chat visitors, and businesses we contact about Wrenhouse, Wrenhouse is in charge of the information and this policy applies directly.

3. What we collect

Information you give us

• Account details: your name, work email, a scrambled (hashed) copy of your password if you set one, your role, and the hub you belong to.
• Onboarding answers: what your business does, your team, your goals and the tools you use, plus your website address if you share it. If you tap the microphone to talk an answer instead of typing it, your own web browser turns your speech into text (for example Chrome uses Google's speech service, Safari uses Apple's), under that browser maker's own privacy terms. Only the text reaches us. We never receive or keep the audio.
• Hub content: the work, notes, drafts, records, files and messages your team creates or handles in the hub.
• Branding: your company name, logo and colors if your super admin uploads them.
• Support and chat: the questions, tickets and emails you send us.
• Live help transcripts: only if you agree at the start of a live help call, a written transcript of what you and our staff say and type during that call. It is saved on your support ticket and used to write your follow-up. Either side can stop it at any time, and we never record the audio. Speech is turned into text by your own web browser (for example Chrome uses Google's speech service, Safari uses Apple's), under that browser maker's own privacy terms.
• Billing: your billing contact, plan, invoices and payment status. Card and bank details are entered with our payment providers, not stored by us.
• Agreements: when you sign an agreement with us, the name you type, the time, and a record of what was signed.

Information collected automatically

• Logs: IP address, browser and device type, pages requested, and errors, used to keep the service running and safe.
• Activity: sign-in times, when people were last active, and important actions such as approvals, role changes and exports. Your super admin and the people they allow can see team activity.
• AI usage: how much AI your hub uses, so we can manage costs and limits.

Information from other sources

• Sign-in providers: if you sign in with Google or Microsoft, we receive your name, email and a profile picture if you have one.
• Tools you connect: see the next section.
• Your public website: if your super admin agrees, the hub reads your public web pages to learn about your business.
• Documents you add: SOPs, checklists, policies and similar files your team chooses to add. The hub reads each one once to learn how you work, keeps only short lessons linked to the document's name, and doesn't keep the file. Deleting a document in the hub deletes what it taught.
• Public business information: for our own sales, business contact details that companies publish about themselves (see "Businesses we contact" below).

We ask people not to put card numbers, bank details, government ID numbers, passwords or health information into the hub. If they turn up, the hub masks them before anything is learned from them.

4. Tools you connect, and learning

Your team can connect tools such as email, a calendar, a CRM, a help desk, an issue tracker, team chat or a business system like a TMS. When you do:

• We use the connection only to run your own hub, and only within the permissions you grant in that tool. You can disconnect it at any time, in the hub or in the tool itself.
• Each person controls their own mailbox and calendar connections. A mailbox's messages are shown only to the person who connected it.
• The keys that let us reach your tools are stored encrypted. When you disconnect a tool, we delete its stored access and, where the tool allows it, revoke it with that tool too.
• Learning is a separate switch. The hub learns from a mailbox, calendar or tool only after it is switched on for that connection. It is off until someone turns it on, and every switch on or off is logged. When your team sends a reply the hub drafted, the hub learns from what was changed, such as greetings, sign-offs and who gets copied, so the next draft is closer.
• What learning keeps. Short lessons and patterns, such as "quote requests mostly arrive on Mondays", each linked to where it came from. Not copies of every message. Lessons about one person's writing style are visible only to that person.
• You can see and undo it. The "What your hub knows" page lists every source and every lesson. You can correct a lesson, dismiss it, or turn off a source and delete everything learned from it.

Google user data. Wrenhouse'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. We use Gmail, Google Calendar and Google contacts data only to provide and improve the features you use in your hub. We don't use it for advertising, don't sell it, and don't let people read it except with your permission, for security, or where the law requires.

Microsoft and other tools. We follow the same rules for Microsoft 365, Outlook, help desks such as Zendesk, Freshdesk, Help Scout and Intercom, work trackers such as Jira, Linear and GitHub, Slack, and every other tool you connect: your data is used only for your hub's features, and only as that tool's terms allow.

5. How AI is used

• Wrenhouse uses Anthropic's Claude models to read, sort, summarize and draft. To do that, the relevant part of your hub content is sent to Anthropic through its business API, processed, and returned.
• Under Anthropic's commercial terms, what we send isn't used to train its models. We don't train any models on your content either.
• AI can make mistakes. That's why drafts wait for a person to approve them unless your super admin turns on automatic mode, why anything about money, contracts or legal matters and every first message to someone new always waits for a person, and why every answer the hub drafts points to where its facts came from.
• The one exception is Wrenhouse's own support: Wren, our AI support assistant, answers the support requests you send us on its own, at any hour, and says it is an AI. A person from our team steps in whenever you ask, and always answers anything urgent or about billing, your data or security.
• We don't use AI to make decisions about people that have legal or similarly significant effects on them, such as hiring, credit or housing decisions. Your team makes those decisions.

6. How we use information

• To run your hub: sign-in, your pages, your team's work, drafts, automations and reports.
• To design and improve your hub, including learning from the sources you turn on.
• To give support, fix problems and answer questions.
• To keep Wrenhouse safe: preventing abuse, fraud and unauthorized access.
• To bill you and keep business records.
• To improve Wrenhouse itself, using usage counts, errors and feedback. Never your hub content for training AI.
• To contact you about your account, service changes and, if you agree or the law allows, new features. You can opt out of marketing at any time.
• To meet legal duties and enforce our Terms.

7. Who we share it with

• Your own team, as your super admin sets in each person's access.
• Service providers that help us run Wrenhouse, listed below, under contracts that limit what they can do with it.
• Tools you connect, when your team approves an action that sends something to them, or when your super admin has turned on automatic mode for that work. Automatic replies go out from the sender's own connected mailbox.
• Legal reasons: when the law requires it, or to protect people's safety or our rights. Where we're allowed to, we tell the customer first.
• Business changes: if Wrenhouse is merged or sold, information moves under the same promises, and we'll tell you before that happens.

8. Service providers

These providers process information for us. Each one gets only what it needs to do its part.

Before a new provider handles your hub content, such as a meeting note taker, we'll add it here and tell your super admin. Stripe will be added here before we start taking card payments.

9. When Wrenhouse staff open your hub

Wrenhouse staff open a customer's hub only to help, for example on a support ticket, during onboarding, or to fix a problem. Every visit is tied to a ticket or a stated reason and is recorded with who, when and why. Your super admin can see this access log, and it is being added to your hub's Settings so you can check it any time. During a live support session, a banner shows and you can see where we are pointing. A transcript is kept only if you allow it, and a notice shows on both screens while it is on. We never take control of your screen without a separate yes from you, and you can stop it at any time.

10. Cookies and similar tools

There's no cookie banner because we don't use cookies for ads, analytics or tracking.

Our website, wrenhouse.io, sets no cookies at all. It keeps two small things in your own browser, and they never leave your device:

• Your light or dark choice, kept until you clear your browser's storage.
• An open chat bubble conversation, cleared when you close the tab.

The app, app.wrenhouse.io, uses only the cookies it needs to work:

• A sign-in cookie keeps you signed in for up to 30 days, or until you sign out.
• Short-lived security cookies protect signing in and connecting tools. They last about 10 minutes.
• Your browser's storage remembers small preferences, such as light or dark mode.

The app's pages load fonts from Google Fonts, so Google receives your IP address when an app page loads. Our website serves its own fonts.

Website analytics. Our website uses Cloudflare Web Analytics to count visits: which pages are read, where visitors come from, the kind of device and browser, and how fast pages load. It sets no cookies, doesn't fingerprint your device or follow you to other sites, and gives us totals, not a profile of you. The app doesn't use it.

Because we don't sell or share information for advertising, there's nothing to opt out of. We honor Global Privacy Control signals anyway. Any analytics we use are cookieless, like the website analytics above, or we'll ask for your consent first.

Website and chat visitors

The chat bubble answers questions from our help articles. We don't keep a record of a chat unless you choose to send it to us, for example to book a demo or reach support. When you do, we keep your name, email, company, your note, and the last few messages of the chat, so we can reply.

Booking a demo

When you ask for a demo, we keep what you give us on the form: your name, work email, company, role, website, industry, team size, which teams would use the hub, the tools you use, what takes your team the most time, your goal, and the times you picked. To come prepared, our AI assistant reads up to 12 public pages of the website you gave us (only pages anyone can see, and never pages your site asks robots not to read). It then writes a short briefing for the person meeting you and a first sketch of the hub we would set up. The briefing uses Anthropic's Claude models, and long numbers that look like card, bank or ID numbers are hidden before anything is sent. The briefing stays inside Wrenhouse and is used only to prepare for your meeting.

During the meeting, we take notes only if you agree first. If you do, our person's web browser turns what it hears into text, under that browser maker's own privacy terms. We never record the audio. The notes are used to write the recap email we send you, and you can ask us to stop or delete them at any time. Anything you send us is kept as described under How long we keep it.

Businesses we contact

To find businesses that may benefit from Wrenhouse, we keep public business contact details, such as a company name, website, work email or business phone number, that a business publishes about itself. We use them only to contact that business about Wrenhouse. Every sales email we send says who we are and how to stop. To opt out, reply "stop" or write to hello@wrenhouse.io. Your address then goes on a do-not-contact list so you're never contacted again, and we delete everything else we hold about you on request.

11. How long we keep it

Copies in our database backups age out within 30 more days after deletion.

12. Security, and if something goes wrong

Connections are encrypted in transit. Passwords are stored hashed, and the keys to your connected tools are stored encrypted. Every lookup is limited to one hub. Staff access is logged, and your super admin controls who is on your team and what they can do. No system is perfectly secure, so we keep watch for errors and misuse and fix problems quickly.

If your information is ever exposed, we'll tell your organization without undue delay, and within 72 hours of confirming it whenever we can: what happened, what information it affects, and what we're doing about it. We'll also notify regulators and people affected where the law requires.

13. Your choices

• See, correct, export or delete: email support@wrenhouse.io. Many changes you can make yourself in Settings.
• Learning: turn learning off for any source on the "What your hub knows" page, and delete what was learned.
• Connections: disconnect any tool at any time.
• Team members: your super admin can remove people and change what they can see or download.
• Marketing: reply "stop" to any marketing email, or write to hello@wrenhouse.io. Account and security emails still arrive while your account is open.

If you use Wrenhouse through your employer, some requests go through your organization's super admin, since they manage your hub.

14. Privacy rights in US states

Residents of California and other states with privacy laws, including Colorado, Connecticut, Virginia, Utah, Texas and Oregon, have rights over their personal information. Depending on where you live, you can ask us to:

• Tell you what personal information we collect, use and disclose, and give you a copy.
• Correct information that's wrong.
• Delete your information.
• Not sell or share it for targeted advertising. We don't do either.
• Limit the use of sensitive information. We don't use sensitive information to infer things about you.

California notice. In the past 12 months we have collected: identifiers (such as name, email and IP address), commercial information (plan and billing), internet activity (logs and usage), professional information (role and company), and the contents of messages and records your organization chooses to connect. We collect them for the purposes in section 6 and disclose them only to the providers in section 8 and as described in section 7. We have not sold or shared personal information, and we don't knowingly collect information from anyone under 16.

How to make a request. Email support@wrenhouse.io with "Privacy request" in the subject. We'll confirm who you are before acting, answer within 45 days, and tell you if we need more time. You can use an authorized agent, and we may ask them for proof of permission. If we turn down your request, you can appeal by replying with "Appeal" in the subject, and we'll answer within the time your state's law allows. We'll never treat you differently for using your rights.

15. People in the EEA, UK and Switzerland

Where these laws apply, we rely on these legal bases: performing our contract with you, our legitimate interests in running and securing the service and in contacting businesses about Wrenhouse, your consent (for example, learning from a connected source, which you can withdraw at any time), and legal obligations. You have the right to access, correct, delete, restrict or object to processing, and to receive your information in a portable form. You can also complain to your local data protection authority.

16. Where information is stored

Wrenhouse and its service providers are based in the United States, and information is stored there. When we move personal information from the EEA, UK or Switzerland, we use safeguards the law recognizes, such as standard contractual clauses.

17. Children

Wrenhouse is for businesses and people 18 and older. We don't knowingly collect information from anyone under 16. If we learn we have, we delete it.

18. Changes to this policy

We update this policy whenever we add a feature, a connection or a provider that changes how information is handled. The date and version at the top always show the latest change. If a change matters, we'll tell your super admin before it takes effect, and the list below records what changed.

• October 25, 2026: Onboarding: you can talk an answer instead of typing it. Your browser turns speech into text, and only the text reaches us.
• October 25, 2026: Booking a demo: the extra details the demo form asks for, the public-website briefing we prepare before a meeting, and meeting notes taken only with your yes. When our assistant guides you on screen from the Get help chat, the steps it showed are saved on your support ticket.
• October 25, 2026: Support: Wren, our AI support assistant, answers support requests first; a person steps in on request and for anything urgent, billing, data or security.
• October 25, 2026: Live help transcripts: kept only when the person on the call agrees, saved on the support ticket, either side can stop, audio never recorded, and speech turned into text by the person's own browser.
• October 24, 2026: Full policy published, covering AI, connected tools and learning, staff access, cookies for the website and the app, retention, and US state, EEA and UK rights.

19. Who runs Wrenhouse and how to reach us

Wrenhouse is operated by Wrenhouse (full legal name to be added). Our mailing address will be listed here soon. For any privacy question or request, email support@wrenhouse.io.

This page describes how we handle information. It isn't legal advice. A lawyer will review it before our full launch.