1 Assistant hour included freeStart free
1THING

Legal

Privacy Policy

Last updated: November 15, 2026 · Version 2026-11-15

Summary

This Privacy Policy explains how we collect, use, and protect your information.

1. Information We Collect:

We may collect personal information such as name, email, and usage data.

2. How We Use Information:

To provide and maintain 1THING.

3. Data Sharing:

We never sell your or your clients’ personal information, and we don’t give it to anyone for their own marketing. We do share it with the service providers listed in section 10 — including the AI services that transcribe your calls and meetings and that power the assistant’s writing, answers and card scanning — solely so 1THING can do its job for you.

4. Security:

We take reasonable measures to protect your data. Only authorized 1THING staff can access it, and only to support you, fix problems, handle billing or keep 1THING secure.

5. Your Rights:

You may request access, correction, or deletion of your data.

6. Changes:

We may update this policy from time to time.

See the full policy below for details.

1. Who We Are

1THING (“we”, “us”, “our”) is an AI assistant with a built-in CRM for real estate agents, operated by 1Thing CRM Inc., based in Ontario, Canada. Our platform is available at 1thing.ca.

This policy covers two kinds of information. Account information about the real estate professionals who use 1THING (“Users”): we are responsible for it. Information about the people our Users work with (“Contacts”), including recordings and transcripts of their calls and meetings with a User: the User (or the User’s brokerage) decides what is collected and why and is responsible for it; we process it on the User’s behalf and only to provide 1THING to that User. This policy describes how we handle personal information under PIPEDA and other privacy laws that apply.

If you have any questions, contact us at privacy@1thing.ca.

2. Information We Collect

From Users (account holders)

  • Name, email address, phone number, brokerage name
  • Account credentials (passwords are hashed with bcrypt and never stored in plain text)
  • Billing information processed through Stripe. We never store card numbers.
  • Usage data: pages visited, features used, actions performed, timestamps
  • Device and browser information for security and troubleshooting
  • OAuth access and refresh tokens for any third-party integration you choose to connect (Google, Microsoft). Tokens are encrypted at rest.

From Contacts (leads and contacts Users add to the platform)

  • Name, email, phone, mailing address
  • Property interests, notes, communication history
  • Custom fields configured by the User

Contact data is entered by our Users. Users are responsible for ensuring they have the legal right to collect and store information about their Contacts under PIPEDA, CASL, or any applicable privacy law in their jurisdiction.

Emails sent through 1THING

When a real estate agent sends you an email through 1THING (a campaign, newsletter, follow-up or one-to-one email), it contains a small image, and its links pass through 1thing.ca. This lets us show the agent when the email was opened, how many times, and which links were clicked. We keep the time of each open and the time and address of each click, with that email. Mail apps that load images automatically can record an open you didn't make. To stop it, turn off images in your mail app; to stop the emails, use the Unsubscribe link at the bottom of any of them.

From recordings and the assistant

  • Recordings of calls made or received through 1THING, which include the voices of the people the agent speaks with
  • Recordings of meetings the agent chooses to record, in person or online, which include the voices of everyone the microphone picks up, and other sound playing on the agent’s computer at the time
  • Transcripts, summaries and suggested follow-ups made from those recordings
  • Notes the agent types during a meeting
  • Photos of business cards the agent scans
  • Questions the agent asks the in-app assistant, and the drafts it writes

Usage Data

Standard server logs (IP address, browser type, pages visited, timestamps) are collected for security and performance monitoring. We do not sell this data.

