Coterie Security & Privacy
Smart CRM, LLC d/b/a Coterie
Last updated November 21, 2026
See also the Terms of Use.
Privacy and security are too important for legalese. Coterie does not own your data, nor do we sell it to others or use it for advertising. It's your data, period.
This policy applies to all information collected or submitted on Coterie's website and our apps, and to the invitation and event surfaces guests use. Coterie is operated by Smart CRM, LLC d/b/a Coterie.
The short version
- Your directory, your notes, your plans: yours. We store them to serve you and for nothing else.
- Guests are told, in the moment, what an invitation captures — and hosts can see their guests' conversations with their own invitations. We say that plainly here and on the invitation itself.
- The Social Secretary runs on a large language model. Your data is never used to train it — ours or anyone's.
- We never sell data, never advertise, and never message your people except as you direct.
Sign in
Sign-in uses an email magic link or Sign in with Google. Sign in with Google is a private, secure way to log in using your Google account and supports two-factor authentication. It does not give Coterie access to your Google credentials or any data stored on Google.
Your directory, and the people in it who aren't users
Most of the people in your Coterie are not Coterie users. Your directory — names, contact details, tags, notes, interaction history — is information you keep, the way your address book or diary would hold it, visible only to you.
- We store your directory to provide the service to you, and for no other purpose.
- Your notes are private to you, used only in your own search and displayed on the corresponding record. Note text is encrypted in storage and in transit.
- Contact information is only accessible to the user who added it. This isolation is reinforced with software safeguards.
- If someone asks what a host holds about them: a host's private notes are the host's own records — like their diary — and are not disclosed by Coterie.
- Guests can always ask us about, and request deletion of, their own conversations with invitations — see "Guests and invitations" below.
Contacts import
When you import contacts (for example, from your phone), Coterie references your contacts only to use the names and details you choose to import, after your review. Imported information is saved only to your account and is never shared. Coterie never messages your contacts except as you direct.
Guests and invitations
When a host invites you to a gathering, you can use the invitation without creating a Coterie account. Here is exactly what happens:
- What we collect from guests: your conversation with the invitation, your RSVP, and details you volunteer in conversation (a plus-one, a dietary note, "running late"), plus thank-yous and replies after the event.
- What the host sees: the host can see your conversation with their invitation and the information captured from it. Captured details are confirmed to you in the moment — the invitation tells you what it noted, when it notes it.
- What other guests see: nothing about you beyond what the host's visibility settings show (for example, whether a guest list is visible). Your conversation is never visible to other guests.
- What you can do: ask us what conversations we hold for your guest link, and request deletion of your conversation history through the contact form.
Co-hosting
Co-hosts share a gathering's plan and see the joint guest list — names and RSVP states. Co-hosts never see each other's directories, person records, or private notes, and a guest's conversation is visible only to the host who invited them. These walls are enforced in software, not in promises.
Invitation links
Every guest gets their own invitation link. The link is the whole of how we know them — guests never make an account and never set a password, which is deliberate: security here should feel like hospitality, not a door with a lock on it.
What the link contains is random and unguessable, and it is never stored in a readable form. We keep a one-way fingerprint of it, which is what an invitation is recognised by, and an encrypted copy, which is what lets your host copy the link again to send it to you themselves. The key to that copy is not in the database, so a stolen copy of our data is worth nothing on its own.
We should be plain about what that second form means: because your host asked to be able to re-send a link by hand, Coterie retains the ability to read an invitation it has already sent. The alternative was a link that could never be copied twice. We chose the one that keeps hosts able to invite people the way they actually do.
A host can end any invitation at any moment, and it stops working on the very next request. They can also set one to expire. An ended link says only that it is no longer available — never that it was withdrawn, and never who withdrew it.
What we record when an invitation is opened
Each time an invitation is opened we record the time and a short description of the device, such as “Safari on iPhone”. We do not keep the full technical signature a browser sends, and we do not keep an IP address with it.
The host of the gathering can see when their own invitations were opened. If one invitation is opened on noticeably more devices than one guest would use, we tell the host that the link may have been passed around. That is all this record is used for: it is never used to advertise, and it is not shared with anyone but the host.
Verified guests, sealed invitations, and surprises
A host can ask that guests be verified. Before a verified invitation shows anything, we email a six-digit code to the address the host invited and ask the guest to type it back. The code is stored only as a one-way fingerprint and expires after ten minutes. We keep a count of wrong attempts so that an invitation under attack stops answering for an hour.
A host can seal an invitation. Until the host approves a guest, that guest sees only who is hosting, what the gathering is called and when. Pressing “I’d like to come” on a sealed invitation sends the host a request; it is not yet a yes.
A host can mark a gathering as a surprise and name a guest of honour. That one person’s invitation shows a cover story the host has written, with its own time and place, in place of the real gathering, and updates about the real gathering are not sent to them. This is the one case in which Coterie deliberately shows a guest something other than the truth, it is done at the host’s direction, and it ends when the host reveals the surprise: from then on the guest of honour’s invitation shows the real gathering. If no cover story has been written, their invitation does not open at all.
Photographs
A host on a paid plan can open an album for a gathering. Photographs are pictures of people, often in someone’s home, so they are handled more strictly than anything else an invitation reaches.
- Who can see or add them: only guests who said yes to that gathering, and its hosts. Holding an invitation link is not enough.
- Where they are kept: in private storage. No photograph has a public address; each viewing uses a link that expires after an hour.
- Taking one down: a guest can hide any photograph they are in, themselves and at once, from everyone. The host can see that it happened and cannot undo it.
- Downloading: anyone who can see the album can download it.
- How long they stay: the host chooses a date, shown from the first photograph. On that date the photographs are deleted from our storage, not hidden or archived. The people who came are emailed twice beforehand so they can save what they want.
We do not run face recognition on photographs, we do not give them to the Social Secretary or any other model, and we use them for nothing but showing them to the people entitled to see them.
The host’s recorded voice
A host can record a message of up to ninety seconds for a gathering’s invitation. The recording is kept in private storage and played to that gathering’s guests through links that expire after an hour. It follows the invitation’s own rules: a sealed guest does not hear it until approved, and a guest of honour never hears it. The host can replace or remove it at any time.
Asking to get together
A member can ask someone in their directory to get together, before there is any gathering or date. The person asked receives a private link from the member; Coterie does not write to them. On that page they can say which of the offered times suit them, suggest another, or decline, and their answer is shown to the member who asked and to nobody else. When several people are asked at once, none of them is told who else was asked.
The page also offers “please don’t ask me this way again”. If someone chooses it, the member is told and can no longer send that person an ask. We keep that choice for as long as the member keeps that person in their directory, and the member has no way to switch it off.
Seats taken from an open link, and plus-ones
A host can share a single open link for a casual gathering. Someone who takes a seat from it gives a name, and receives an invitation of their own; the open link itself shows nobody the address. A guest whose host allows it can also add a named plus-one by giving that person’s name and, where they give one, an email address, so the plus-one can have their own invitation. In both cases the name is kept on that gathering’s guest list and is not added to the host’s directory.
Connected agents
You can connect an outside assistant — one that speaks the Model Context Protocol — to your account by issuing it a key from your account page. Nothing is connected unless you connect it; there is no default, and no assistant reaches Coterie without a key you made.
A key acts as you. An assistant holding one can read and write your own Coterie data: your people and what you've written about them, your log of time spent, your plans and their guest lists, and your open threads. It cannot reach another member's account, a co-host's private notes, guests' conversations with the Social Secretary, budgets, or vendor terms. Coterie sends nothing to an assistant you have not connected.
What that assistant does with what it reads is governed by whoever makes it, not by us — including whether they retain it or train on it. We can't control a system you've handed a key to, and we won't pretend otherwise. That is the trade, and it's why the key is yours to issue and yours to end. Coterie itself still never sells your data, never advertises from it, and never uses it to train models.
We store only a fingerprint of each key, never the key itself, and show you the key once when it's made. Your account page lists every key you hold and when each was last used, and ending one stops it working immediately. Closing your account ends all of them.
Messages to your people
Coterie sends messages to your guests only as you direct: the invitations you send, a single day-before confirmation if you switch it on, the updates you write to them, the notes you approve, and the working sheet you send a vendor. Two kinds of message follow from a choice you made rather than a button you pressed each time: a verification code when you have asked that guests be verified, and the emails an album sends to the people who came (an invitation to add their photographs, and two reminders before the album is deleted). There are no marketing messages to guests, ever, from us or through us.
Most invitations are not sent by Coterie at all. You are given each guest’s link to send yourself, in your own text or chat, and the same is true when you ask someone to get together. What Coterie does send goes by email. Coterie does not send text messages, to guests or to hosts. If that ever changes, this policy will say so first, and no guest will be texted without giving their own number and their permission on their own invitation.
Public event pages and visitors
Some gatherings have a public event page. Visitors to a public page see only what the host published as public, and can converse with the Social Secretary about only that. If a visitor requests an invitation, we collect the name and contact details they provide and share them with the host for approval; declined requests are not retained.
What we will never do
- Never sell personal information. Never advertising — no ads in the product, no ad targeting from your relationships.
- Never message your guests or contacts except as you direct.
- Never use your directory, notes, or conversations to train AI models — ours or anyone's.
- Never show one host's private notes to anyone else, including co-hosts.
- Never use notifications for marketing.
Email from us
We use your account email for product features like summaries you enable, product-update newsletters, and transactional notices (receipts, support). Unsubscribe from newsletters and non-essential notifications anytime.
Analytics
Our apps collect usage metrics — like the percentage of users who use a feature, or sign-in events — solely to improve the product and catch errors and performance problems. This telemetry is high-level product usage and never includes sensitive data like notes, contact information, or conversation content.
Keeping automated sign-ups out
Our public forms — signing up, the contact form, and subscribing to our letters — are protected against automated abuse. Where a bot check is shown, it is run by a third-party service (hCaptcha or Cloudflare Turnstile), which receives the information a browser normally sends in order to decide whether a visitor is a person; that service’s own privacy policy governs what it does with it.
We also count how often a form is used from one network address and for one email address. What we store for that is a one-way fingerprint rather than the address itself; sign-up counts are deleted after a day.
Subscriptions
Payment and card information is handled by Stripe. Payment information is never stored on our servers, is used only for your subscription, and is never shared with any third party.
Information usage and disclosure
We use the information we collect to operate and improve Coterie and to support you. We do not share personal information with outside parties except to the extent necessary to provide Coterie's functionality (for example, the LLM processing described above, and payment processing).
The companies that process information for us, each only to provide its part of the service: Supabase (our database and file storage), Vercel (hosting), Anthropic (the large language model behind the Social Secretary and drafted suggestions), Resend (sending email), Stripe (payments), and the bot-check service named above. Vercel also provides the high-level usage figures described under Analytics.
We may disclose information in response to subpoenas, court orders, or other legal requirements; to exercise our legal rights or defend against claims; to investigate or prevent illegal activity, suspected fraud, abuse, or policy violations; or to protect rights, property, or safety.
If we sell to, buy, merge with, or partner with other businesses, user information may be among the transferred assets; this policy's commitments travel with the data.
Security
We implement a variety of measures to keep your information secure. Passwords, where used, are hashed — never stored — using industry-standard methods (currently PBKDF2 with SHA-256, per NIST guidance). All communication with the app and website requires HTTPS. Notes, conversations, and sensitive directory fields are encrypted in storage and in transit. If you enable notifications, we store a delivery token; we never use notifications for marketing. We use cookies on the site and tokens in the app to keep you signed in; server software may hold basic technical data such as IP addresses in temporary logs.
Security vulnerability disclosure
If you believe you've found a security or privacy vulnerability affecting Coterie, please report it through the contact form. Include the product and version affected, what you observed versus expected, and numbered reproduction steps (a short video helps). We'll acknowledge receipt and follow up if we need more. For our members' protection, we don't disclose, discuss, or confirm security issues until investigation is complete and any necessary updates are generally available.
Accessing, changing, or deleting information
- Hosts: access or change your information, or delete your account, in the app. Deleting your account deletes your directory, records, plans, and conversations. Deleting a person from your directory deletes that record and its history.
- Guests: request access to or deletion of your conversation history through the contact form.
- Deleted information may persist in encrypted backups for up to 90 days, accessed only for disaster recovery.
- Coterie may delete information when required for technical, legal, or abuse-prevention reasons, or for extended inactivity, with notice where practicable.
Regional rights and compliance
- California: we comply with applicable California privacy law, including consumer rights to access and delete personal information; we do not sell or share personal information as those terms are defined under California law, and we do not distribute personal information to outside parties without consent.
- European Union / UK: where European data-protection law applies, we process personal information under appropriate legal bases and transfer it internationally only under recognized safeguards; residents may exercise access, correction, deletion, and objection rights via the contact below.
- International transfers: information may be processed and stored outside your country; protections in this policy apply wherever the data is processed.
- Children: Coterie accounts are for people 18 and older. Guests at a host's gathering may include minors (a family dinner, a birthday); information a host keeps about their own family members is the host's directory data under this policy, and guest surfaces are not directed at children.
Third-party links and content
Coterie may display or link to third-party content and services (for example, a host's outside links on an event page). These have independent privacy policies, and we're not responsible for their content or practices.
Changes to this policy
We may update this policy as the product and the law evolve. We'll post changes here and, for material changes, notify you in the app or by email before they take effect. Continued use after notice means the updated policy applies.
Contact
Privacy questions and requests: use the contact form · Smart CRM, LLC d/b/a Coterie.