Privacy Policy

This policy applies to all products, applications and services provided by Bitwize.ai, Inc. ("we", "us", "our"), a corporation incorporated under the laws of the Province of Ontario, Canada. That includes Aria, Chaise, Logue, ChatBro and the bitwize.ai website (together, the "Services").

Read Part A, then the one part that covers the product you use.

1. Who we are

Bitwize.ai, Inc. is the organization responsible for the personal information described in this policy. We are based in Ontario, Canada, and can be reached at privacy@bitwize.ai.

2. What each product collects

• Aria requires an account and runs on our servers. It collects your name, contact details, the address where work happens, your device location, what you tell it about the job, your booking history and a payment token held by Stripe. It cannot work without these. Part B covers each in turn.
• Chaise is licensed to a shop and runs on our servers. It holds the shop's appointments, the people who work there and the shop's own client records — names, mobile numbers, addresses and notes. Part C.
• Logue and ChatBro run on your device. There is no account, no telemetry, and your documents, recordings and transcripts never reach us. Part D.
• This website collects anonymous, cookieless analytics and whatever you type into a form. Part E.

3. What we never do

We do not sell your personal information, and we never have. We do not train AI models on your content. Every processor named in this policy is bound by contract to one stated purpose and may not use your information for its own.

We cannot say your information reaches nobody: §22 names the processors Aria depends on, §28 names Chaise's, and some of them operate outside Canada. What we can say is that none of it is sold, and none of it is repurposed.

4. Your rights, and how to use them

Under Canada's Personal Information Protection and Electronic Documents Act (PIPEDA) you may:

• Access the personal information we hold about you, and be told how it has been used and who it has been disclosed to.
• Correct anything inaccurate or incomplete.
• Withdraw consent at any time, subject to legal and contractual limits. Withdrawing consent to the processing Aria depends on (location, payments, identity) means closing your Aria account, because the service cannot run without them.
• Delete your account and the personal information attached to it. We keep what tax, accounting and fraud-prevention law requires us to keep; §23 says what and for how long.
• Complain to the Office of the Privacy Commissioner of Canada if you believe we have got this wrong.

Email privacy@bitwize.ai. We respond within 30 days. We will ask you to verify your identity first, and we will not charge you for a reasonable request.

If you are in Quebec, section 37 sets out the additional rights that apply to you.

5. Security

Data in transit is encrypted with TLS. Data at rest on our servers is encrypted. Access to production systems is restricted to the people who need it, and payment card numbers never reach our servers at all. Stripe holds those, and we hold only a token (§16).

On your own device, Logue and ChatBro rely on the platform's encryption (FileVault on macOS, Data Protection on iOS). You are responsible for the security of the device itself and for who can physically pick it up.

No system is perfectly secure, including ours.

6. If there is a breach

Where a breach of security safeguards creates a real risk of significant harm, PIPEDA requires us to report it to the Office of the Privacy Commissioner of Canada and to notify affected individuals as soon as feasible, and to keep records of all breaches regardless of whether they meet that threshold. We will do both, notify you directly rather than by press release, and say what we know and what we do not yet know.

7. How long we keep things

The general rule is that we keep personal information only as long as it serves the purpose it was collected for, or as long as the law requires, whichever is longer. Aria's per-type schedule is in §23 and Chaise's is in §31. Data held on your own device by Logue or ChatBro is kept until you delete it; we have no copy and no say in it.

8. Children

Aria is for adults. You must be at least 18 to hold an Aria account, whether as a customer or a worker. Work is being arranged in someone's home and money is changing hands, and neither is appropriate to arrange through a minor.

Logue and ChatBro are not directed at children under 13 (or under 16 where a higher age of digital consent applies). Between 13 and 18, they may be used with the consent and supervision of a parent or guardian.

If you believe a child has given us personal information, write to privacy@bitwize.ai and we will delete it.

9. Changes to this policy

We will update this page when our practices change. For material changes affecting Aria, we will also notify account holders by email at least 30 days before they take effect, so you can close your account first if you disagree. The date at the top of this page always reflects the current version.

10. Governing law

