Privacy policy.

What this policy covers

This policy applies to the steer website at trysteer.ai, the request-access form, the public meeting demo on the homepage, and the steer desktop app and services during the private beta (together, “steer”, “we”, or “us”).

Connected services such as Google, Slack, Atlassian, or GitHub have their own privacy policies. Those policies govern how they handle information in their products.

When you visit the website

We use PostHog, hosted in the United States, to understand how the site is used: page views and exits, which sections are viewed, scroll depth, clicks to feature pages, download clicks, request-access steps, and meeting-demo steps. When a beta signup completes or someone clicks to download steer or its Chrome extension, we report the conversion to X Ads so we can measure our advertising. If you allow analytics, we also use the Reddit Pixel to measure our Reddit advertising: Reddit receives page visits on the site and, when a beta signup completes or a download is clicked, that action as a conversion. Because automatic matching is turned on in our Reddit account, Reddit also receives a hashed (irreversibly scrambled) version of any email address or phone number you type on the site, including on the beta signup form, and uses it to match ad activity to people. We do not send Reddit any other form answers.

We use PostHog session replay, which records how a visit looks and moves, such as the pages you view, where you click, and how you scroll, with everything you type into a form hidden and the request-access forms left out entirely. We do not use heatmaps or automatic click capture. Apart from the hashed email address or phone number described above, form answers, names, audio, and transcripts are excluded from analytics. PostHog, X, and Reddit may receive standard request details such as your IP address, browser, and device type, and Reddit may store an identifier in your browser to recognise repeat visits.

You can turn analytics off at any time with Privacy preferences in the site footer. Your choice is stored in your browser for 180 days. We also store your theme preference in your browser.

When you request access

The request-access form collects your email address and, if you provide them, the kind of work you do, the plan you expect to use, and whether you are willing to join the pilot and share feedback. We also record which page you signed up from and any campaign parameters in the link you used.

We use this to manage the beta waitlist, contact you about access, and understand which pages and campaigns bring people to steer. It is stored in our database provider, Supabase.

When you try the meeting demo

The homepage demo asks for your microphone, the names you enter, and short voice samples, then transcribes a live conversation for up to 60 seconds. Audio is streamed to our transcription service and its speech-recognition provider to produce the transcript and match speakers.

Demo speaker profiles, including the voice samples and the voiceprints made from them, are temporary and isolated to that session. They are deleted when the session ends or expires, and a demo is never saved as a meeting. We use your IP address to limit how many demo sessions can start from one network.

When you use steer

During the private beta, steer processes the information needed to do the work you ask for:

• Account information, such as your name, email address, and sign-in details.
• Content you provide, including messages, instructions, voice notes, files, notes, to-dos, projects, and scheduled tasks.
• Meetings you choose to capture, including audio, transcripts, speaker labels, summaries, decisions, and action items.
• Voice profiles you create to recognize speakers, as described in Voice profiles and biometric information.
• Connected-account data from services you connect, limited to the scopes you grant, such as email, calendar events, documents, messages, and issues.
• Memory that steer builds from your work, such as people, projects, preferences, and decisions, so context carries between tasks.
• Local access to files, folders, the terminal, and your browser session, as permitted by macOS and your settings.
• Technical information, such as logs, errors, device and app version, and usage needed to operate and secure the service.

Integration credentials are encrypted at rest. The security overview explains how account access, connections, device permissions, and approvals are separated.

Google user data

You can connect a Google account to steer. You choose which Google services to connect, and Google asks you to approve each permission before steer can use it. steer accesses only the services you connect, and uses them only for the work described below.

• Basic profile. Your Google account email address, so steer can tell your connected accounts apart.
• Gmail. Search and read your messages, threads, and attachments when you ask, for example to answer a question or turn a thread into to-dos. If you turn it on, steer also checks your inbox on a schedule for replies and commitments that need attention. When you ask, steer writes drafts for you to review, sends email, adds or removes labels, marks messages read, archives, moves messages to Trash, and cleans up or unsubscribes from senders you pick from a list it shows you. steer asks for your approval before sending any email and never permanently deletes email.
• Google Calendar. Read events on all your calendars, including shared ones, to show your meetings, link meeting notes and to-dos to the right event, and check your availability. When you ask, steer creates, updates, or deletes events after you approve a preview.
• Google Drive. Search your Drive and read or export the files you ask about, including Google Meet recordings and transcripts saved there. When you ask, steer also saves files it made for you into a folder you pick, and renames or moves files. Depending on the permissions you grant, steer can also read the activity history of your shared files, such as who changed what, to include in your briefs, and read and update the Apps Script project attached to a file when you ask. steer never changes your files’ activity history.
• Google Docs, Sheets, and Slides. Read the documents, spreadsheets, and presentations you name, and create or edit them when you ask: inserting text in a document, writing or appending rows in a spreadsheet, or replacing text in a presentation, for example turning meeting notes into a document or action items into a spreadsheet.

steer’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. In particular:

• We use Google user data only to provide and improve the user-facing features described above that you use.
• We transfer Google user data only as needed to provide those features (for example, to our hosting and AI model providers to complete a task you asked for), for security, to comply with law, or as part of a merger, acquisition, or sale of assets with your explicit prior consent.
• We do not use Google user data to serve advertising, and we never send it to our analytics or advertising providers.
• We do not sell Google user data, and we do not use it to determine creditworthiness or for lending.
• We do not use Google user data to train or improve generalized AI or machine-learning models, and our AI model providers may not use it for that purpose.
• People at steer do not read your Google user data unless you ask us to, for example for support; it is needed for security, such as investigating abuse; it is required by law; or it has been aggregated and anonymized for internal operations.

