Resios is operated from Canada and is committed to protecting your personal information in accordance with the Personal Information Protection and Electronic Documents Act (PIPEDA), Quebec's Act respecting the protection of personal information in the private sector (Law 25), and other applicable Canadian privacy laws. This policy explains what we collect, why we collect it, how it is used and shared, and the choices you have.
Who we are
Resios is operated by Resios Technologies Inc. and provides software for residential real estate teams, developers, and consumers across Canada. In this policy, "Resios", "we", "us", and "our" refer to Resios Technologies Inc. Our privacy officer can be reached at privacy@resios.com for any question relating to this policy or the handling of your personal information.
Our customers' contacts
Resios provides software to real estate developers, brokerages, realtors and employers. When you submit a form, inquiry, application or message to one of these businesses, or a business adds you as a contact, that business decides how your information is used and its privacy policy applies. Resios stores and processes the information on the business's behalf as its service provider: for example, to show your inquiry to its team, send its emails and text messages, record whether you open its emails or click their links when it turns that on, and run the AI features it uses. If the business has not given you its own privacy policy, this section describes how Resios handles your information on the business's behalf. Send requests to access, correct or delete your information to the business, or to privacy@resios.com and we will pass them on. Resios uses this information for its own purposes only to keep the service secure, prevent fraud and abuse, operate and support the service, and produce aggregated, anonymized market statistics from developers who opt in. We do not sell it.
Job applicants and employees
Employers use Resios to post jobs, receive applications and keep employee records. If you apply for a job through a careers page that uses Resios, or your employer keeps your HR records in Resios, the employer decides what is collected and how it is used, and its privacy notice applies. Resios stores and processes this information on the employer's behalf as its service provider. Send questions or requests about your application or employee records to the employer, or to privacy@resios.com and we will pass them on.
Information we collect
We collect information you give us, such as your name, email address, phone number, organization, role, and the content of messages, waitlist and demo requests, forms, survey answers and support requests you send. When you use the platform we also collect your account credentials and settings and the content you and your team add, such as listings, contacts, messages, meeting notes and documents. If you turn on text-message sign-in codes, we keep the phone number you verify and send the codes through Twilio. We collect technical information automatically, including IP address, device and browser details, language, time zone, log data, pages visited and referring URLs. In the signed-in web app we also collect product analytics, as described under "Product analytics and your choices". We keep a record of when you accept our Terms of Service and acknowledge this Privacy Policy, and which versions they were.
How we use information
We use personal information to create and maintain your account, provide and improve the service, respond to inquiries, route form submissions to the right business and team, process payments, provide support, understand how the product is used, keep the platform secure, prevent fraud and abuse, comply with legal obligations, and communicate with you about your account, service updates and, where permitted, marketing. Survey answers submitted through public project forms may be linked to your contact profile so the project team can follow up and understand demand, preferences, and project planning signals. We rely on the performance of our contract with you, our legitimate business interests, your consent, and applicable legal obligations as the bases for these activities under PIPEDA and equivalent provincial laws.
Product analytics and your choices
When you are signed in to the Resios web app, we use PostHog, a product analytics service hosted in the United States, to understand how the product is used and to find problems. It records the pages and features you use, clicks, errors, and device and browser details, and it makes session recordings in which all text and form entries are masked and images and video are hidden. We identify you to PostHog by your Resios user ID, role and organization, not by your name or email address. Capture and recording pause on HR and survey pages. Our public website at resios.com and the websites we host for our customers do not load PostHog. You can turn product analytics off in Settings › Account in the web app, or ask us at privacy@resios.com; PostHog then stops and no longer loads for your account. If your browser sends a Global Privacy Control signal, PostHog does not load in that browser. Our mobile apps send a smaller set of usage events, such as app opens and the screens you view, without recordings; the Settings switch does not apply to them yet.
AI features
Resios uses AI for features such as the assistant, AI nurture messages to leads, meeting notes, meeting suggestions from email, answers about connected files, website chat and content drafts. When these features are used, the content they need, such as messages, contact and project details, files you ask about and meeting transcripts, is sent through OpenRouter to the AI model providers it routes requests to, such as Google. AI output can be wrong; review it before relying on it or sending it.
Google account connections
When you choose Google sign-in, Resios receives your Google account identifier, name, email address and profile information to authenticate your account. Gmail, Google Calendar, Google Ads and connected Google Drive files are separate optional features. We request their permissions when you choose the relevant feature and use the information for the purposes described below.
Gmail conversations
When you connect Gmail, Resios processes your mailbox identity, message identifiers, sender and recipient addresses, dates, subjects, message bodies and reply or thread information on our servers. We retrieve recent messages and subsequent changes to find conversations involving an existing CRM contact in your workspace. Matching conversations are stored in that workspace's CRM and are visible to members with the relevant access permissions. Unmatched messages are processed to determine contact matches but are not added to CRM conversations or used to create new contacts. Resios sends one-to-one messages and replies that you initiate through your connected Gmail account. Organization campaigns and automated email use a separate sending service. The Gmail connector does not edit existing message labels or delete existing Gmail messages.
Google Calendar data
When you connect Google Calendar, Resios reads calendar names, identifiers and access information so you can choose calendars and a write destination. For selected source calendars, we process event identifiers, readable titles, dates and times, time zones, visibility and availability information to display external events and avoid scheduling conflicts. Private or confidential imported events appear as Busy; descriptions, attendees and conference details are not imported into the external-event display. For Resios-managed appointments, we send the title, dates and times, location, description, attendees and optional meeting information you provide to your selected Google calendar. Changes and cancellations in Resios can update or remove the corresponding managed Google event, and requested Google Meet links can be created through the Calendar API. Synchronization cursors and change notifications keep the selected calendars current.
Google Ads data
When a workspace administrator connects Google Ads, Resios reads the authorized account and lead-form information. For mapped forms, we import submitted contact details and answers, submission identifiers and dates, and associated form, campaign and ad attribution into the workspace's CRM and form submissions. The current connector does not create ads or change advertising budgets. Google Ads lead submissions are separate from Gmail and Calendar data; connecting Ads does not authorize the use of Gmail or Calendar content for advertising audiences or targeting.
Google data storage and sharing
Google authorization credentials are stored in encrypted application records to support your connections. Matching Gmail conversations, imported Ads leads and relevant calendar synchronization data are processed on our service infrastructure, with access governed by user and workspace permissions. We use service providers necessary to operate these features. Where a workspace enables AI-assisted communication features, conversation context may be processed through OpenRouter and its configured model providers, including Google, to prepare replies, extract context and coordinate follow-up. Matching message content and derived context can be retained in CRM records, AI workflow memory, drafts and assistant conversation history for these features. Gmail-derived communication activity may also inform the workspace's CRM engagement and lead-scoring features. These uses remain subject to the Google Limited Use restrictions below.
Google connection controls and deletion
Disconnecting a Google feature stops new synchronization and API requests through that connection, including sending through a disconnected Gmail mailbox. Disconnecting Gmail does not necessarily remove your Google sign-in or other Google connections that share the account. Imported CRM records and derived context are not automatically deleted, and enabled workflows may continue to use them until separately removed. You may also remove Resios's access through your Google Account's third-party connections; because some features share a Google project, this can interrupt multiple Resios Google features. To request deletion of Google-derived information held by Resios, email privacy@resios.com with the subject "Google data deletion" and identify the relevant workspace and records. Do not send passwords or access tokens. We verify the request and coordinate with the workspace responsible for the records where necessary, subject to applicable legal obligations. The request must account for relevant imported records, derived context and backup copies; deleting one contact or disconnecting a feature does not necessarily remove every copy. Google-derived data is retained only as needed for the disclosed service purposes or applicable legal obligations, as described in the Retention section below. Requests concerning information held by Google itself must be directed to Google.
Google Limited Use
Resios's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In this policy, Google user data means any information we receive from Google APIs, including Google Workspace data such as Gmail, Google Calendar and Google Drive content, and information derived from it. We use Google user data only to provide the user-facing features described in this policy that you connect it for. We transfer it only as needed to provide those features, including to our AI providers when you use AI features with it, for security, to comply with law, or as part of a merger or acquisition with your explicit prior consent. We do not sell it, and we do not use or transfer it for advertising, including advertising targeting and advertising audiences, or to determine creditworthiness or for lending. We do not use or transfer it to develop, improve or train generalized AI or machine-learning models. Our staff and contractors do not read it unless you give us permission for specific data, it is needed for security or to comply with law, or it is aggregated and anonymized for internal operations. Where another part of this policy describes broader practices, these limits govern Google user data.
Connected files
When you enable a supported Google Drive, Microsoft OneDrive, SharePoint or OneNote connection, Resios uses the permissions you approve to search or select files and retrieve authorized file information and content for the enabled feature. Personal and workspace connections have different sharing permissions. Referenced content may be processed on our servers for extraction, search and enabled AI features through our configured AI providers. A source link is not a public sharing grant; access depends on the owning account, workspace permissions and source availability. Disconnecting stops future access through that connection but does not automatically remove imported records, extracted copies or retained AI context. To request deletion, contact privacy@resios.com and identify the workspace and records. Google Workspace restrictions described above also apply to Google-derived file content.
Microsoft mailbox and calendar connections
If you sign in with Microsoft, Resios receives your name, email address and Microsoft account identifier to authenticate your account. The Microsoft 365 mailbox and Outlook calendar connections are separate optional features. When you connect Microsoft 365, Resios uses the permissions you approve for the selected mailbox or Outlook calendar features. For the mailbox, we process account identity and Inbox and Sent Items message metadata and content to find conversations involving existing CRM contacts; matching conversations are stored in the workspace and are visible to members with the relevant permissions. If you turn on meeting suggestions from email, we also read the folders you choose for it, as described under "Meeting suggestions from email". We send the one-to-one messages and replies you initiate, using provider drafts where required. For selected calendars, we process calendar information and readable event titles, times and availability to display external events and avoid conflicts; private, confidential or personal event titles appear as Busy. We can create, update or remove Resios-managed events in your chosen calendar and request a Teams meeting link where supported. Enabled AI features may process retained matching conversations through OpenRouter and its configured model providers for replies, context and follow-up. Disconnecting stops new use through that connection; imported records and derived context require separate deletion, and enabled workflows may continue using them. To request deletion, contact privacy@resios.com and identify the relevant workspace and records. Do not send passwords or access tokens. Requests concerning information held by Microsoft itself must be directed to Microsoft.
Meeting suggestions from email
Meeting suggestions from email is optional and off by default. For now it works only with a connected Microsoft mailbox; it is not available for Gmail. If you turn it on and choose email folders for a project, then when you ask for suggestions on one of that project's meetings, Resios reads the messages in those folders from the period before the meeting, by default since the last meeting, whether or not the people in them are CRM contacts. To suggest topic updates and follow-up tasks, it sends the text, subject, date and sender and recipient names of those messages, with the meeting's topics, notes and open tasks that you can see, through OpenRouter to an AI model provider. These requests are routed only to providers that commit to keeping no copy of the data and not using it for training. Resios does not store the emails themselves. Suggestions waiting for your review are stored encrypted, each with the email's subject and sender and a quote of up to 300 characters, for up to 7 days, and only you can see them. When you accept or dismiss a suggestion, its quote, subject and sender are erased; a record of which email it came from is kept until the 7 days end so that email is not suggested again. Only what you accept is kept: a topic update becomes an ordinary meeting note labelled "From email" and a task becomes an ordinary task. They follow the meeting's normal access rules like any other note or task: people who can see the meeting can read them, and they can appear in meeting summaries and be used by the AI assistant. Turning the feature off, or removing a project's folders, stops the reading and deletes your pending suggestions; it does not remove notes or tasks you already accepted. Pending suggestions are also deleted soon after the meeting is completed, you disconnect the mailbox or you lose access to the meeting.
AI meeting notes and recording
When an authorized person starts the AI note taker, Resios processes meeting speech to produce transcripts, agenda notes and action items. Virtual meetings use Recall.ai: we send the meeting join link and bot configuration, and Recall joins as a visible participant to process audio, speaker information and transcripts. Where the meeting platform allows it, the note taker also posts a message in the meeting chat saying that it is transcribing. Microphone recordings use Deepgram transcription through OpenRouter. On a meeting page, the recording is also sent through OpenRouter to ElevenLabs to tell voices apart, so the transcript can show Speaker 1, Speaker 2 and so on; these labels do not identify who is speaking. Relevant transcript excerpts and agenda context are sent through OpenRouter to the configured notes model. The person who starts a meeting recording or sends the note taker to a call must confirm that everyone has agreed to be recorded. Automatic joining requires an explicit meeting or series setting. The person who turns it on confirms that invitees have agreed. Resios adds a recording notice to the calendar invitations it manages for automatic joining. When the organizer uses the series option for an existing Teams or Google Meet link, they tell invitees about the note taker and Resios leaves the calendar invitations alone. A virtual note taker continues when you close Resios, so use Stop note taker to end it. Review AI-generated notes and tasks for accuracy before relying on them.
Meeting recording access and retention
Internal team members who can view a meeting can read its transcripts, including recordings another team member started. Filed notes and tasks follow the meeting's normal access rules. External project collaborators cannot read meeting transcripts. The current virtual-meeting configuration uses Recall's US West region and sets temporary recording and transcript retention to 24 hours after completion; Resios requests earlier media deletion after successful reconciliation or discard. This provider setting does not govern all metadata, logs, backups or derived records in Resios. Resios deletes meeting transcripts and the record of who attended a call 90 days after the meeting; notes and tasks already filed from them stay. Discarding a source transcript sooner does not delete notes and tasks already filed. To request deletion of meeting information, contact privacy@resios.com and identify the workspace and meeting without including access tokens or meeting passcodes.
Meta integration data
When a workspace administrator connects Meta through OAuth, Resios uses the authorized Facebook Page and Instant Form information to discover forms and subscribe to lead notifications. For linked forms, we retrieve contact details and submitted answers to create or update CRM contacts and form submissions, with project association determined by the destination Resios form. With authorized read-only advertising access, we also retrieve ad-account, campaign, ad-set and ad performance information to display reports on demand; ad performance data is not persisted by Resios. Customers retain ownership of their Meta assets. Resios does not create or edit ads, change budgets, or administer customer business portfolios.
Meta data deletion
Disconnect the Meta connection in your Resios workspace to stop future syncing and remove its stored authorization tokens. Disconnecting does not automatically delete CRM contacts or form submissions already imported. Imported lead-event payloads, submitted answers and related workflow or assistant context may remain even after a CRM contact is deleted; a deletion request must cover the relevant copies. To request deletion of Meta-derived personal information held in Resios, email privacy@resios.com with the subject "Meta data deletion" and identify the relevant workspace and records, such as the email address you used on a lead form. Do not send passwords or access tokens. If you submitted a lead to a business using Resios, you can also contact that business about its handling of your submission. We may need to verify your identity and coordinate with the relevant business before fulfilling a request, subject to applicable law and any required retention. Requests concerning information held by Meta itself must be directed to Meta.
AI apps you connect
When you connect an AI app such as ChatGPT, Claude or Codex to Resios, you choose a workspace and approve specific permissions. Resios sends the requested records to that app only within those permissions and your current workspace, module and project access. Depending on what you approve, results can include project and unit information, authorized project summaries, developer team-task titles and status, brokerage listings and agent names, CRM contact names and summaries, follow-up task text and the names of assignees and creators, and inventory shared with your brokerage. Where your workspace has email drafts turned on and you approve email access, results can also include the email drafts and templates you can open, with their names, subjects, text and links, your organization's name and email theme name and colours, the captions and descriptions of approved email images, and, for a developer project, the project facts you are allowed to read when you have also approved access to projects. The connector does not return dedicated contact email, phone or budget fields; names and user-written text may still contain personal information. Results become part of your conversation with the AI app, whose terms, privacy policy and retention settings apply. Resios records call identifiers, outcomes, duration and connection activity to operate and secure the connection, without logging returned records or tool arguments. Disconnecting in Settings > Connected apps stops future access; it does not delete results already sent to the AI app. Manage those copies with that app. Reading records does not authorize changes. Where task or email draft actions are enabled, you separately approve access to create tasks, to edit and complete them, or to create or edit email drafts. You review and confirm each change in Resios using your current permissions. The AI app can receive the proposed change and its outcome. Resios keeps the proposed details temporarily to show what will change and keeps a receipt to recognize repeated requests. For an email draft, the proposal keeps the draft's name, subject, preview line, its content as a structured document, the requested changes and short excerpts of the changed text; it does not keep the finished email, which Resios renders again when you review it. Unconfirmed proposals expire within ten minutes of being prepared, or sooner if the AI app's current access token expires first. Cancellation clears the proposal details at once, a cleanup that runs every minute clears them after expiry, and the details of a proposal with a recorded outcome are cleared thirty days later. The task or draft and the identifiers and timestamps used for audit and duplicate prevention remain subject to the applicable account and record retention rules. If a proposed email draft uses an approved image that is already public, preparing the proposal can give that version of the image a lasting public address so the preview can show it. Canceling the proposal or letting it expire does not remove that address; it keeps working while the image stays approved and public. Confirming an email draft only saves it in Resios; it does not send, schedule or publish it. The connector cannot delete tasks, approve business decisions or send customer messages.
How we share information
We do not sell personal information. We share it only with: (a) our service providers, listed below, which process it to operate the platform; (b) members of your organization or transaction (for example, agents, brokerages, developers, buyers, or co-listed parties) where the service is designed to facilitate that exchange; (c) AI apps and other services you choose to connect, within the permissions you approve; (d) professional advisors, auditors, and insurers; (e) parties to a corporate transaction such as a merger, acquisition, or financing; and (f) authorities or other parties where disclosure is required by law, court order, or to protect rights, safety, and property.
Service providers
We use these service providers to run Resios: hosting and storage providers, including Railway and Vercel; email delivery providers, such as Resend; Twilio, for text messages and phone calls sent or received through Resios and for sign-in codes; Stripe, for payments; Cloudflare Turnstile, to check that form submissions come from people rather than bots; PostHog, for product analytics in the signed-in web app; OpenRouter and the AI model providers it routes requests to, such as Google, for AI features; Recall.ai, for the virtual meeting note taker; Deepgram, for speech transcription; and ElevenLabs, to tell speakers apart in meeting recordings. When you connect a Google or Microsoft account, those companies provide the connected services under their own terms and privacy policies.
International transfers
Personal information collected by Resios may be stored or processed in Canada, the United States, or other jurisdictions where our service providers operate. Several of them, including Recall.ai and PostHog, process information in the United States. When personal information is transferred outside the province in which it was collected, it remains subject to this policy and may be accessible to courts, law enforcement, and regulatory authorities in those jurisdictions in accordance with their laws.
Retention
We keep personal information while it is needed to provide the service, as our customers instruct for the records they hold in Resios, and as needed to meet legal, accounting or reporting obligations, resolve disputes and enforce our agreements. Some information is deleted automatically: audio stored for voice notes, dictation and meetings is deleted from our servers once it is transcribed and within 24 hours at most; Recall.ai keeps virtual meeting recordings for up to 24 hours after recording ends; meeting transcripts and call attendance are deleted 90 days after the meeting, while notes and tasks filed from them stay; meeting suggestions from email that you have not accepted are deleted within 7 days, while the notes and tasks you accept stay; and website chat conversations are deleted within 24 hours. Other records, such as contacts, messages, documents and HR records, are kept until the customer or user deletes them or asks us to, subject to any legal requirement to keep them. Deleting a record or disconnecting an integration does not always remove every copy, such as copies in backups. To ask us to delete information, email privacy@resios.com.
Security
We use safeguards designed to protect personal information, including encryption in transit, encryption of stored connection credentials, permission controls within each workspace, and optional two-factor sign-in. No system can be guaranteed to be fully secure, and you are responsible for keeping your account credentials confidential and for the access you give members of your workspace.
Your rights and choices
Subject to applicable law, you have the right to access, correct, update, or request the deletion of personal information we hold about you, to withdraw consent where consent is the basis for processing, to request a copy of your information in a portable format, and to object to or restrict certain processing activities. Residents of Quebec, British Columbia, Alberta, and other jurisdictions with sector-specific privacy laws may have additional rights, including the right to data portability and the right to be informed about automated decision-making. To exercise these rights, contact privacy@resios.com. We will respond within the timelines required by applicable law and may need to verify your identity before fulfilling your request.
Marketing communications
Where required by Canada's Anti-Spam Legislation (CASL), we will obtain your express or implied consent before sending commercial electronic messages, identify the sender, and provide a working unsubscribe mechanism in every message. You can opt out of marketing emails at any time by using the unsubscribe link included in our messages or by contacting us directly. Transactional and account-related messages necessary to operate the service are not subject to opt-out.
Children
The Resios platform is intended for business users and adult consumers. It is not directed to children under the age of majority in their jurisdiction, and we do not knowingly collect personal information from children. If you believe a child has provided us with personal information, please contact us so we can take appropriate action.
Changes to this policy
We may update this policy from time to time to reflect changes in our practices, technologies, legal requirements, or other factors. When we make material changes, we will update the "last updated" date and, where appropriate, provide additional notice through the service or by email. Your continued use of the service after the effective date of an updated policy constitutes acceptance of the changes, to the extent permitted by applicable law.
Contact and complaints
Questions, concerns, or complaints about our handling of personal information can be sent to our privacy officer at privacy@resios.com. If you are not satisfied with our response, you have the right to lodge a complaint with the Office of the Privacy Commissioner of Canada (priv.gc.ca) or with the privacy regulator in your province, including the Commission d'accès à l'information du Québec, the Office of the Information and Privacy Commissioner for British Columbia, or the Office of the Information and Privacy Commissioner of Alberta.
Last updated November 12, 2026.