What we collect, and what we don’t.

The short version

This summary is not the policy — the sections below are — but nothing in them contradicts it.

Who this covers

This policy covers the Brizeet mobile app on iOS and Android, this website, and the emails we send you. It applies to everyone who uses Brizeet, whichever side of a delivery you are on: people having something picked up, people driving, and the small number of people at Brizeet who verify drivers and answer support.

Brizeet is operated from Ontario, Canada, and handles personal information under Canada’s Personal Information Protection and Electronic Documents Act (PIPEDA) and applicable provincial law. The service is offered in Canada.

Where we say “we”, we mean Brizeet. Where we say “you”, we mean the person holding the account.

What you give us

Everything in this section is something you typed, chose or attached.

Your account

Name, email address and a password. The password is stored only as a hash by our authentication provider — nobody at Brizeet can read it, and we cannot tell you what it is.

Your profile

Phone number and city, both optional. A photo, also optional: if you would rather not upload a face, the app draws one from a seed on your device and no image is uploaded at all.

If you drive

Vehicle type, make, model and colour, number plate, and the last four digits of your driving licence. A person at Brizeet reviews these before your first job. We do not ask for, and do not keep, a photograph or scan of the licence itself.

Your routes

Drivers describe trips they already make: a start, an end, how far either side of that line they will stray, which days, and which hours. This is what matching runs against.

What you post

The pickup and drop-off addresses and their coordinates, what the item is, your notes for the shop, the deadline you chose, and the amount you are offering.

Files you attach

Photos or PDFs you add to a request — a prescription, a receipt, a picture of the item, a piece of ID a shop insists on. You choose each one. We do not read your photo library.

Saved places

Addresses you save with a label, so you do not retype home every time.

Messages

Text and images sent in the chat attached to a job. That chat exists only for that job and only between the two people on it.

Ratings and reviews

The stars and words you leave after a delivery.

Disputes and support

What you write when you open a dispute, and anything you send us by email.

What your phone gives us

Only with your permission, and every one of these can be refused or withdrawn later in your device settings. The app is built to stay usable without any of them.

Location

Read only while the app is open. It sorts pickups near you, centres the map, and — for a driver, at the moment they tap a status step during a job — records a single point alongside that step. There is no background tracking and no continuous trail. Decline it and everything still works: you type addresses instead.

Camera and photos

Only the specific image you take or pick. The app has no access to the rest of your library.

Notifications

A push token issued by Apple or Google that identifies the device, not you, so a notification can find it. Turn notifications off and the token is deleted.

Basic technical facts

App version, platform and the timing of your requests to our server, kept in ordinary server logs so faults can be traced and abuse can be rate-limited. No advertising identifier, ever.

Error reports

When something in the app goes wrong, it sends us a report: the app version, the platform, which part of the app failed, the technical error message, and a short reference shown on the screen so you can quote it to us. It is sent to our own database — there is no crash-reporting service and no third party involved. Before anything leaves your phone it goes through a filter that strips out addresses, phone numbers, names, coordinates, codes and anything you typed, so what arrives says which screen broke and not what you were doing on it. Kept 30 days.

Which screens got used

A short, fixed list of things the app records so we can tell whether it works: that a job card was shown to a driver and whether it was one on their route, that they opened it, that they took it, and which step of the request form somebody reached. That is the whole list, and it is enforced in the database rather than in the app — anything not on it is refused. Each record holds the reference of the delivery it is about and nothing else: no address, no coordinates, no names and nothing you typed. It goes to our own database; there is no analytics service and no third party involved. Kept 90 days. It exists for one question — whether matching a driver's route actually helps them find work — and we would rather find out we are wrong than not find out.

The update check

Brizeet is installed as a downloaded file rather than from an app store, so it has to ask directly whether a fix is available — otherwise a mistake we have already corrected stays on your phone until you happen to reinstall by hand. On launch the app asks the update service run by Expo, who build the app for us, whether there is newer code for the build you are running. That request carries the platform, an identifier for which build you have and an anonymous installation id — no account, no name, no email, no location and nothing about your deliveries. It is the only request the app makes to anybody other than us, it collects nothing on our behalf, and it exists because the alternative is being unable to fix anything already installed.

What we record as you go

These are written by Brizeet rather than by you, because a delivery that nobody can account for afterwards is not much use to either side.

• A status timeline with timestamps — accepted, on my way, at the store, picked up, delivered — and the proof photographs taken at pickup and drop-off.
• Your 4-digit handover code, and a count of the wrong codes tried against it, so it cannot be guessed through. The code is never shown to the driver.
• Whether a handover went ahead without that code, and the driver’s written account of who took the goods.
• Earnings totals, rating averages, and counts of completed and cancelled jobs.
• An audit log of consequential actions — a driver approved or rejected, an account suspended, a dispute opened or resolved, an account deleted — recording who did it and when.
• Which notifications we sent you, and whether you have read them.