This policy is governed by the laws of the Province of Ontario and the federal laws of Canada that apply there. Nothing in it removes a protection given to you by the mandatory consumer or data protection law of your own jurisdiction.

11. Contact

Bitwize.ai, Inc.
Ontario, Canada
Privacy: privacy@bitwize.ai
Everything else: support@bitwize.ai

12. Your account

To use Aria you give us your name, email address and mobile number, and we keep a record of the bookings you make. Workers additionally provide the information described in §19.

We use this to run your account, to reach you about a booking, to tell the other side of a job who is coming or who is expecting them, and to prevent fraud and abuse. The legal basis is the performance of our agreement with you, and your consent.

13. Location

Aria collects your device's precise location, and it is not optional in any useful sense. Matching you to a worker who can actually reach you is the product, and without a location there is nothing to match on.

Concretely:

• We collect precise location when you are actively using the app, and the service address you enter for a job.
• Workers share location while they are on their way to a job, so you can see they are coming. It stops when the job ends.
• We do not track your location in the background when you are not using Aria and have no active booking.
• You can refuse or revoke the permission in your device settings. Aria will then ask you to type an address instead, and features that depend on knowing where you are will not work.

A job's service address is shared with the worker assigned to it once you approve the booking, and not before.

14. What you tell Aria

Aria works by you describing a job in your own words, so what you say is the input. We store the job descriptions you write or speak, the conversation you have with Aria, photos you attach, and details you give about your home so you do not have to repeat them next time.

You can see what Aria has remembered about you and clear it at any time from within the app. Clearing it means Aria will ask you those things again.

Because this is free text, it contains whatever you put in it. Please do not tell Aria things it does not need. It needs to know that the leak is under the kitchen sink, not your health history.

15. Voice

When you hold to talk, speech is converted to text on your own device. The audio recording does not leave your phone and we never receive it. What we receive is the text, which is then handled exactly like text you had typed (§14).

We do not create a voiceprint, we do not use voice to identify you, and we hold no biometric information of any kind. If that changes, this section will be updated before the change takes effect.

16. Payments

Card payments are processed by Stripe. Your card details go directly to Stripe and are never received or stored on our servers; we hold a token that lets us charge the card without being able to read it. Stripe processes this information as an independent controller under its own privacy policy.

When you book, your card is authorized for the agreed amount. The money is held against your card but not taken. It is captured only once you have approved the finished job. A booking made far enough in advance may need to be re-authorized before the job; Aria will tell you if that fails.

We keep a record of what was charged, when, for which job, and to which worker it was paid. Canadian tax and accounting law requires us to, and §23 says for how long.

17. Automated matching and pricing

You are entitled to know when a decision affecting you is made by a computer rather than a person.

Aria decides automatically which worker to put in front of you and what the job should cost. The principal factors are the type of job you have described, where it is, when you want it done, which workers are available and near enough to do it, their verification status and their rating history, and prevailing prices for that kind of work.

You are not stuck with the result:

• Nothing is booked without you. You can require your own approval on every booking, so no automated outcome takes effect until you say yes to it.
• You can ask a person to look at it. Write to privacy@bitwize.ai and a member of our team, not a system, will review the outcome, hear what you have to say about it, and can change it.
• You can ask what was used. We will tell you which of your information fed the decision, and correct it if it was wrong.

We do not use automated processing to make decisions about your credit, your employment, or anything else beyond arranging the job in front of you.

18. AI processing

Aria uses large language models to understand what you have asked for and to arrange it. Those models are accessed through OpenRouter, which routes requests to model providers that are contractually bound to a zero data retention policy. They do not keep your request after answering it, and they do not train on it.

Two limits on that claim, stated precisely:

• We do not attach your identity. Your name, email, phone number, payment details and account identifiers are not sent to a model provider. What is sent is the substance of the job and the conversation about it.
• What you write is what is sent. The text you type or speak is transmitted for processing, and we cannot control what you put in it. If you tell Aria your address in the middle of a sentence, that sentence is what gets processed. This is why §14 asks you not to include things Aria does not need.

19. Worker verification and background checks

This section applies to workers, not customers.

