ORACA AI orca markORACA AI Powering buildings and communities
DevelopersOwners and operatorsMixed-usePlatformCommunities
Work with ORACA
DevelopersOwners and operatorsMixed-usePlatformCommunitiesWork with ORACA
Trust & compliance

Privacy, handled the way we handle everything.

We built ORACA AI for regulated, high-stakes work — so your data is treated as evidence: documented, secured, and never sold. Here's exactly what we collect, why, and the control you keep over it.

Last updated · 26 October 2026Applies to · ORACA AI & deployed agentsAligned with · PIPEDA · CASL

Encrypted end to end

Data is encrypted in transit and at rest. Access is logged and least-privilege.

Never sold

We don't sell or rent your data. Ever. No data brokers. Ad measurement only with your OK (see §08).

Consent-first

We only contact you with your consent — and you can withdraw it anytime.

AI, disclosed

When you talk to an AI agent, we tell you — and explain how it uses your input.

On this page
01Overview02What we collect03How we use it04AI & automation05Consent & contact06Security07Retention08Sharing09Google user data10WhatsApp data11Instagram & Messenger data12Your rights13Contact
01 · Overview

Who we are & what this covers

ORACA AI — represented by Nael, ORACA AI provides AI-assisted services through this website and chat interface. This policy explains how we handle personal information across this website, our booking tools, and the AI agent we operate.

In plain English

When you message our agent, book a call, or submit a form, we collect only what's needed to help you — and we protect it the way the regulated industries we serve demand.

When ORACA AI operates an AI agent, your data is handled under this policy. We act as the data controller for the information you provide — we determine how it is used and are responsible for protecting it.

02 · What we collect

Information we collect

We collect only what each interaction requires. We don't buy personal data or build hidden profiles.

CategoryExamples
You give usName, email address, phone number, and anything you type into the chat, booking form, or inquiry form.
Conversation dataMessages exchanged with our AI agent, the goal or topic you shared, and the outcome (booked, redirected, etc.).
Collected automaticallyBrowser type, approximate region, and session identifiers needed to run and secure the service.

We do not intentionally collect health records, payment card numbers, or government ID through this service. However, our AI chat accepts free-text input — if you type sensitive information, it is received and stored as conversation content.

03 · How we use it

How we use your information

  • To respond to your enquiry and connect you with Nael.
  • To send booking confirmations, reminders, and — with your consent — follow-up communications about your request.
  • To operate, secure, and improve our AI-assisted services.
  • To meet our legal and regulatory record-keeping obligations.

We do not use your conversations to train third-party public AI models, and we do not sell your information.

04 · AI & automation

AI & automated processing

Our chat interface is powered by an AI assistant. We tell you when you're talking to one.

  • Disclosure: the AI agent identifies itself before you share details. The widget displays a clear “AI assistant” label at all times.
  • Scoring: enquiries may be assessed by an AI model to help prioritize follow-up. This supports — it does not replace — professional judgement.
  • Human review: conversations may be reviewed by our team to ensure quality and accuracy.
Your control

You can ask to speak with a human at any time. You can also request that a significant decision not be made by automated means alone.

05 · Consent & contact

Consent & how we contact you

We rely on two consent bases under CASL, and we treat them differently:

BasisWhat it means & how long it lasts
Implied consentWhen you message our agent or submit an enquiry, that's implied consent to reply and follow up about it. Under CASL this lasts 6 months — after that, enquiry-based contacts are automatically excluded from outreach unless you've expressly opted in.
Express consentWhen you explicitly opt in (for example, by ticking a consent checkbox), we may contact you about relevant services until you withdraw it. No 6-month expiry.
  • Every commercial message includes our name, contact information, and an easy unsubscribe mechanism.
  • Reply STOP to any email to be permanently removed from future messages.
  • Withdrawing consent doesn't affect messages strictly needed to complete something you asked for, like a booking confirmation.
The 6-month rule

If you reach out and then go quiet, our system stops contacting you after 6 months on its own — that's CASL, enforced in code, not left to memory.

06 · Security

How we protect your information