What we never collect

• Card or bank details
• Background location
• Advertising or analytics IDs
• Contacts, calendar, microphone
• The rest of your photo library
• Your browsing history

• Card numbers or bank details. Brizeet does not process, hold or move money. You and the driver agree an amount in the app and settle it between yourselves in cash or by e-transfer, so there is nothing of that kind for us to store.
• Background or continuous location. The app never asks for “always” location, and background location is switched off in the build itself.
• Advertising identifiers. There is no advertising SDK, no analytics SDK and no third-party tracker in the app or on this website. Nothing here follows you anywhere else, and there is no cookie to accept because we set none. What the app counts about itself — which screens got used — and what it sends when something breaks — error reports — both go to our own database and to nobody else; the entries above say exactly what each one holds and what is stripped out first. The one request the app makes to anybody other than us is the update check, also described above, which asks whether newer code exists and reports nothing about you to anyone. What we do count on this website is described under this website below.
• Anything outside the permissions above. No contacts, no calendar, no microphone, no health or fitness data, no browsing history.
• Anyone else’s information for its own sake. If you post a drop-off at someone else’s address, we hold that address to complete the delivery and for no other purpose.

We do not sell, rent or trade personal information, and we do not share it with advertisers or data brokers. There is no arrangement under which we could.

This website

Two things are counted here, both entirely on the server. No cookie is set, no script tracks you, and nothing is stored that could pick you out of the traffic. There is no consent banner because there is nothing to consent to.

Page views

Cloudflare Web Analytics counts visits to these pages from the request itself. It records the page, the referring site, the country, and the kind of device — and no cookie, no fingerprint and no identifier of any sort. We cannot tell one visitor from another, or the same visitor from one day to the next.

App downloads

When the Android app is downloaded from this site we add one to a counter, along with which build it was and which country the request came from. Not your IP address, not your browser, not a session. It exists to answer one question — how many people who read this page go on to install the app — and it cannot answer any other.

The page also fetches a small file from this same domain to show the current version number and file size of the download. That request goes to us and to nobody else.

Why we hold each thing

We collect a piece of information when a specific part of the product stops working without it. If a purpose below ever ends, so does the collection.

Running a delivery

Addresses, item, deadline, amount, attachments, messages, phone number.

Matching

Pickup and drop-off coordinates against a driver’s route, corridor width, days and hours — which is how a job lands with someone already going that way.

Proof and safety

Handover codes and their failed attempts, proof photographs, status points, the unverified-handover flag and the driver’s note.

Trust

Driver vehicle and licence details, verification decisions, ratings, and the counts behind them.

Telling you things

Push tokens and email address, for job updates, deadline reminders, receipts and account emails.

Support and disputes

Account details, the request in question and its history, and what each side has written about it.

Keeping the platform honest

Rate-limit counters, the audit log, and account status, to stop abuse, spam and fraud.

Improving the product

Counts and averages only — requests per day, completion rate, time to accept — read in aggregate, never as a profile of one person.

We rely on your consent, given when you create the account and again each time you grant a device permission. You can withdraw it at any time by turning a permission off, changing your notification preferences, or deleting your account; some of that will stop parts of Brizeet from working, which is said plainly at the point you do it. We also keep and use some information where the law requires it, or to establish or defend a legal claim.

What other people can see

This is the part most people are actually asking about, so it is set out in full. The short of it is the same map twice:

Before a driver accepts your job

• The shop or pickup place by name, and the neighbourhood.
• A deliberately fuzzed map pin — a circle roughly 500 m wide, not your building.
• What the item is, when it is due, and what it pays.
• Not your street address, not your phone number, not your notes, not your attachments, not your last name.

After they accept

• The full address, unit included, for both ends.
• Your name and photo, and your phone number — for that job.
• Your notes and the files you attached.
• A chat that exists only for that job.

If the driver releases the job or it is cancelled, that access ends with it.

What you see about a driver

• Their name and photo, vehicle and plate, and their rating.
• Their proof photographs and the status timeline.
• Not their live position. Brizeet is a scheduled errand, not a tracked one, and a moving dot would cost a driver more privacy than it buys you certainty.

Brizeet staff

A small number of people at Brizeet can see account and request details in order to verify drivers, answer support and settle disputes. Those actions are written to an audit log that records who did what and when, and that log cannot be edited or deleted by anyone.

Everyone else

Nothing. There is no public profile, no public feed and no shareable link. Stored files — attachments, proof photographs, avatars — sit in private buckets and are reachable only through short-lived signed links issued to the customer, the assigned driver, or an admin.

Who else handles it

