Privacy Policy

Effective October 29, 2026. Questions: [email protected]. What changed

Resonate ("Resonate", "we", "us") is operated by David Aragon, an individual, at resonatecircle.com (our website, and the app at resonatecircle.com/app, which works in a browser on a phone or a computer). Resonate is a personal-network app: it helps you keep track of the people you know, suggests who to reach out to each morning, turns the conversations you log into notes, and lets student clubs find times their members are free. This policy explains what we collect, why, where it goes, how long we keep it, and the choices you have. Resonate is in beta and is run by one person, so some things are done by hand; we say so where that matters.

The short version

What we collect

We do not collect your precise location, and the app does not request camera or location permission. It asks for microphone access only when you tap the microphone to dictate.

Google user data

Connecting Google Calendar is optional and is a separate step from signing in to Resonate. (You sign in to Resonate with an email and password, or with Sign in with Apple or Sign in with Google. Signing in with Google is a separate step: it shares only your name and email address with us, and it does not give Resonate any access to your Google Calendar. Calendar access is only ever granted by the Connect step described here.) If you connect it, Resonate asks for one permission: view your availability in your calendars (https://www.googleapis.com/auth/calendar.freebusy). We use that permission to ask Google which times on your primary calendar are busy over the next 14 days. We do not access event titles, descriptions, attendees, locations, or any other event details, and we do not read any calendar other than your primary one.

What we keepOnly the start and end time of each busy block (merged where blocks touch) for the next 14 days, and a refresh token that lets us update those blocks without asking you to sign in to Google again. The refresh token is encrypted before it is stored. Older blocks are replaced each time your availability is refreshed.
How it is usedOnly for the club scheduling feature you see in the app. Club presidents see, for a proposed time window, how many approved members are free, busy, or have not connected a calendar. The number free is shown only once at least five members of the club have connected a calendar, so a count never reveals one person's schedule. Presidents can also see whether each board member (the officers of that club) is free or busy at a given time, by name, and which members have connected a calendar. Other members see counts only. We never show anyone your event details. If you take part in a joint plan between two clubs, the people running that plan see the shared availability grid for it.
When it updatesWhen you connect, when a club grid you belong to is opened and your data is more than about 15 minutes old, and in a nightly refresh.
Storage and securityStored in our database with row-level security. The app itself has no direct read access to busy blocks or tokens; they are read only through restricted server-side functions. Data is encrypted in transit, and the token is additionally encrypted at rest with AES-256-GCM.
SharingWe do not sell Google user data, use it for advertising, or transfer it to anyone except our hosting and database providers as needed to run Resonate, to comply with the law, or with your explicit agreement. We do not send Google Calendar data to our AI provider.
AIWe do not use Google user data to develop, improve or train generalized AI or machine-learning models.
Human accessWe do not read your Google user data unless you ask us to in order to help you, it is necessary for security or abuse investigation, or the law requires it.
DisconnectingChoose Disconnect in the app's club settings. We revoke our access token at Google, delete your stored busy blocks, and delete the token. You can also revoke access at myaccount.google.com/permissions. Deleting your account also removes this data.

Resonate's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

How we use data

We do not sell personal data, share it for cross-context behavioral advertising, or use it to build advertising profiles. Resonate does not send you text messages. If you turn notifications on (You, Morning note), your morning note arrives as a notification on that device, and at most one more a day: an evening reminder on days you have not logged a talk, on Sundays a recap of how many people you kept up with that week (you can turn it off), a note that someone joined from your card, or an introduction notification. Never more than two a day, and never between 10 PM and 7 AM. The morning note names up to three people by first name with a short fixed reason, because anyone who sees your screen can read them; the evening reminder and the Sunday recap name nobody. Introductions have three notifications: to the friend in the middle when someone asks them for an introduction ("Sam asked you for an intro"), to the other person once that friend says yes ("Priya wants to introduce you"), and to the person who asked once both said yes ("You and Hana are introduced"). Each names one person by first name and never shows a note, a line or an interest, and none is sent if you chose "Just in the app". The morning note can also set the number on the app's icon to how many people are on Today; opening the app clears it. To deliver them we keep, for each device you turn them on for, the address and keys its push service gives us, and a record of which notes were sent; the message is encrypted so the push service cannot read it. You can turn them off on a device at any time (signing out does too), and choosing "Just in the app" sends nothing. Without notifications your morning note is computed and shown in the app. We only email you about your account: confirming your address, resetting your password, and when you ask to delete it (when the deletion is scheduled, and when it is done).

Who we share data with

We use a small number of service providers who process data on our behalf:

AI processing (Anthropic) and voice input

What is sent. When you use Log a talk or ask Resonate to write a note or a suggested message, the app sends our server a request, and our server sends it to Anthropic's API. That request can include: the text or transcript you submitted; the names (and nicknames) of the people in your list whose names, or close sound-alikes, appear in what you said (not your whole list), so the AI can match who you are talking about; and, for the people it identifies, their summary, interests, recent notes and how they are connected to you. When you ask for a professional email draft, the request carries only the talking points you may use in an email (what you logged from your talks, what they are up to, how you know them, and an introducer's name or your trip only once you have said it is OK), the person's first name, your name and school, the kind of email, and, for a follow-up, the earlier subject; never your private summary, Resonate's reason for suggesting them, how close you are or who else you both know. Drafts can also carry your writing voice (see below). Requests do not include your Google Calendar data, your email address, your password, or your contacts' phone numbers or email addresses.