3. How We Use Your Information

  • To provide and maintain 1THING. To fix a problem with the service, our staff may look at the specific record, recording or transcript involved. To improve features we use account and usage information, not your Contacts' information, recordings or transcripts.
  • To authenticate Users and secure accounts (including two-factor authentication)
  • To process payments and manage subscriptions through Stripe
  • To sync and display your emails, calendar events, meetings, and call history inside the CRM
  • To send emails on your behalf from your connected email account, when you initiate the send
  • To create calendar events and Google Meet meeting links on your behalf, when you initiate the creation
  • To place outbound calls and handle inbound calls through your connected VoIP provider
  • To turn the audio of calls and meetings into text (Soniox for calls, or Groq if Soniox is unavailable; AssemblyAI for meetings in English and wherever several voices share one recording; Groq for meetings in other languages), to write a summary (Anthropic) and suggested follow-ups (Anthropic, with OpenAI and then Google Gemini as backups), and to store them with the call or meeting
  • To index the transcripts of your calls and meetings so the assistant can search them. The transcripts and the search questions the assistant asks are sent to Google (Gemini), and the matching transcript text is sent to Anthropic with your question
  • To answer questions you ask the in-app assistant. To answer, the assistant may read your CRM records, your connected email, your team messages and your past transcripts, and sends what it reads to Anthropic
  • To draft emails and notes, write up a call, translate call notes, and read business cards you photograph and screenshots you attach to a support request (Anthropic), and to turn your dictation into text (Soniox, or Groq if Soniox is unavailable)
  • Voicemails are stored as recordings. They are not transcribed or summarised automatically.
  • To send you transactional emails (billing receipts, password resets, service notifications) and, with your opt-in, product updates
  • To detect, investigate, and prevent fraud, abuse, and security incidents
  • To comply with legal obligations

We do not sell, rent, trade, or give away your personal information or your clients' data — ever. We do not use your data, your Contacts' data, recordings or transcripts to train AI models. The AI services we use are not permitted to train their models on what we send them; see section 10 for the conditions.

4. Google Integration — Specific Disclosures

If you connect a Google account, you choose which features to enable, and we request only the permissions those features need:

  • gmail.modify — read your Gmail inbox to display emails alongside CRM contacts and deals, and update message state (for example, marking a message read in the CRM marks it read in Gmail). Email metadata (sender, subject, date) and body content are stored in our database to power search and contact linking. We never permanently delete your mail.
  • gmail.send — send emails on your behalf using your Gmail account as the sender.
  • calendar.events — create, read, and update calendar events for meetings and showings scheduled in the CRM, and generate Google Meet links attached to those events.
  • contacts.readonly (optional) — read your Google address book to suggest recipients as you type. Off unless you enable it.
  • drive.file (optional) — attach Google Drive files to emails. This grants access only to the specific files you select in Google’s file picker; we cannot see or access anything else in your Drive.
  • userinfo.email — read the email address of the Google account you connect, so we can label it in the app.

We do not use Google data to serve advertisements. We share Google user data only as needed to provide features you use: our database provider stores it, and when you ask the in-app assistant about your email, the relevant messages are sent to Anthropic to answer you. Google user data is not used to train AI models. Our use of Google API data complies with the Google API Services User Data Policy, including the Limited Use requirements.

5. Microsoft Integration — Specific Disclosures

If you connect a Microsoft account, we request equivalent permissions for Outlook email (read and send) and Outlook Calendar (create and update events). The same data handling rules as Google apply: no advertising use, no resale, no use for training machine learning models. As with Google, our database provider stores the data, and when you ask the in-app assistant about your email, the relevant Outlook messages are sent to Anthropic to answer you.

6. Call and Meeting Recording

  • Call recordings — calls made or received through the CRM’s built-in calling feature may be recorded to create notes and summaries. Recording is a setting the agent chooses. On an incoming call the agent can switch the assistant off during the call, which stops the recording and deletes what was captured. We do not announce the recording to the other party by default. An account owner can enable an automatic announcement, which is played to the other party before the conversation begins; agents are advised to say so themselves at the start of the call. Recordings are stored with our telephony provider (Telnyx) and referenced in the CRM for playback. Every recorded call is automatically transcribed and summarised — no agent action is required. The recording audio is sent to Soniox (or Groq, if Soniox is unavailable) to produce the transcript. If a third person joins the call, the side of the recording that carries more than one voice is sent to AssemblyAI, which transcribes it and tells the voices apart, and the other side is sent to Groq. The transcript is then sent to Anthropic (Claude) to write the summary and suggest follow-ups; if Anthropic is unavailable, the follow-ups are written by OpenAI, or by Google (Gemini) if OpenAI is also unavailable. The recording audio is turned into text on servers located in the United States, so the recording audio and transcript are transferred outside Canada for this purpose. Anthropic and OpenAI may process the transcript in other countries where they operate, and Google may briefly store or cache it in other countries. We do not create voiceprints, and we do not use anyone's voice to identify them. When a recording has several voices on one channel, AssemblyAI separates the speakers within that recording only; to do so it briefly derives voice characteristics. AssemblyAI states that it does not keep these after the transcript is returned and has no way of identifying who the speakers are. 1THING does not receive or keep them. Contact privacy@1thing.ca to request deletion of a recording or a transcript.

