Tapestry PRMYour relationship data stays on your device.
Unless you turn on Always-on, no Tapestry server stores what you connect or can read it. Your Tapestry account holds your email address and sign-in records, not your data. Here’s where your data lives, what leaves your device and why, and how to reach us about security.
Where your data lives
Everything you connect or create in Tapestry, from messages and events to contacts, notes and lists, stays in your Tapestry folder on your device. By default that’s .tapestry in your home folder.
Unless you turn on Always-on, no Tapestry server stores what you connect or can read it, so none of it is on our servers to breach, sell or hand over. Your Tapestry account holds your email address and sign-in records, not your data. Always-on’s copy is on our hosted service, where code we deploy can read it and a legal demand can reach it.
Tapestry’s own features don’t use cloud AI providers, and we never use your data to train AI models.
How your data is protected
Tapestry doesn’t encrypt its own database. Your Mac protects it, so turn on FileVault and keep macOS up to date.
- FileVault, your Mac’s built-in disk encryption, keeps it encrypted while your Mac is turned off. A Tapestry folder on another drive is protected only if that drive is encrypted. Tapestry tells you if the drive holding your data isn’t.
- On your Mac’s own disk, only your macOS account has permission to open your Tapestry folder. Apps you run can still read it, as they can your other files.
- App Lock, off until you turn it on in Settings, asks for Touch ID or your Mac’s password before Tapestry shows anything, and locks again after a while without use or when your Mac sleeps or its screen locks. It covers Tapestry’s window, not its files.
- Your Google authorizations, Granola key, Slack sign-ins, HubSpot tokens and Android texts pairing are kept encrypted in the macOS Keychain on your device, not synced to iCloud.
Copies are only as protected as where they’re kept. Time Machine backs up your Tapestry folder unencrypted unless the backup disk is encrypted. Don’t keep your Tapestry folder in iCloud Drive, Dropbox or another synced folder, because that copies your data to that service.
Read-only by design
- Every source is read-only. Tapestry can’t send, delete or change your email, messages, calendar or contacts.
- AI assistants you connect get read-only access, and only after you turn it on. They can ask questions; they can’t change your data.
- Tapestry never contacts anyone for you.
What leaves your device, and to whom
Tapestry connects to outside services only in these ways.
| What | Goes to | What it includes |
|---|---|---|
| Imports from your sources | Google and Granola | Requests for the source you connected, with your authorization for it |
| Slack, if you connect it | Slack (slack.com) | Requests with your Slack sign-in, to find and read the one-to-one direct messages you wrote in, their threads and the profile of the person on the other side. Disconnecting a workspace asks Slack to end the sign-in |
| HubSpot, if you connect it | HubSpot (api.hubapi.com) | Read-only requests with the token you pasted in, for the contacts, companies, deals and logged activity you chose |
| Map images | OpenStreetMap | Your IP address and the area of the map you view |
| A city name, to place people on the Map | OpenStreetMap Nominatim | The place name only, never names, email addresses or street addresses |
| An organization’s name and icon | That organization’s website, and the host of its icon | A request for its public home page and icon, with your IP address |
| An organization’s About and news, only when you press Refresh | That organization’s website, and Google News | Requests for its public home page and news feed; to Google News, the organization’s name (for a name that is just a web address, the name part of it) and your IP address, nothing else |
| News about a person, only when you press Refresh | The website saved on that contact, and Google News | A request for its news feed; to Google News, only if you saved where they work, the person’s name, the organization’s name and your IP address, nothing else |
| Profile photos | LinkedIn and Google | Photos you captured from LinkedIn, and Google Contacts photos with your Google authorization |
| What an AI assistant reads | The assistant you connect, and its provider | The people, excerpts and notes it asks about, only after you turn assistant access on |
| Remote access, if you turn it on | Tapestry’s relay, Let’s Encrypt, and Cert Spotter or crt.sh | Each approved assistant’s connection to your main computer, passed through encrypted so the relay can’t read it; requests for your main computer’s certificate; and a daily check of its address |
| Always-on, if you turn it on | Tapestry’s hosted service, on Amazon Web Services | An encrypted copy of what the assistants you approved may read, without your Gmail data, which our service reads to answer them while your main computer is off. |
| Your Tapestry account | Supabase, and Resend for its emails | Your email address, the codes you enter and your sign-in, with your IP address, when you use Settings → Account or open Ask. With remote access on, a daily check signed by your main computer. |
| Diagnostics | PostHog and Sentry | Usage, performance and errors with random IDs and, while you’re signed in, your account’s ID (never your email), never relationship content. Tapestry Capture’s also include your IP address and approximate location. On by default; turn them off in Settings → Privacy & security, or in Tapestry Capture’s popup. |
Our privacy notice describes each case in full, along with how this website and the waitlist handle information.
What we can’t see
Unless you turn on Always-on, our servers don’t store your local data, and our relay can’t read the remote access connections it passes on, so no one at AMS Global Ventures, LLC can read your local data, export it or delete it for you. You control it on your device.
Deleting everything
Open Settings → Data in Tapestry and choose Delete all Tapestry data on this device. Tapestry deletes your Tapestry folder, its Google sign-ins after asking Google to revoke them, its Granola, Fathom and Fireflies keys and Plaud sign-ins in the Keychain and its own settings, removes remote access from this device and signs it out of your Tapestry account, then starts again at the welcome screen. Disconnect each Slack workspace, HubSpot portal and Attio workspace first, which removes their sign-ins and tokens, and Android texts, which ends its pairing and deletes its Keychain item. If Always-on is on, it turns it off first, which deletes its copy. Your account stays until you delete it in Settings → Account. It lists what’s left for you to do elsewhere, such as removing the Tapestry Capture extension from Chrome. Backups you keep, such as Time Machine, may still hold an unencrypted copy of your Tapestry folder unless the backup disk is encrypted.
Who builds Tapestry
Tapestry PRM is built by Andrew Stroup. He co-founded CommonKey, a team password manager, served as a Pentagon subject-matter expert on chemical, biological, radiological and nuclear defense, and was Deputy Director of the White House Presidential Innovation Fellows. Why he’s building it.
Report a vulnerability
If you find a security problem in Tapestry PRM or this website, please help us understand and address it.
How to reach us
Email security@tapestryprm.com with the affected surface, reproduction steps and likely impact. Please keep private data out of the initial message and do not publish an exploit or someone else’s information.
What to expect
We aim to acknowledge reports within three working days and provide an initial assessment within ten. These are response targets, not guaranteed service levels. We will keep you informed as we investigate and discuss appropriate credit with you. There is no paid bounty programme.
Good-faith research
Use your own installation, accounts and data. Avoid accessing, changing or retaining anyone else’s information, denial-of-service testing, high-volume scans and social engineering. If you encounter private information unintentionally, stop and tell us. Give us reasonable time to investigate and fix an issue before disclosure.
We will not pursue legal action against research conducted in good faith under this guidance. We cannot authorise testing of another organisation’s systems or bind third parties.
Scope and impact
Reports may concern this website or Tapestry software provided for testing, including local services and source permissions. We assess issues by their demonstrated impact, including exposure of local data. A local architecture does not remove the need for secure storage, permissions and deletion.
Machine-readable contact
Our contact is also available at /.well-known/security.txt.