Google user data is encrypted in transit and access tokens are encrypted at rest. Content steer brings in from Google, such as a meeting summary, a to-do, or a note made from an email, is stored with your other steer records and follows How long we keep it. You can disconnect a Google account in steer at any time, or remove steer’s access at myaccount.google.com/permissions. Either stops future access. To have records made from your Google data deleted, delete them in steer or email privacy@trysteer.ai.

How we use information

• To provide steer: run tasks, capture and summarize meetings, keep memory, and act in the tools you connect.
• To operate, secure, debug, and improve the service, and to prevent abuse.
• To communicate with you about access, the beta, support, and changes to steer.
• To measure website traffic and advertising, as described above.
• To comply with law and enforce our terms.

We do not sell your personal information.

Who processes it with us

We rely on service providers that process information on our behalf and under our instructions:

• Hosting and infrastructure: Amazon Web Services, Cloudflare, and Supabase.
• AI model providers, which process the content a task sends them to return a result.
• Speech recognition for transcribing meetings, voice notes, and the demo.
• Analytics and advertising measurement: PostHog, X Ads, and Reddit Ads, for the website only.

When you ask steer to act in a connected service, such as sending an email or updating an issue, the relevant information goes to that service as part of the action. We may also disclose information when required by law, to protect people or the service, or as part of a merger, acquisition, or sale of assets.

Information about other people

Meetings, email, and messages naturally include other people. If you capture a meeting or connect a shared workspace, you are responsible for giving any notice and obtaining any consent the law or your organization requires. Voice profiles of other people have additional rules, described next.

Voice profiles and biometric information

steer can recognize who is speaking in a meeting. To do that it keeps voice profiles: a short audio sample of a person’s voice and a voiceprint, a numerical representation of that voice made from the sample. Some laws, including those of Illinois, Texas, and Washington, treat voiceprints as biometric identifiers. This section explains how we collect, use, keep, and destroy them.

• Creating a profile. When you record or upload a voice sample in Settings › Speaker profiles, or name a speaker during a meeting, steer saves the audio sample and a voiceprint under the name you choose.
• Recognizing speakers. During a meeting you capture, steer makes voiceprints from the meeting audio and compares them with your profiles to label who said what. These comparisons happen while the meeting runs and are not saved. Up to 20 seconds of each voice steer does not recognize is held so you can name it, and discarded when the meeting ends if you don’t.
• Model updates. When we update voice matching, we may make new voiceprints from your saved samples so your profiles keep working. Earlier voiceprints are kept, so we can roll back, until the profile is deleted.

We use voice profiles only to label speakers in your own meetings and transcripts. Each account’s profiles are stored separately and are never compared with another account’s meetings. We do not use them for advertising, to train AI models, or to identify people for anyone else.

Voice profiles are stored and matched by our own transcription service, hosted on Amazon Web Services. Meeting audio goes to our speech-recognition provider for transcription, and transcripts with speaker names are processed like other meeting content, but voiceprints are never sent to our speech-recognition or AI model providers. We do not sell, lease, trade, or otherwise profit from voice profiles, and we do not disclose them to anyone else unless the person they belong to consents or the law or valid legal process requires it.

Only create a voice profile for another person, including by naming their voice during a meeting, after you have told them and they have agreed, in writing where the law requires it, as it does in Illinois.

A voice profile is kept until it is deleted. Deleting a profile in Settings › Speaker profiles permanently deletes its audio samples and every voiceprint made from them. When you close your account, we delete all of your voice profiles. In any case, we permanently destroy a voice profile no later than three years after it was created or last matched a voice, whichever is later. Anyone whose voice is in a profile can ask us to delete it at privacy@trysteer.ai.

How long we keep it

Request-access details are kept while the beta waitlist is active or until you ask us to delete them. Meeting-demo sessions are deleted when they end or expire. App data is kept while your account is active so steer can keep its context, and deleted or de-identified within a reasonable period after you delete it or close your account, unless we need to keep it for legal, security, or backup reasons.

Disconnecting an integration stops future access through that connection. Notes, meetings, and other records already created from it stay until you delete them.

Voice profiles follow their own schedule, described in Voice profiles and biometric information.

Your choices and rights

You can turn off website analytics, disconnect integrations, withdraw macOS permissions, and delete records and voice profiles inside steer. Depending on where you live, including California and the European Economic Area, you may also have the right to access, correct, delete, or export your personal information, and to object to or restrict certain processing.

To make a request, email privacy@trysteer.ai. We may need to verify your identity, and we will not discriminate against you for exercising your rights.

Security

We use technical and organizational measures to protect information, including encrypted connections, encrypted integration credentials, and separated access paths. No system is perfectly secure. See the security overview for details.

International processing

steer is operated from the United States, and our providers may process information in the United States and other countries. Where required, we rely on appropriate safeguards for those transfers.

Children

steer is not directed to children under 16, and we do not knowingly collect their personal information. If you believe a child has provided us information, contact us and we will delete it.

Changes to this policy

We will update this page as steer changes and revise the date above. If a change materially affects how we use personal information, we will give reasonable notice before it applies.

Contact

Questions or requests about privacy: privacy@trysteer.ai.