Meeting recording

An agent can record a meeting with the 1THING desktop app or phone app, in person or online. A recording captures the agent’s microphone, and on a computer also the sound the computer is playing, which may include other people on a video call and any other sound at the time. 1THING does not announce that a meeting is being recorded; agents are advised to tell the people present.

Meeting audio is stored in our file storage (Supabase) and kept until the meeting is deleted. It is sent to AssemblyAI to produce a transcript, or to Groq for a meeting in a language other than English (AssemblyAI still separates the voices when they share one recording). The transcript, and any notes the agent typed during the meeting, are sent to Anthropic to write the meeting note and suggested follow-ups, and to OpenAI, or Google (Gemini), for the follow-ups when Anthropic is unavailable. Typed meeting notes are visible only to the agent who wrote them. Contact privacy@1thing.ca to request deletion of a meeting recording or its transcript.

7. Discontinued Calling Integrations

1THING previously offered optional integrations with Dialpad and RingCentral. Those integrations have been discontinued. 1THING does not connect to, receive webhooks from, or store any data originating from either service.

8. Data Storage and Security

  • Data is hosted in Supabase’s AWS infrastructure, primary region us-east-1. File attachments are stored in Supabase Storage, encrypted at rest.
  • Each tenant's (brokerage's) data is kept separate from other tenants' data by access controls in our application and, for our public API, by database Row-Level Security (RLS).
  • Passwords are hashed with bcrypt.
  • OAuth tokens are encrypted at rest.
  • Two-factor authentication (2FA) is available to all users via authenticator apps or email / SMS codes.
  • All data transmission uses TLS 1.2+.
  • Access by 1THING staff: only authorized 1THING staff can see account data, and only to provide support, investigate a problem, handle billing or keep the service secure. Our internal usage and cost pages do not show who your clients are, and their phone numbers are partly hidden there.

9. Data Retention

We retain your account data for the life of your account. The following retention rules apply to specific data categories:

  • Account and CRM data (contacts, deals, leads, notes, activities) — retained for the life of the account. Cancelling a subscription does not delete it. If you delete your account, it is retained for 30 days so the account can be restored, then deleted (see the end of this section).
  • OAuth tokens — deleted immediately on disconnect.
  • Synced email content (from Gmail or Outlook) — retained while the account is active; deleted within 30 days of integration disconnect.
  • Voicemail audio — stored with our telephony provider (Telnyx) for 12 months, then deleted. Voicemails are not transcribed or summarised automatically.
  • Voicemail transcripts — voicemails received before 13 August 2026 may have a transcript. It is kept with the call for the life of your account, and you can ask us to delete it by writing to privacy@1thing.ca.
  • Call recordings — 12 months, then deleted. This applies to recordings made through the built-in calling feature, which are stored with Telnyx. The reference to the recording is retained as part of the Call Activity.
  • Transcripts, summaries and suggested follow-ups of calls, and the search index made from them, are kept for the life of your account. Deleting a call's recording after 12 months does not delete them. While a call's recording is still kept, the agent can discard it, which also deletes its transcript, summary and suggested follow-ups. After that, you can ask us to delete them by writing to privacy@1thing.ca. Meeting transcripts, notes and summaries are deleted when you delete the meeting. A meeting you archive instead of deleting is kept for 30 days so it can be restored, and is then deleted with its transcript, notes and summary.
  • Meeting recordings — kept until the meeting is deleted.
  • Conversations with the in-app assistant — kept until you delete the conversation or your account is deleted.
  • Copies held by the AI services — see section 10.
  • Server logs — 30 days, for security and performance monitoring.
  • Audit logs and billing records — retained as long as required by law, typically seven years for financial records.