Security isn't a feature here — it's the premise. We apply the safeguards our regulated clients require:

  • Encryption in transit and at rest — all data moves over TLS; data stored in our database is encrypted at rest (AES-256).
  • Least-privilege, logged access — every touch of your data is attributable. Our database enforces access controls at the row level.
  • Append-only audit trail — every material action (capture, AI processing, email send, deletion) is logged and retained for accountability.
  • Secret management — API keys and credentials are stored in encrypted environment vaults, never in source code or version control.
  • Ongoing monitoring — we have defined processes for detecting and handling security incidents.

No system is perfectly secure, but we design, document, and audit ours so issues are containable and traceable.

07 · Retention

How long we keep it

We keep personal information only as long as needed for its purpose, to meet legal obligations, and to resolve disputes — then we delete or anonymize it. Retention is tiered and enforced automatically:

Record typeRetention period
Leads with contact info & appointments6 years
Anonymous chat sessions (no email collected)6 months — data minimization: no ongoing relationship basis
Conversation logs6 months
Compliance & audit logExtended — retained to preserve a defensible chain-of-custody record
Unsubscribe recordsPermanent — CASL requires suppression lists to be kept indefinitely

You can ask us about any specific record at any time using the request form in §11.

08 · Sharing

Who we share it with

We share personal information only as needed to run the service. Our sub-processors are bound by contract to process data only on our behalf:

Sub-processorPurpose & data involved
Hosting & database (Vercel, Supabase)Running the application and storing lead, conversation, and appointment records securely. Data resides on US-based servers.
AI model providers (Anthropic, OpenAI)Generating agent responses. The full text of your chat and text messages is sent to Anthropic's or OpenAI's API to produce replies.
Email delivery (Gmail)Booking confirmations, reminders, and consented follow-up emails. Includes your name, email, and appointment details.
Calendar & scheduling (Google)Creating calendar events and meeting links when you book. Includes your name, email, and appointment goal.
Internal notifications (Slack)Notifying our team of new enquiries. Includes your name, email, and a summary of your message.
Text messaging (Twilio)Sending and receiving SMS and WhatsApp messages. Includes your phone number and the messages.
Phone calls (Twilio)If we miss your call, our AI assistant may answer it and tells you it is an AI. Twilio and its speech providers turn your voice into text and the assistant's replies into speech. We keep a written transcript of the call, not an audio recording, and the text goes to our AI model providers like any other message.
WhatsApp (Meta)Delivering WhatsApp messages. Meta handles them under WhatsApp's own terms and privacy policy.

All sub-processors listed above are based in the United States. When your information is processed outside Canada, it may be subject to the laws of that jurisdiction, which may differ from Canadian privacy law. By using our services, you acknowledge this cross-border transfer.

We never sell or rent personal information, and we never share it with data brokers. The only advertising platforms we share with are Meta and Google, only if you choose Accept, to measure our own ads, as described below. We may share with legal or safety authorities when required by law.

Requests from public authorities. We cooperate with government and other public authorities as the law requires. For each request, we check that it is lawful, challenge it if we believe it is not, disclose only the minimum information the law requires, and keep a record of the request, our response, and the reasons for it.

Advertising measurement (Meta)

We advertise on Facebook and Instagram. To see which ads bring in enquiries, we use two Meta tools:

  • The Meta Pixel, a cookie in your browser that tells Meta when you visit our site or submit a form. It stays off until you choose Accept.
  • The Meta Conversions API. If you have chosen Accept, when you submit a form, our server sends Meta your email address and phone number in coded (hashed) form, along with what you asked for. Meta uses them to match you to your Facebook or Instagram account and tell us which ad you saw.
  • Google Ads. Our site also loads Google's ad tag. Until you choose Accept, Google is told not to set ad cookies or use your visit for ads (Google Consent Mode). Accept lets it measure our Google ads.

Meta gives us totals, not who you are. Meta can also use this information for its own advertising, under its own terms.

You choose. A small notice asks the first time you visit. Accept turns this on. Decline sends nothing to Meta or Google's ads, and our site and forms work exactly the same. You can change your choice any time from the "Cookie settings" link, or by emailing privacy@oracaai.com. You can also block cookies in your browser or change your ad settings in your Facebook account.

Cookie settings

09 · Google user data

How we handle Google user data