Before you can accept work through Aria we verify who you are. This is done by [SCREENING VENDOR], a third-party screening provider, and it involves confirming your identity against government-issued ID and obtaining a criminal record check.

Criminal record information is sensitive, and we treat it accordingly:

• It is collected only with your express, separate consent, given before the check runs.
• We receive an outcome (cleared or not cleared) and the information needed to explain a decision to you. We do not hold your full record.
• It is never shown to customers. What a customer sees is that you are verified, not what was checked.
• It is used to decide whether you can work through Aria, and for nothing else.
• You may ask what the outcome was based on, dispute it with the screening provider, and ask us to reconsider.

We also collect the information needed to pay you and to meet our tax reporting obligations.

20. What the other side of a booking sees

Aria is a two-sided service, so some of your information necessarily reaches the other person. This is what crosses.

• The worker sees: your first name, the job description you wrote, any photos you attached to it, the service address and access details (released when you approve the booking, not while a job is merely being arranged), and a contact number for the day of the job.
• You see: the worker's name and photo, that they are verified, their rating and job count, their reviews, and their location while they are travelling to you.
• Neither side sees the other's email address, payment details, home address (for the worker), or any part of a background check.

A worker may photograph their own work, and those photos reach you and us. They may not photograph or record anything else in your home, and may not keep or reuse a photo for any purpose beyond the job and any dispute about it. §37 of the Terms binds them to that.

After a job is finished and reviewed, contact details are no longer exchanged through the app.

21. Reviews and ratings

A review you leave is published with your first name and last initial, and it stays visible after you close your account, because removing it would misrepresent the worker's record. If you want a review taken down, ask us and we will consider it on the facts.

A worker's rating is calculated from customer reviews and is shown to customers before they approve a booking.

22. Who else processes your information

We use the following service providers. Each is bound by a data processing agreement, and each is used for the stated purpose and nothing else.

Transfers outside Canada. Some of these providers process data in the United States and elsewhere. Under PIPEDA we remain accountable for your information wherever it is processed, and we use providers who commit contractually to comparable protection. Being outside Canada does mean the information can be subject to the laws of the country it is in.

23. How long we keep Aria data

Closing your account deletes what the table above lists, except for three things. We keep the payment record, because Canadian tax law requires seven years. We keep your reviews, as part of the worker's record (§21). We keep a worker's verification outcome for 24 months. The payment record is separated from your profile, so it can no longer be used to contact or identify you.

24. Emails and text messages

Aria sends you messages about your bookings: a worker is confirmed, someone is on their way, a job is waiting for your approval. These are part of the service, and you cannot switch them off while you have an active booking, though you can choose between email and SMS.

Marketing email is separate. We send it only if you have opted in, the opt-in is never pre-ticked, and every message carries a working unsubscribe link and our identity and address, as Canada's Anti-Spam Legislation requires.

25. Who controls what

For the people who work in a shop — an owner, an employee, a chair renter, an apprentice — we are the controller of the account information in §26, and you exercise the rights in §4 with us directly.

For a shop's own client records, the shop is the controller and we are only its processor. We hold those records to run the service for that shop and for nothing else. If you are a client of a salon and want your record corrected or deleted, ask the shop: it decides, and we act on its instruction. If you cannot reach the shop, write to us and we will help you reach it.

26. What Chaise collects

• The name, mobile number and address of a person set up in a shop
• Date of birth and gender, where a shop records them on a person's own record
• A profile photo, where one is uploaded
• Notes a staff member keeps on a client, and notes attached to an appointment
• Appointments, services, prices and working hours
• An account identifier, and a session token held in your device's secure storage

There is no password. You sign in with your mobile number and a single-use code we text you.

27. What Chaise does not collect

No device location, precise or approximate: the database has no field for a coordinate. An address someone types is ordinary contact information, and no position is ever taken from a device.

No payment or financial information. Chaise processes no payments, and a shop takes money from its clients exactly as it did before.

No advertising identifier, no analytics SDK and no crash-reporting SDK. Nothing in Chaise is combined with third-party data for advertising or shared with a data broker, which is why the app asks for no tracking permission. It requests no access to your contacts, your health data or your browsing history, because it has no feature that uses them.