You may request deletion of your account and all associated data at any time by emailing privacy@1thing.ca or using the delete account option in Settings. In the app you can choose to delete in 30 days — your account stops working immediately, and signing back in before the 30 days are up restores it — or delete permanently now, which cannot be undone.

10. Third-Party Services

1THING uses the following third-party services to operate the platform. When you use these integrations, you are also subject to their respective privacy policies.

  • Supabase — database, authentication, and file storage (AWS us-east-1)
  • Vercel — application hosting, serverless function execution, and content delivery (global edge)
  • Stripe — payment processing. We never store card numbers.
  • Resend — transactional email delivery (billing receipts, password resets, notifications)
  • Telnyx — telephone calling and SMS through the built-in dialer, including call recording and recording storage, and delivery of two-factor authentication codes by text, when enabled; and SMS delivery: the texts that send you the app download link and alerts about your Assistant time and, when those features are enabled, texts sent to contacts from 1THING and automated sequence and workflow messages
  • Soniox — speech-to-text for call recordings, and for dictation as you speak (United States). Receives the call audio and the dictation audio. Each call recording is deleted from Soniox as soon as its transcript is returned. Soniox does not store dictation: it processes it as it arrives.
  • Groq — speech-to-text for meetings held in a language other than English, for English meetings when AssemblyAI is unavailable, for dictation (when you speak instead of typing), and for calls when Soniox is unavailable (United States). Receives the audio.
  • AssemblyAI — speech-to-text for meeting recordings in English, and speaker separation for meeting recordings in any language when the recording alone cannot tell the speakers apart: an in-person meeting captured on a single microphone, or several people on the other side of a video call sharing one audio channel; and on calls where a third person joins, the side of the call that carries more than one voice (United States). Receives that meeting or call audio. It does not generate summaries or suggested follow-ups.
  • Anthropic — writes call and meeting summaries, answers questions you ask the in-app assistant, drafts emails and notes, writes up calls, translates call notes, reads business cards, reads screenshots you attach to a support request so our support team can see what went wrong, checks the sender name you set for outgoing email, and suggests follow-ups from transcripts. Anthropic may process this data in other countries where it operates. Receives transcripts (not the audio), notes typed during meetings, your questions, and what the assistant reads to answer them, which can include your CRM records, emails from your connected account, your team messages and the summaries and transcripts of past calls and meetings. Also receives the content of emails and notes you draft with AI assistance, call notes you translate, business-card images you scan to create a contact, screenshots you attach to a support request, and the sender name you type for outgoing email.
  • OpenAI — suggests follow-ups from transcripts when Anthropic is unavailable (United States; processing may run in other countries). Receives transcripts and notes typed during meetings, not the audio.
  • Google LLC — Gmail and Google Calendar integration, with your explicit OAuth consent. Google's Gemini models also suggest follow-ups from transcripts when Anthropic and OpenAI are both unavailable, and index the transcripts of calls and meetings so the assistant can search them. Gemini receives transcripts and the search questions the assistant asks, not the audio. Google may briefly store or cache this data in other countries.
  • Microsoft Corporation — Outlook and Microsoft Calendar integration, with your explicit OAuth consent
  • Supabase Realtime — real-time notifications to your browser (call banners, message delivery)
  • Expo — delivers notifications to the 1THING phone app, including who called

We share only the minimum data necessary for each integration to function. OAuth tokens are stored encrypted and can be revoked from your account settings at any time.

Each service provider listed above operates under its own published terms and privacy policy, and we send each one only the data it needs for the job it does here. We have not independently reviewed every other provider's contract against this policy, so nothing here should be read as a promise that each of them matches it clause for clause.