Running the app means using a handful of specialist services. Each is bound to use what it receives only to provide that service to us.

Supabase

Our database, file storage and sign-in. Effectively everything in this policy is stored there.

Expo, Apple and Google

Push delivery. They receive the device token and the text of the notification — which is why a notification says “a delivery was updated” rather than repeating an address.

Resend

Sends account email: your verification code, password resets, receipts. It receives your email address and the message.

Google Maps Platform

Map tiles, address search and turning coordinates into street names. When you move a map or search an address, that query reaches Google under Google’s own privacy policy.

Apple and Google app stores

Distribute the app. They tell us nothing about you individually.

Beyond those, we disclose personal information only in three situations: when the law compels it and we are satisfied the demand is valid; when it is necessary to protect someone’s safety or to investigate serious misuse of Brizeet; and if Brizeet is ever sold or merged, in which case the buyer inherits this policy and you will be told before anything about your data changes.

Where it is kept

Brizeet’s database and file storage run in the United States (Oregon, on Amazon Web Services via Supabase). Email is sent through Resend and push notifications through Expo, Apple and Google, all of which may process the information in the United States or elsewhere.

That means your information is stored and processed outside Canada, and while it is there it may be accessible to courts, law enforcement and national security authorities of that country under their laws. We are telling you this because Canadian privacy law expects it to be said, not buried.

How long we keep it

Some of it goes on a timer whether you ask or not. A scheduled job runs against the database and deletes the following without anyone being involved:

• Driver location points 7 days
• Email codes, once expired 1 day
• Rate-limit counters 2 days
• Error reports from the app 30 days
• Which screens got used 90 days
• Notifications you have read 90 days

The bars are to scale against the longest of the five. Email codes are single-use and short-lived before that timer even starts.

Everything else — your profile, your requests and their history, messages, attachments, ratings, disputes — is kept while your account exists, because it is the record of deliveries you and other people took part in. When you delete your account, see your choices below for exactly what is erased and what survives without your name on it.

Audit log entries are kept as a permanent record of consequential actions. They identify the account that acted; once that account is deleted, the name attached to it is gone.

Your choices

See it and correct it

Your profile, saved places, routes, requests, messages and ratings are all visible in the app and most of them are editable there. For a copy of everything we hold about you, or a correction the app will not let you make, email [email protected] from the address on the account. We will respond within 30 days.

Delete it

In the app: Profile → Delete my account. There is a fuller walkthrough on the deleting your account page, including what is erased, what is kept, and how to do it if you can no longer sign in.

Turn the permissions off

Location, camera, photos and notifications are all revocable in your device’s own settings, at any time, without telling us first. The app will say what stops working and carry on.

Choose which emails and pushes you get

In the app: Profile → Notifications. New job requests, delivery and account updates, messages, offers and tips, and email about your deliveries can each be switched off separately. We send no marketing email at all — there is no newsletter and no product-news list, and if that ever changes it will be opt-in with an unsubscribe link on every send. We will still send the small number of emails an account cannot work without — verifying your address, resetting your password.

Complain

Write to us first at [email protected]; we would rather fix it than be reported for it. If you are not satisfied, you can complain to the Office of the Privacy Commissioner of Canada, or to your provincial privacy commissioner.

Keeping it safe

• Every request between the app and our servers is encrypted in transit, and data is encrypted at rest by our host.
• Access rules live in the database itself, row by row, rather than in app code that could forget to ask. A driver cannot read a request they have not been given, no matter what the app sends.
• Attachments, proof photographs and avatars are in private storage, reachable only through short-lived signed links.
• Your sign-in session is held in the device’s secure hardware store — Keychain on iOS, Keystore on Android.
• Passwords are hashed and salted. Handover codes are generated by the server, never returned to the driver, and locked out after five wrong attempts.
• Staff access is limited to the people who need it, and every consequential action is logged.

No system is perfect. If a breach ever affects you and creates a real risk of significant harm, we will tell you and the Privacy Commissioner, as the law requires, and we will tell you what we know rather than what sounds best.

Children

Brizeet is for adults. You must be 18 or older to hold an account — a driver is doing paid work, and a customer is inviting a stranger to an address. We do not knowingly collect information from anyone under 18. If you believe a child has an account, tell us at [email protected] and we will remove it and its data.

Changes to this policy

When this policy changes, the date at the top changes with it. If a change materially affects what we collect or who sees it, we will tell you in the app or by email before it takes effect, and where the law requires it we will ask for your consent again rather than assume it. Older versions are available on request.

Contact us

Questions about this policy, or about what we hold on you, go to the same place a support question does. A real person reads it.

[email protected] Other ways to reach us

Brizeet, Ontario, Canada. Written for the two people who use the app, and meant to be read in full — it is not long on purpose.