28. Who else processes Chaise information

• Twilio — a mobile number, to send a sign-in code or an appointment notification.
• Google (Places API) — a partial business address typed by an owner, sent from our servers rather than from your device, so no device identifier, IP address or coordinate reaches Google.
• Amazon Web Services — hosting.

No other third party receives information from Chaise. Each is bound by contract to the purpose named here and to nothing else.

29. Where Chaise information is kept

On servers in Canada, in the Montreal region. Appointments, client records and notes do not leave the country. If that ever changes we will say so here before it does.

30. Text messages from Chaise

A sign-in code is sent because you asked to sign in. A notification to a shop's client is sent on that shop's instruction and rests on the consent the shop obtained from its own client; every such message identifies the shop and offers a way to stop. Canada's Anti-Spam Legislation places obligations on the shop and on us, and the shop's agreement with us records that division.

31. How long we keep Chaise data

For as long as the shop's account is open. When a shop closes its account we delete or irreversibly anonymise its records, except where a legal obligation requires us to keep something — billing and tax records being the usual example. Closing an account also stops billing; it is not a request you have to chase.

32. Everything stays on your device

Logue and ChatBro process content locally. Documents, recordings, transcriptions, conversation history, preferences and downloaded AI models are stored on your device, and we cannot access any of it. There is no account to create and no licensing system.

The AI models are downloaded once, then run offline. Core functionality needs no internet connection at all. You can verify this by unplugging the network, or, since Logue is MIT-licensed and public, by reading the source.

These applications collect no analytics or telemetry of any kind. No tracking SDK, no usage metrics, no network calls for analytics.

33. The optional features that do use the network

Each of these is off by default and requires you to turn it on:

• Third-party AI APIs: you may point the app at an external provider using your own account and key. Content you send is then subject to that provider's privacy policy. When this is off, no content leaves your device.
• Web search: sends your search query and nothing else. Never a document, a meeting or a transcript. Results are summarized locally.
• Cloud sync: where offered, via Apple iCloud, governed by Apple's privacy policy and disabled in your device settings.

Separately, the app checks GitHub for new versions and downloads AI models. Neither transmits your content.

You can confirm all of this with any network monitoring tool: Little Snitch, Wireshark, whatever you already trust.

34. Distribution

Where an application is distributed through Apple's App Store, installation, updates and any payment are handled by Apple under Apple's privacy policy. For directly distributed applications, Apple performs code signing and notarization only. Open-source releases are distributed through GitHub, so downloading or checking for an update involves a request to GitHub under its privacy statement.

35. Analytics and cookies

This website does not use cookies. We run Google Analytics 4 in cookieless mode (Consent Mode v2 with analytics storage denied), which gives us page views, visit duration and general traffic without placing anything on your device or tracking you individually. Google may briefly process your IP address for geolocation; GA4 does not store full IP addresses. See Google's privacy policy.

The legal basis is legitimate interest: we need to know which pages do their job. We have assessed this against your rights and concluded it does not override them; ask at privacy@bitwize.ai if you want the detail. Under PIPEDA we rely on implied consent, which is reasonable for anonymous analytics.

Global Privacy Control: we honour GPC signals. When one is present, analytics collection is disabled outright, and we treat it as a valid opt-out request.

Do Not Track: we do not respond to DNT, because there is still no agreed standard for what a response would mean. GPC is the signal we honour instead.

To opt out, turn on Global Privacy Control in your browser, as described above, or block the script. Analytics is the only third-party script on this site, and blocking it stops nothing here from working.

36. Forms

The waitlist and contact forms are delivered through Web3Forms, so that an email address can reach us without us running a server for it. We ask for your email address, your city, and whether you are hiring or working. Nothing else, and nothing inferred.

37. Quebec (Law 25)

If you are in Quebec, you additionally have the right to data portability, the right to have your information de-indexed or ceased to be disseminated in defined circumstances, and, where a decision is based exclusively on automated processing, the right to be informed of it, to know the principal factors behind it, and to have it reviewed by a person. §17 sets those factors out and tells you how to request that review. Complaints go to the Commission d'accès à l'information du Québec.