This section applies if you engage ORACA AI as a client and connect a Google account so we can schedule on your behalf. Data we obtain from Google APIs (“Google user data”) is handled under the rules below, in addition to everything else in this policy. Connecting Google is optional — we also offer a service-account calendar-sharing path that requires no Google sign-in.

What we access

These permissions, requested at the moment you connect and never before:

PermissionWhat we do with it
auth/calendar.freebusyRead busy/free times on the calendars you connect — times only, never event titles, guests or details.
auth/calendar.eventsCreate, update, or cancel the appointments your agent books, on the calendar you connect.
auth/gmail.sendOptional. Send your booking emails from your own Gmail address. Send only — we cannot read, search, or change your mail.
auth/userinfo.emailSee which Google account you connected, to show it to you and to send from it.
auth/meetings.space.readonlyCheck whether a Google Meet call attached to one of those appointments took place, to mark it attended or missed. We do not read chat, recordings or transcripts.

The only Gmail permission we request is send-only, and it is optional. We request no Drive or Docs access, no Contacts access, and no Google Workspace admin or directory access. We cannot read your email.

How we use it

Only to operate the scheduling features you authorized: checking availability before a time is offered, booking it, and issuing reschedules or cancellations. We do not use Google user data for any other product, feature, or purpose.

How we store it

  • Your Google authorization tokens are encrypted at rest, stored per-client with row-level access controls, and held server-side only — never exposed to browser code, written to logs, or committed to version control.
  • Busy/free times are read from Google at the moment we calculate availability and are used to produce that answer. We do not build or keep a copy of your calendar.
  • What we retain is the appointment record itself — the booking your agent made, under the retention schedule in §07.

How we share it

  • Google user data is transferred only to the sub-processors needed to run the authorized feature (§08), under contract and only for that purpose.
  • We never sell or rent it, and never transfer it to advertising platforms, data brokers, or for targeted advertising.
  • We never use it for credit assessment, lending decisions, or any similar purpose.
  • We never use or transfer Google user data to develop, improve, or train generalized or non-personalized AI or machine learning models — not by us, and not by any provider we use.

Who can read it

ORACA AI personnel do not read Google user data except:

  • with your explicit, specific agreement, to resolve an issue you raised;
  • where necessary for security investigations or abuse prevention;
  • where required by law; or
  • where the data has been aggregated and anonymized for internal operational metrics.

Limited Use

Affirmative statement

ORACA AI'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.

Withdrawing access

You can revoke ORACA AI's access at any time at myaccount.google.com/permissions, or by emailing us. On revocation we stop calling Google APIs on your behalf immediately and delete your stored tokens within 30 days; scheduling stops working, and calendar events already created stay on your calendar untouched. On termination we revoke and delete them within 30 days without you having to ask.

10 · WhatsApp data

How we handle WhatsApp data