What Anthropic does with it. Under Anthropic's commercial terms, inputs and outputs from its API are not used to train its models by default. Anthropic deletes them automatically from its systems within 30 days, except where a longer period is required by law or is needed to enforce its usage policies (for example, to investigate a violation). We do not store your raw transcript with Anthropic, and Anthropic's retention is governed by its own policies, which may change.

Your control. Log a talk is optional, and the app asks your permission the first time anything would be sent to Anthropic. Until you agree, nothing is sent and the app uses simple on-device text matching instead. You can turn Claude off or on again at any time under You, Your account. Your choice is saved on your account. You review everything the AI proposes before it is saved. If the AI service is unavailable, the app falls back to the same text matching.

Voice dictation. When you tap the microphone, the app records the audio on your device. The first time a recording would leave your device, the app asks your permission. If you agree, the clip is sent through our server to AssemblyAI. For a longer talk, the app starts sending it to our server in pieces while you are still talking, so the text is ready sooner after you stop; our server only converts each piece into the format AssemblyAI needs and sends it straight back to the app, keeps nothing, and sends nothing to AssemblyAI before you stop. Then the whole clip goes to AssemblyAI, a speech-to-text provider, together with the names of people in your list so they are spelled correctly. AssemblyAI returns text, and the text is then processed by Anthropic as described above. We do not store your audio. Our server asks AssemblyAI to delete the transcript as soon as we have read it; AssemblyAI's published policy is that uploaded audio is deleted starting at 24 hours (at most 48 hours) and transcript records within 30 days. AssemblyAI's own terms govern what it does with data it receives. Those terms allow it to use customer data, and de-identified data made from it, to improve and train its speech models unless the customer opts out. If you decline, or turn this off under You, Your account, or the service is unavailable, the app uses your browser's built-in speech recognition instead. In most browsers that sends your audio to the browser maker's speech service (for example Google for Chrome, Apple for Safari) under that company's privacy policy. Either way, Resonate itself does not keep a copy of your audio; we receive only the text.

Your writing voice. So suggested messages sound like you, Resonate learns how you write from the messages you send from the app (the text you hand off to Messages or Mail) and any you paste on the Your voice page. It keeps a few measurements of your style (such as length, punctuation, emoji and contractions), up to ten of your own messages for each kind of message, the words you tend to swap, cut or add when you change a suggested message (noted only once two of your edits agree), and your last three edits as before-and-after pairs, all with phone numbers, email addresses, links and names removed, on your account. Resonate applies what it learned to the drafts it shows you; under You, Your voice, each learned rule has a "Not me" button. When Claude writes a draft for you, those measurements and examples are sent to Anthropic with the request, as described above. To check how well drafts fit, Resonate also records what it suggested, what you sent, and which rewrite buttons you used; the text of those records is deleted after 30 days, and only the measurements are kept. This is on unless you turn it off: under You, Your voice, you can switch "Learn my voice" off (Resonate then stops learning and stops keeping drafts), turn emoji off, and reset what it learned. Deleting your account deletes all of it.

Cookies and browser storage

The website (resonatecircle.com, Privacy and Terms) sets no cookies and runs no tracking or analytics scripts. The app (resonatecircle.com/app) uses your browser's local storage, not advertising cookies, and only for things it needs to work:

