Who we are
Moat is the operating platform that Peak Edge Ventures Ltd (trading as Peak Edge Ventures, “PEV”, “we”, “us”) provides to the firms in its portfolio and to its own team. It connects the tools a firm already uses, such as email, its recruiting system and its phone system, to Claude, and stores the firm's shared skills, files and dashboards.
Peak Edge Ventures Ltd is registered in England under company number 13721971. Its registered office is Unicorn House, 2nd Floor, Station Close, Potters Bar, Hertfordshire, EN6 1TL.
PEV is the controller of the personal data described in this policy. Where a firm connects its own business systems to Moat, that firm also decides how its data is used, and its own privacy notice applies alongside this one.
This policy covers the Moat web app at moat.peakedgeventures.com, the Moat connector used from Claude apps, and the Moat Slack app.
Information Moat processes
Your account
Your name, work email address, the firm you belong to and your role, the sign-in records Moat needs to keep you signed in, and the preferences you set (for example your assistant's name and theme).
Connected apps
You or your firm can connect apps to Moat: Gmail and Google Calendar, Slack, Atlas (recruiting CRM), Granola (meeting notes), Ringover and Devyce (phone systems), and contact-finding and search services (Apollo, Exa, FullEnrich, AI Ark, Bright Data). A firm can also add other services of its own. Moat fetches from these apps what you ask for, when you ask for it, plus the scheduled imports described below.
Connection credentials
When you connect an app, Moat stores the sign-in tokens or API key it needs to act for you. These are kept encrypted in a separate secure store (Supabase Vault), never in the tables that hold the rest of your data, and are read only through restricted database functions. They are never shown back to you or anyone else, and they are removed from Moat's logs.
Recruiting data from Atlas
For firms that use Atlas, Moat keeps a nightly copy of the firm's Atlas records (candidates, prospects, companies, jobs, placements, fees, meetings, emails and notes) so it can build the firm's dashboards and reports. This copy is readable only by Moat's own services, not directly by users.
Calls and meetings
Where a firm connects Ringover or Devyce, Moat imports call records (date, direction, duration, outcome, the phone numbers and contact names involved) and the call transcripts the phone provider produces. Where Granola is connected, Moat can import meeting notes and transcripts. Moat does not store call audio. Transcripts are stored per person and used to show call and meeting figures and to suggest follow-up tasks.
Questions you ask
When it is switched on, Moat records the short questions you ask its analysis and dashboard tools (for example the title of an analysis you request, up to 500 characters) so PEV can see which questions firms need answered and improve the tools.
Usage information
Moat records which of its tools were used, by whom, when, whether they succeeded and how long they took. These usage records never include what you sent to a tool or what came back. When PEV turns on detailed logging to diagnose a fault, application logs can also hold parts of your requests and of connected apps' error replies, such as a search you ran and the start of the reply; logs are kept for 30 days. The Moat plugin in your Claude app reports which skill was used, never its inputs. Where your firm has set up usage reporting for Claude Code or Claude Cowork, PEV also receives usage events from those apps, which can include the text of prompts you type; PEV uses these to understand how Moat and its skills are used, and to give each person their own private feedback on how they use AI (Your AI, in the AI report). For that feedback, prompt text is read once a week and reduced to counts, such as how many asks were about outreach or were asked again; only those weekly figures are kept, never the prompts themselves. Each person's feedback is shown only to them, and their firm's founders and admins see firm-wide figures with no names, never for a group of fewer than three people.
Pages and files you publish
Files, skills, dashboards, memories and pages you save to Moat. When you publish a page you choose who can see it: only you, your firm, everyone signed in to Moat across PEV's portfolio, or anyone with the link.
Technical information
Your IP address and browser details appear in Moat's security logs. Moat also sets a cookie holding your approximate location (to about 11 km) so its theme can follow your local weather. To fetch that weather, your browser sends the approximate location to Open-Meteo, a weather service, which also sees your IP address.
Google user data (Gmail and Google Calendar)
Moat's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
What Moat accesses in Gmail
When you connect a Gmail account, Moat asks Google for permission to read, draft and send email and to see the account's email address. Moat uses that permission only to do what you ask:
- list and search your email threads and read the messages in a thread;
- list your Gmail labels so you can filter by them;
- create drafts for you to review;
- send an email once you have confirmed it;
- when you share a file or skill with a colleague who is not on Slack, send them a short notice from your Gmail account.
Moat does not delete your email or change its labels.
What Moat accesses in Google Calendar
When you connect Google Calendar, Moat lists your calendars, checks when you are free, looks up names and email addresses in your Google contacts to fill in attendees, and creates the events you ask for. It does not read the details of your other events.
What Moat keeps
Moat does not keep a copy of your mailbox. It stores the email address of each account you connect, its encrypted tokens while it stays connected, and a record of each email sent or drafted through Moat (recipients, subject, the first 500 characters and Gmail's message identifiers) for security and audit. When detailed logging is on and a Gmail request fails, application logs keep the full search, the Gmail account it was for and up to 500 characters of Google's reply, for 30 days. If you turn on a scheduled Gmail automation for your own inbox, which today only PEV's own team can do, Moat reads the messages it matches on a schedule, saves the results to your private Moat files and may create drafts for you; it never sends email from an automation.
What Moat never does with Google data
- It does not sell it.
- It does not use it for advertising.
- It does not use it to train or improve AI models, Moat's or anyone else's.
- It does not transfer it to anyone except to provide the features you ask for, to keep the service secure, or where the law requires it.
- PEV staff do not read it unless you ask us to (for example to help with a problem), it is needed for security, or the law requires it.
Removing access
You can disconnect Gmail or Google Calendar on Moat's Connected apps page. Moat then deletes the stored sign-in and asks Google to revoke its access. You can also revoke Moat's access at any time from your Google Account permissions.
How Moat uses AI
Moat is used from Claude, Anthropic's AI assistant. When you ask Claude to do something with your data, for example to summarise an email thread, Moat returns that data to the Claude app you are using. How that app handles it is governed by your or your firm's agreement with Anthropic.
Some Moat features also send data to Anthropic's Claude models from Moat's own servers: suggesting follow-up tasks from call and meeting transcripts, answering questions put to MoatBot in Slack, reviewing skills, and the scheduled Gmail automation described above. These requests use PEV's commercial Anthropic account, under terms in which Anthropic does not train its models on the content.
Moat does not use your data to train or fine-tune any AI model.
Why we use information
- To provide Moat to you and your firm under PEV's arrangement with the firm: running the tools, imports and dashboards you use.
- With your consent when you connect an app such as Gmail or turn on an automation. You can withdraw it by disconnecting the app.
- For our legitimate interests in keeping Moat secure, fixing faults, and understanding how it is used so we can improve it.
- To meet legal obligations, where they apply.
Where data is stored
Moat's database and files are stored with Supabase in the European Union (Ireland). Some providers, including Anthropic, may process data in the United States. Where data leaves the UK, we rely on safeguards recognised under UK data protection law, such as the UK International Data Transfer Agreement or Addendum.
How long we keep data, and deletion
- Your account, files, skills and pages: for as long as you use Moat, or until you ask us to delete them.
- Connected-app credentials: when you disconnect an app, Moat deletes its stored credential. For Gmail and Google Calendar, Moat also asks Google to revoke its access, so reconnecting means signing in again.
- Atlas copy: refreshed nightly and kept while your firm uses Moat. Some records removed from Atlas are also removed from Moat after two full refreshes; candidates, prospects and emails are kept, with Atlas's record that they were deleted, until your firm leaves Moat or asks us to delete them.
- Call and meeting transcripts, and questions you ask: kept until deleted on request, or when your account or firm leaves Moat.
- Records of emails sent or drafted through Moat: kept with your account.
- Application logs and error reports: 30 days.
- Expired sign-in tokens: removed 30 days after they expire.
- Published pages: you can take a page down at any time, after which it is no longer served.
To have your account or any of this data deleted, email privacy@peakedgeventures.com. When we delete an account, we delete the personal data held against it, including its stored credentials, transcripts and files, except where the law requires us to keep something.
Security
- All traffic to Moat is encrypted in transit.
- Connection credentials are encrypted at rest in a separate secure store.
- Your sign-in session is held in an encrypted, browser-inaccessible cookie.
- Each firm's data is kept apart by row-level security in the database, which is tested to confirm one firm cannot read another's data.
- Access to sensitive operations is limited by role, and emails sent through Moat are logged.
Your rights
Under UK data protection law (UK GDPR) you have the right to:
- access the personal data we hold about you;
- have inaccurate data corrected;
- have your data deleted;
- restrict or object to how we use it;
- receive your data in a portable format;
- withdraw consent you have given, such as for a connected app.
To use any of these rights, email privacy@peakedgeventures.com. If you are unhappy with how we handle your data, you can complain to the Information Commissioner's Office at ico.org.uk.
Changes and contact
We will update this policy when Moat's handling of data changes, and change the effective date above. For any question about this policy or your data, email privacy@peakedgeventures.com.
Peak Edge Ventures Ltd (trading as Peak Edge Ventures)Registered in England, company number 13721971
Registered office: Unicorn House, 2nd Floor, Station Close, Potters Bar, Hertfordshire, EN6 1TL