This section applies if you are a business that connects a WhatsApp Business Account to ORACA AI (through Meta's “Login with Facebook” signup), and to anyone who sends a WhatsApp message to a business that uses ORACA AI. It adds to everything else in this policy.

What we receive

  • From the business: the IDs of its WhatsApp Business Account and phone number, the phone number and display name, and its message templates.
  • From people who message the business: their WhatsApp phone number and profile name, the messages and any files they send, and delivery and read status for the replies.

The connection asks Meta for two permissions only: whatsapp_business_messaging (to send and receive messages) and whatsapp_business_management (to manage the account's phone number and message templates). It does not give us access to the business's Facebook profile, Pages, ads or personal contacts.

How we use it

  • To answer messages on the business's behalf with its AI assistant, and to hand a conversation to the business when needed.
  • To send the booking confirmations and reminders a person asked for.
  • To show the business its own conversations and leads in its ORACA AI console.
  • To stop messaging anyone who replies STOP.

We do not sell WhatsApp data, use it for advertising, or use it to train general AI models. Message text is sent to our AI model provider only to write the reply (see §08).

How we store and share it

Messages travel through Twilio, Meta's approved WhatsApp partner. Each business we connect gets its own Twilio account and its own WhatsApp Business Account, and its messages are stored in that business's own database, encrypted at rest. One business can never see another's messages. Access credentials are kept server-side only and never shown in a browser or written to logs.

Disconnecting and deleting your data

Businesses: you can disconnect at any time by removing ORACA AI's access in Meta Business Suite (Settings → Accounts → WhatsApp accounts → Partners), or by emailing us. When you disconnect, we stop sending and receiving messages for you straight away and delete your stored WhatsApp messages and credentials within 30 days, except records the law requires us to keep (such as opt-out lists).

People who messaged a business: reply STOP to stop messages. To have your messages deleted, use the request form in §12 or email our Privacy Officer (§13). We confirm within 30 days.

11 · Instagram & Messenger data

How we handle Instagram and Messenger data

This section applies if you are a business that connects a Facebook Page or an Instagram professional account to ORACA AI (through Meta's “Login with Facebook”), and to anyone who sends a direct message to a business that uses ORACA AI on Instagram or Facebook Messenger. It adds to everything else in this policy.

What we receive

  • From the business: the ID and name of its Facebook Page, the ID and username of the Instagram account linked to it, and an access token for that Page.
  • From people who message the business: the ID Meta gives them for that business's account (not their phone number or email), the messages and any files they send, and replies the business's staff send by hand.

The connection asks Meta only for the permissions needed to read and answer the business's direct messages: pages_show_list, pages_messaging, pages_manage_metadata, instagram_basic and instagram_manage_messages. It does not let us post, run ads, or see anyone's personal profile, friends or followers.

How we use it

  • To answer direct messages on the business's behalf with its AI assistant, which says it is automated in its first reply.
  • To step back when the business's staff reply by hand, and to hand a conversation to the business when needed.
  • To show the business its own conversations and leads in its ORACA AI console.
  • To stop messaging anyone who sends STOP.

We only reply to people who messaged the business first, within the time Meta allows. We do not sell this data, use it for advertising, or use it to train general AI models. Message text is sent to our AI model provider only to write the reply (see §08).

How we store and share it

Messages come to us directly from Meta and are stored in the business's own database, encrypted at rest. One business can never see another's messages. Page access tokens are kept server-side only and never shown in a browser or written to logs.

Disconnecting and deleting your data

Businesses: you can disconnect at any time by removing ORACA AI under Business integrations in your Facebook settings or Meta Business Suite, or by emailing us. When you disconnect, we stop answering messages for you straight away and delete your stored Instagram and Messenger messages and tokens within 30 days, except records the law requires us to keep (such as opt-out lists).

People who messaged a business: send STOP to stop messages. To have your messages deleted, use the request form in §12 or email our Privacy Officer (§13). We confirm within 30 days.

12 · Your rights

Your rights & choices

Under PIPEDA, you have the right to:

  • Access — request a copy of the personal information we hold about you. We will respond within 30 days (PIPEDA s.8(3)).
  • Correction — request that inaccurate or incomplete information be corrected (PIPEDA s.12).
  • Deletion — request that your personal information be deleted from our active systems. We will honour requests except where law requires retention.
  • Withdrawal of consent — withdraw consent to our use of your personal information at any time, which may limit our ability to serve you.
  • Unsubscribe — reply STOP to any commercial email to be permanently removed from our contact list.

We'll verify your identity before disclosing records, and respond within 30 days. You may also raise a concern directly with the Office of the Privacy Commissioner of Canada.

Privacy request · access, correction or deletion

ORACA AI will respond within 30 days as required by PIPEDA s.8(3). We may ask you to verify your identity before disclosing records.

13 · Contact

Talk to us about your privacy

Questions, requests, or concerns about this policy or your data — reach our Privacy Officer directly.

Privacy Officer

Mead · ORACA AI
3-644 Portland Street, Box 107, Dartmouth, NS B2W 6C4, Canada
privacy@oracaai.com
Response within one business day
Email the Privacy Officer →
ORACA AI orca markORACA AI Powering buildings and communities

Intelligence for the places we share. Built and operated from Halifax, Nova Scotia.

+1 782-819-2847

For

DevelopersOwners and operatorsMixed-use developments

The platform

Property intelligence platformInside an intelligent propertyConnected communitiesInsights

Work with ORACA

Explore what ORACA could powerStrategic partnershipPricingBook a callAbout ORACA AIPrivacyTerms
ORACA AI. Documented, auditable, defensible. Last reviewed 2026-11-14.Every building on this site is an illustration built for it. No client property is shown.