Sign-in sessionKeeps you signed in (stored by our authentication provider's code under a name starting sb-). Removed when you sign out.
A copy of your accountYour people, notes and settings as the app last loaded them, kept in this browser's storage (IndexedDB) so the app opens at once and works without a connection. Replaced each time the app loads them again; deleted when you sign out, delete your account or ask for it to be deleted, or another account signs in on this device. An account waiting to be deleted is never opened from it.
Unsaved changesIf you edit something, remove someone or note news while offline, a copy waits on this device until it reaches our servers, then is removed (at most 14 days). Signing out asks first if anything is still waiting, then deletes it. Deleting your account (now or in 30 days) also deletes it, after telling you if anything was still waiting; it does not come back if you keep the account. Also cleared when another account signs in on this device.
A talk in progressA talk you have logged but not yet saved or discarded, so closing the app does not lose it (at most two days). Cleared when you sign out or delete your account, or ask for it to be deleted.
App filesThe app's own code, styles and fonts, kept so it opens quickly. Nothing about you or your people is kept there. The same part of the app (a service worker) shows your notifications, if you turn them on.
Invite linksRemembers the invite, room or notification link you opened while you sign in, so it still works afterwards (about a day; a personal invite link, up to a week, and it is also kept on your new account until the app has used it).
Small preferencesDisplay choices and things you already answered or dismissed on this device (for example room notices you have handled), so they are not shown again. Cleared when you sign out, except the app's light or dark theme.
Home Screen sign-in codeOn an iPhone, when Safari shows the one-time code that signs in the Resonate app you added to your Home Screen, the same code is kept in a cookie (rz_handoff, readable only by our server) for 10 minutes, so the app can sign in without typing it. It works once. Our server keeps only a scrambled form of the code and of your IP address (to stop guessing), and deletes them within a day.
Setup draftWhat you typed during first-time setup, kept only until you close the tab.
Usage countsOnly while Share usage counts is on: a random session code (replaced after 30 minutes away from the app), and counts waiting to be sent, kept on this device until they reach our servers (at most 200, at most 14 days; the sign-in page keeps a few until you are signed in, for that tab only). The part of the app that shows notifications keeps a note that one was shown or tapped (the kind and the date only) until the app next opens. Deleted when another account signs in on this device.

Because all of this is strictly necessary to provide the app you asked for, we do not show a cookie banner. Cloudflare, which protects our site, may set its own short-lived security cookie (such as __cf_bm) if it needs to tell people from bots; it is not used for tracking or advertising. You can clear all of this at any time in your browser's settings for resonatecircle.com; you will then need to sign in again. The usage counts are not needed to provide the app: they are described under How we measure whether Resonate works, and you can turn them off at any time. If we add anything else that is not strictly necessary, we will update this section first and ask for your consent where the law requires.

People you add

Resonate stores information about people you add, who may not use Resonate. You are responsible for adding only information you are comfortable keeping, and for treating it with care. That information is visible only to you unless you choose to share it. If you are one of those people and want information about you removed or corrected, email [email protected] and tell us who added you if you know; if we cannot reach the person who added you, we will delete what we can identify.

Your choices and rights

Retention and security

We keep your data while your account is active, except: nudge records, which are deleted about three months after the nudge ends (a stop you set lasts as long as you keep it); the per-hour and per-day request counters behind our rate limits, which are reset every hour and day; the usage counts, kept 90 days, then only as totals that cannot be linked to you; request records, kept 30 days; and event-room data: the record of who was in a room is deleted after the room closes and no later than 30 days afterwards, and requests in that room go with it. Your own space history line (title, place, time) stays until you remove it or delete your account; blocks are kept so they keep protecting you. Also on their own clock: the text of the drafts Resonate suggested and the messages you sent (kept to learn your writing voice) is deleted after 30 days, and only the measurements are kept; the record of which notifications were sent is deleted after 60 days; the copy of your account on a device is not used after 30 days without a fresh load; and the per-day cost estimates behind the spending limits hold no content and are deleted with your account.

If you choose Delete in 30 days, your data stays in our live systems, hidden and unused, for 30 days so you can keep your account (we also keep the email address and time zone you had when you asked, to send the confirmation), except your Google Calendar connection, voice recordings, exports and the devices we send notifications to, which are deleted when you ask; within a day after those 30 days everything is deleted. If you choose Delete now, your data is removed from our live systems immediately; if you ask by email, within 30 days. Copies in routine encrypted backups kept by our database provider may persist for a limited period before they expire; we do not restore deleted accounts from them. Hosting logs are short-lived and expire on the provider's schedule. We may keep limited records where the law requires.

How we measure whether Resonate works. When you use the app, it records simple usage counts: which screens you open, which buttons you tap (for example "opened Log a talk", "saved a talk by voice", "turned on notifications", "tapped I sent it"), how many items were involved (for example "3 facts suggested, 2 kept"), error codes you saw, and your device type (for example "iPhone, Home Screen app"). A random session code links the counts from one recording or one message draft to the cost of processing it. If you delete your account, the app may ask why, and only the answer you pick (for example "Privacy") is counted. These records never contain what you wrote or said, the names or details of the people you add, your messages, your search words, or your IP address, and never which person, room or club an action was about. They are stored with your account in our database (Supabase), are not shared with anyone else, and are not used for advertising or sold. We use them only to see how the app is used and to fix and improve it; for example, we check whether the morning note leads people to reach out, and where setup loses people. We keep the individual records for 90 days, then keep only totals that cannot be linked to you. They are deleted with your account, and "Export everything" includes them. You can turn this off at any time in You, Settings, Privacy & data, Share usage counts, and the app then stops sending them. For people in the UK and EEA, our legal basis is our legitimate interest in understanding and improving the service; in the UK we rely on the exception for statistics about how a service is used, with your right to object through that switch. If your device's time zone is in the EEA, the switch starts off and nothing is recorded unless you turn it on.

Paid processing records. To see what Resonate costs and whether it is working, we record each paid processing call (for example a transcription or a talk summary): which feature was used, whether it succeeded, how long it took, how much processing it used, what it cost, and which app version sent it, with your account id but no content. We keep these records for 90 days, then keep only daily totals that do not identify you. When you delete your account, your account id is removed from these records.

Request records. For each request the app makes to our servers we also record which service was called, whether it worked, how long it took, how much processing and data it used, and which outside provider it relied on (for example the AI or calendar provider) and whether that provider answered. No content, web address, IP address or error text is kept. When the request came from your signed-in session and was answered, the record carries your account id. We keep these records for 30 days; when you delete your account, your id is removed from them.

Data is encrypted in transit (HTTPS). Every table holding your data is protected by row-level security so your account can read only its own rows, files are kept in private storage with short-lived access links, and Google refresh tokens are encrypted at rest. No system is perfectly secure, and we cannot guarantee absolute security. If a breach affects you we will notify you as the law requires.

How an account started. When you create an account we record once how you arrived: the kind of link you opened (someone's invite or card link, an event-room or club link, a campaign link, or none), the campaign code if the link carried one, and when you first opened it. Before you sign up, your browser keeps only that (the kind of link, the code and the time) in its own storage for up to 7 days, never the username, room code or anything you type. We also count how often each kind of link is opened, per hour, without any account, IP address or device identifier; for event rooms and clubs the count is kept per room or club, for cards and invites only as a total. The sign-up record carries your account id, is included in "Export everything" and is deleted with your account; the hourly counts are kept 90 days, and daily totals after that.

Club Mirror. Club Mirror keeps a record of when you turned it on or off for each club (and when a club's president turned it on or off for the club), so we can show what you agreed to; it is deleted with your account. No club totals are kept yet; when they are, they will stay with the club while it exists, and the club's officers will be able to delete them.

Where your data is processed

Resonate is operated from the United States and your data is stored and processed in the United States. If you use Resonate from another country, you understand your data will be transferred to and processed in the United States, where privacy laws may differ from those where you live.

If the GDPR or UK GDPR applies to you, we rely on: contract to run your account and the features you use; consent for AI processing of what you log, voice transcription, Google Calendar, notifications, nudges and appearing in Discover (you can withdraw it at any time in the app, which does not affect what happened before); and legitimate interests to keep the service secure, to measure how the app is used through usage counts (in the UK, the exception for statistics about how a service is used; you can object with the Share usage counts switch), to improve suggestions as described above, to learn your writing voice (on unless you turn it off under You, Your voice), and to keep information you add about other people in your private list. You can object to processing based on legitimate interests by emailing us. You can also complain to your local data protection authority.

Children

Resonate is for people 18 and older. We do not knowingly collect data from anyone under 18. If you believe a minor has created an account, email [email protected] and we will delete it.

Changes

We will post changes on this page and update the effective date. If a change affects how we use Google user data, we will notify you in the app before it takes effect and ask for your agreement where required.

What changed on October 29, 2026 (since the October 21, 2026 version)

What changed on October 21, 2026 (since the October 20, 2026 version)

What changed on October 20, 2026 (since the October 18, 2026 version)

What changed on October 18, 2026 (since the October 12, 2026 version)

What changed on October 12, 2026

Contact

David Aragon, Resonate
[email protected]