For the six AI services above (Soniox, Groq, AssemblyAI, Anthropic, OpenAI and Google's Gemini models), we have read each one's terms and confirmed the same thing of all six: none of them is permitted to use what we send them to train its own AI models. For two of the six, that is true because of a choice we make and keep in place, rather than because of their standard terms: we use Google's paid Gemini service, because the free one would let Google use what we send it to improve its products; and AssemblyAI's standard terms would permit training, so we have opted our account out of it. That setting stops AssemblyAI training its own AI models on what we send. Under its terms, AssemblyAI may still use what we send to develop and test its products, and may use de-identified data made from it for other purposes, including improving and marketing its services.

How long the AI services keep what we send them, as set on our accounts:

  • Soniox: we delete each call recording and its transcript from Soniox as soon as the transcript comes back. Soniox does not store dictation.
  • Groq keeps nothing once the request is answered (we have turned on its Zero Data Retention setting).
  • AssemblyAI begins deleting the audio and the transcript after one day (a setting on our account).
  • Anthropic deletes what we send within 30 days. If its automated safety systems flag a request, Anthropic may keep that request and its response for up to 2 years, and its safety scores for up to 7 years, and it may keep data longer where the law requires. Anthropic may look at what it keeps for safety and security purposes.
  • OpenAI keeps what we send, and what it returns, for up to 30 days to detect abuse, and may keep it longer where the law requires.
  • Google keeps prompts and responses for a limited period to detect and prevent misuse of its service, and does not use them to improve its products while we use its paid service.

These are settings on our accounts and terms of each provider, and they may change.

If your account uses its own Anthropic key, those requests go to Anthropic under your own agreement with Anthropic, and its settings, not ours, decide how long Anthropic keeps them.

Several of the services above, including our database provider, store or process personal information in the United States. While it is there, it may be accessed by the courts, law enforcement and national security authorities of the United States, and of any other country where a provider processes or stores it.

Text messages

If you give us your mobile number, we may text you about your account: the link to download the 1THING app and alerts about your Assistant time, about 1–3 messages a month. Message and data rates may apply. Reply STOP to stop these texts, or HELP for help. We do not sell or share your mobile number or your consent to receive texts with third parties or affiliates for their marketing purposes. Text messaging opt-in data is shared only with the provider that delivers the messages (Telnyx).

11. Your Rights

You have the right to:

  • Access the personal data we hold about you
  • Correct inaccurate data
  • Request deletion of your account and data
  • Export your data (contacts, deals, leads, activities) in a portable format
  • Object to specific processing activities
  • Revoke OAuth access to any integration at any time, either through the provider's account settings or from within 1THING Settings
  • Withdraw your AI consent at any time in Settings → Assistant; your calls are then no longer recorded, recordings of your calls and meetings are no longer transcribed or summarised, and the assistant stops answering your questions

If you are a User, email privacy@1thing.ca to exercise any of these rights. We respond within 30 days. If you are a Contact (for example, a client or lead of a real estate professional who uses 1THING), please send your request to that professional or their brokerage: they decide what is held about you and can answer it. If you write to us instead, we will verify your identity, pass your request to the professional who holds your information, and help them respond. If we cannot reach them, we will deal with your request ourselves.

12. Cookies

We use session cookies for authentication. We do not use advertising or tracking cookies. No third-party analytics cookies are set without your consent.

13. Children's Privacy

1THING is not directed at children under 16. We do not knowingly collect personal information from children. If you believe a child has provided us with personal data, please contact us and we will delete it promptly.

14. Changes to This Policy

We may update this policy from time to time. When we do, we post the updated version on this page with its date. Where a change is material, we ask you to agree to the new version before you can continue using 1THING.

15. Contact

1Thing CRM Inc.
Ontario, Canada
Privacy requests: privacy@1thing.ca
General support: support@1thing.ca

Privacy Officer, 1Thing CRM Inc., 3910 Bathurst St, North York, ON M3H 5Z3, Canada, privacy@1thing.ca. The Privacy Officer is the person accountable for how 1THING handles personal information. Send questions and complaints about our handling of personal information to the Privacy Officer at that address.

For the purposes of Quebec's privacy law (Law 25), the Privacy Officer is also the person in charge of the protection of personal information, and can be reached at privacy@1thing.ca.