Privacy policy
Last updated: 31 October 2026.
1. Who is responsible for your information
Bongo is run by Northern Peak Ventures Inc., a company incorporated under the Canada Business Corporations Act. This policy says what personal information Bongo collects, why, who sees it, and what you can do about it. It is written to meet Canada's Personal Information Protection and Electronic Documents Act (PIPEDA) and British Columbia's Personal Information Protection Act (PIPA).
Questions, requests and complaints: hello@bongomp.com, or by post at #1317-1500 W Georgia St, Vancouver, BC V6G 2Z6, Canada.
2. Nobody has an account
Buyers never sign in and never have an account or a password. An order is reached by the link in its receipt, and only by that link. The people who run an organization sign up and sign in to their own dashboard with an emailed link or code, and may also choose to set a password; that is the only sign-in on Bongo, and it is theirs, not yours. A password is optional and nobody has one until they set it. Bongo never stores the password itself, only a one-way scrambled form of it (a hash) that cannot be turned back into the password, and emails the account's own address whenever a password is set, changed, removed or reset. The people who run an organization can change the email address they sign in with: Bongo first emails a code to the new address to check it is theirs (Bongo staff also give the code from their authenticator), then changes it, emails the old address to say so, signs the account out on its other devices, and keeps a record of the change with both addresses. An invitation still open to the old address moves to the new one; the organization's contact email and payout address do not change. A link to reset a password works for a short while and only the newest one works, and Bongo keeps only a hash of it. To slow guessing, Bongo counts wrong passwords against a hash of the email address and of the network address for a short while, and records each password sign-in, and each wrong password tried on an existing account, against that account. Anyone can set up an organization: Bongo keeps the email address it was set up with, the name that person gave, and the organization's name and school, and tells its own staff about every new organization so they can check it is real. An email address typed into the sign-in form is kept too, so its sign-in email can be sent, even if it never goes on to set up or join an organization. Each sign-in is kept with the network address and the browser it came from. When an owner invites someone, Bongo keeps the address invited and when the invitation was sent, and emails the invitation; the owner can resend or cancel it. Someone who joins gives their name, if their account has none yet, and Bongo keeps it with their account: the organization's owner sees it on its list of members, and the organization's people see its first word beside each item that person marks collected. A member the owner removes is emailed to say so, can no longer sign in to the organization, and is told so if they open it again; the record of what they did stays. When an owner hands the organization to a member, the new owner is emailed, and asked to set the payout email again. Someone who signs in with the emailed code or link may choose "Keep me signed in for 30 days", ticked unless they untick it: that browser then stays signed in for 30 days from the last time it was used, Bongo keeps when the choice was made and when that sign-in was last used, and the browser keeps a second small cookie beside the sign-in cookie that holds nothing but that choice. Bongo also notes on each sign-in when it last proved, through a code or link sent to the person's email, that the person holds that inbox; asking for a payout, changing the payout email or handing the organization to a member asks for a fresh emailed code once that is 12 hours old. The dashboard keeps a sign-in cookie in the browser of whoever is signed in, and a couple of notes in that browser's own storage: when it last showed a new sale, so the next one can be announced, and any marks made at the table that have not reached Bongo yet, so none is lost on a weak connection. When someone sets up their first organization, the dashboard also sets a cookie in their browser for two minutes, holding only the new organization's id, so it can show that person a welcome once, and clears it as soon as it has read it. An organization's owner may add its colour and its Instagram handle to its profile; both are the organization's, shown on its own pages. The first time the owner of a newly set-up organization reaches the dashboard, Bongo asks three optional questions (what brings the organization to Bongo, what it wants to sell first, and roughly how big it is) and keeps the answers with the organization, to put what it chose first on its dashboard, together with when the questions and the short tour that follows were finished or skipped.
Designs. An organization's owner can ask Bongo for a design from their dashboard. What they send for it is kept: what they would like made, rough quantities, a budget and a date, their logo and other files, and later the sizes, any names and numbers to print, how it should reach them (a delivery address, where they give one) and their notes, with the name of whoever sent each step. Names and numbers to print can be other people's: the organization sends them, and is responsible for having their agreement. All of it is kept in the system Bongo uses to make orders, not in Bongo's own database, and Bongo's staff use it to make the mockup, the price and the order. The organization's owner sees it on the dashboard, and Bongo emails the owner when a design is ready to review. The organization's members do not see it.
3. What we collect when you buy from a storefront
When you order. Your first name, your last name, your email address, and your student number, or the fact that you ticked "Not a student". With them, what you ordered: the product, the colour, the size and the quantity, the price and tax at the time, the reference code, and when the order was placed.
Your card. You type your card into a form that belongs to Stripe, our payment processor, and the details go to Stripe, never to Bongo. Bongo keeps Stripe's reference for the payment and the amount Stripe charged, and nothing about the card itself: not the number, not the brand, not the last four digits.
Two cookies. Bongo sets one cookie for your cart on an organization's storefront, which holds what you have put in it, and one for a checkout you are in the middle of, so a second try after a declined card picks up the same order. Both are set for the one address you are on and are never shared with another site. There are no advertising cookies, no third-party analytics and no tracking across other websites. Your order page also keeps one small note in your browser's own storage, which is not a cookie and is never sent to Bongo: how far along your order was the last time you looked, so a step reached since then can be marked. It holds the order's id, never your link, your name or your email address.
Automatically. Standard server logs, which carry your network address, your browser and the pages you asked for, kept for security and troubleshooting. To slow abuse, Bongo counts checkout attempts against a hash of your network address and of your email address for a short while; the counter is not a record of who you are.
4. Why we collect it
- To take your payment and hold the goods for you while it goes through
- To send you your receipt, with the reference code and the pickup details, and to email you about that order: a change to the pickup details, a reminder to collect, or a refund
- To give the organization what it needs to hand you the right thing and to answer a refund request
- To keep the records Canadian tax law requires
- To detect and prevent fraud
Bongo does not sell your personal information and does not use it for marketing. Bongo emails you about your own order and about nothing else.
5. If you ask to be told when a size is back
A sold-out size offers to email you if more arrive. If you ask, Bongo stores your email address against that one size. When the organization restocks it you get one email, and only one, with a link that stops any further email about that size. Asking for several sizes means one email per size. If the size sells out again after that email and you ask again, you get one more email the next time it is back, and the link in the earlier email keeps working until that next email replaces it.
The organization sees how many people asked for each size, never their addresses. The addresses are never given to the organization, never exported and never used for anything else. Unsubscribing keeps the record that you unsubscribed, so the same address is not emailed again.
Asking is counted against a hash of your network address and of your email address for a short while, to slow abuse; the counter is not a record of who you are. The link in the email is made when the email is sent, works once, and Bongo keeps only a hash of it, so the link cannot be rebuilt from what is stored. A reply to the email goes to the organization's contact address where it has one, and to Bongo otherwise. If you unsubscribe and later ask again about the same size, nothing is stored and nothing is sent.
6. What the organization sees
The organization you bought from can see, for each of its own orders, the fields in this table and nothing else about you. Its owner can see every field; the members it adds to work the pickup table see the pickup list, which is built from the same fields. Bongo's own staff can see the same, to run the service and to pay the organization, and, when it pays the organization, staff read a statement of what each thing it sold has taken in, which names no buyer.
| What | Why the organization sees it |
|---|---|
| Your first name | To find your order at the pickup table |
| Your last name | To find your order at the pickup table |
| Your email address | To reach you about your order, and to fix a typo before a receipt goes astray |
| Your student number | A backup check of who you are at the table, never a gate |
| Whether you said you are not a student | So the table knows there is no number to ask for |
| The colour and size you chose | To hand you the right thing |
| The state of your order | Paid, collected, refund requested, refunded, disputed, charged back, so the table knows what is owed |
| The reason you gave when asking for a refund | The organization decides on the refund, so it reads your reason |
| The name of somebody who collected for you | Written down at the table when a friend collects on your behalf |
| Whether your bank is disputing the payment, the day it began, and the reason category the bank gave | The money for the order is held back while the bank decides, and the organization answers for the sale, so it is told what is happening and why |
Beside each order the organization sees its reference code and what was ordered, which are facts about the order rather than about you. It never sees your card or anything about it, never an order you placed with another organization, and never the name behind a payment that did not go through: an order that was never paid is on no list the organization can see.
7. When you pay for a name on a list
The list itself. An organization that makes a list gives Bongo the names on it, a tell-apart where two names are alike, a size where it already knows one, and an email address where it has one. Bongo did not ask you for any of that: it came from the organization, which is responsible for having your agreement to put your name on a list that the people it shares the link with can see. The list shows the names still to pay to anyone holding the link and the passcode, as the organization wrote them or, if it chose that, as initials with the tell-apart; tapping a name shows it in full on the payment page, so the person paying can confirm it is theirs. Beside a name it never shows an email address, a size, an amount, or whether somebody is in the middle of paying for it. A name comes off the list the moment it is paid for. The organization can hide a name from the list at any time, and if you write to hello@bongomp.com we will have yours hidden.
When you pay. Your email address, and the size you chose where the list has sizes. With them, what you paid for: the item, the name on the list you paid into, the price and tax at the time, the reference code, and when the pre-order was placed. Bongo asks you for nothing else: the name on the pre-order is the name you tapped.
Your card. You type your card into a form that belongs to Stripe, our payment processor, and the details go to Stripe, never to Bongo. Bongo keeps Stripe's reference for the payment and the amount Stripe charged, and nothing about the card itself: not the number, not the brand, not the last four digits.
Why. Bongo uses what it holds about you:
- To take your payment and hold the name for you while it goes through
- To send you your receipt, and to email you about that payment if it is moved to another name or refunded
- To give the organization what it needs to order and hand out the right thing
- To tell you where and when the items are handed out, once the organization says so, unless it chose to tell everyone itself
- To remind a name the organization gave an address for, before the due date
- To keep the records Canadian tax law requires
- To detect and prevent fraud
Bongo does not sell your personal information and does not use it for marketing.
Three cookies. Bongo sets one cookie when you type the passcode, so the list opens without it for the next 30 days in that browser; a changed passcode ends it early. It sets a second when you choose a name and go on to pay, which remembers the name you are paying for: for 10 minutes from then, then 15 minutes from the moment you tap pay, and it is cleared when the payment settles. It sets a third, a security cookie, when you open a list: it holds only a random number for that browser, for a year, so that wrong passcodes typed in it, and names chosen in it, are counted apart from everyone else on the same network, and a shared wifi does not lock out people who type the right passcode or choose their own name. It is used for nothing else and is never tied to your name, your email address or anything you pay for. All three are set for the one address you are on and are never shared with another site. There are no advertising cookies, no third-party analytics and no tracking across other websites. Your pre-order page also keeps one small note in your browser's own storage, which is not a cookie and is never sent to Bongo: how far along the pre-order was the last time you looked, so a step reached since then can be marked. Right after the passcode opens the list, the page keeps a second note, in that tab and for under a minute, so the list can be drawn fading in, and removes it as soon as it is read. When you choose a name and go on to pay, the page keeps a third note in that browser: the list's own code for that name and its place on the list, never the name itself. If that browser opens the list again within 15 minutes of your tap on pay and the name has come off it, the list there, and nowhere else, shows a row saying you're paid where the name was, once, and removes the note; otherwise the note is removed the next time the list is opened after that. None of the three holds your name or your email address.
Automatically. Standard server logs, which carry your network address, your browser and the pages you asked for, kept for security and troubleshooting. To slow guessing, Bongo records each passcode try against a hash of your network address, per list, and keeps those records, and counts wrong passcodes for a short while against a hash of the security cookie's number; a right passcode is never held against you. They are a count of tries, not a record of who you are, and the organization never sees them. Choosing a name is counted for a short while against a hash of the security cookie's number, and against a hash of your network address with a higher limit shared by everyone on it. Payment attempts and, where the organization allows it, adding a name are counted for a short while against a hash of your network address and, for a payment, of your email address. When a lot of wrong passcodes come from one network, Bongo's staff are alerted, naming the list and the organization, never the network address.
Reminders. Where the organization put an email address beside your name and set a due date, Bongo emails that address a reminder 3 days before the due date and again on the due date, in the morning, Vancouver time, and never after the date has passed. Each reminder names the organization, the item and the amount, never the passcode, and carries a link that stops any further reminder for that name. A list with no due date sends none, and a name that has been paid for gets none. On the due date the organization is emailed how many names are still to pay and which; it can already see both on its list. The reminder goes to a person who has bought nothing, which is why it goes only to an address the organization gave for a name it expects to pay, is about that one list, and carries the link that stops it.
Adding your own name. An organization can let people add their own name to its list. Where it has, a name you add is on the list like any other, with the tell-apart you give. Adding a name is counted against a hash of your network address for a short while, to slow abuse.
Asking to be added. Where an organization does not let people add their own name, you can ask it to add you from the list. You type your name and your email address; Bongo keeps both, with when you asked and whether the organization added you or dismissed your ask, and the organization sees your name and your email address on its list's page, as it would beside a name it had added, and is emailed your name. If it adds you, your name goes on the list with that address beside it, as if the organization had put it there, and Bongo emails you the link to pay, once; after that the address is used as the one beside any other name is (see Reminders). Asking is counted for a short while against a hash of your network address and per list, to slow abuse, and the address is never part of that count.
Handing out. Once the items have arrived, the organization says where and when it hands them out, and Bongo keeps where, when, the time it said so and whether it asked Bongo to email everyone. Unless it chose to tell everyone itself, Bongo emails where and when to the address you typed when you paid, with your reference code; for a name counted as in without a payment through Bongo, to the address the organization put beside that name, where there is one, and to nobody where there is none. Once the order has been placed, which happens automatically once everyone on the list is in and the list takes no more names (on a list people can add their own name to, after its due date), the organization ticks your name on its list when it hands you your item, and Bongo keeps the time your name was ticked. The organization can undo a tick until it marks the whole list handed out, and the ticks are fixed after that. Bongo releases what the list took in to the organization only once every name on it is ticked.
How long the list is kept. The list, with every name on it, is kept with the organization's payment records for as long as they are kept, because it is the record of who paid for what. A name the organization removes from its list stays in its records, marked removed, and is in the file the organization downloads. There is no control that deletes a list. If you want your name out of a list that is no longer taking payments, or out of an organization's records, write to hello@bongomp.com and we will remove it, subject to what must be kept by law.
8. What the organization sees about its list
The organization that made the list can see, for each name on it, the fields in this table and nothing else about the person. Its owner sees every field; the members it adds to its dashboard see none of the list, only how many names are on it and how many have paid. Bongo's own staff can see the same, to run the service and to pay the organization, and, when it pays the organization, staff read a statement of what each thing it sold has taken in, which names no buyer. Only Bongo's staff can mark a name as in without a payment through Bongo, with a reason the organization can read.
| What | Why the organization sees it |
|---|---|
| The name as it wrote it on the list | It wrote the list, and the name is how it knows who you are |
| The tell-apart beside a name | To tell two people of the same name apart |
| The email address it put beside your name | It gave the address, and it is where Bongo's reminders go and, for a name counted as in without a payment through Bongo, where Bongo says where and when the items are handed out |
| The email address you typed when you paid | To reach you about your payment, and to fix a typo before a receipt goes astray; shown on a paid name alone |
| The size | To order the right thing for you |
| The state of the name | Unpaid, paid, waived or removed, so it knows who is in |
| The reason a name was waived | Only Bongo's staff can waive a name, and they write down why |
| A note the organization wrote about a name | Its own working note, which it wrote |
| The reference code of your payment | To find your payment when you write about it |
| When you paid | To know when a name was paid for |
| When you were handed your item | It ticks your name when it hands you the item, so it knows who is still waiting for theirs |
| Whether your bank is disputing the payment, the day it began, and the reason category the bank gave | The money for the name is held back while the bank decides, and a dispute about a list is held against the organization that wrote it, so it is told what is happening and why |
Beside the list the organization sees how many names are paid for, waived and still to pay, how many items it has handed out once its order is placed, and what the list has taken in before tax, which are facts about the list rather than about you. It never sees your card or anything about it, never a payment on another organization's list, never who is in the middle of paying for a name, and never the address behind a payment that did not go through: a pre-order that was never paid is on no list the organization can see. It can download its list as a file carrying the name, the tell-apart, both email addresses, the size, the state, the day a name was paid for and the reference code, for every name, the removed ones included, and Bongo records every download.
9. What we collect when you pre-order on a countdown
When you pre-order. Your first name, your last name, your email address, and your student number, or the fact that you ticked "Not a student". With them, what you reserved: the item, the size, the price and tax at the time, the reference code, and when the pre-order was placed.
Your card, and the one thing Bongo keeps about it. You type your card into a form that belongs to Stripe, our payment processor, or choose Apple Pay or Google Pay, which hand Stripe a card from your wallet; either way the details go to Stripe, never to Bongo. A countdown charges nothing on the day you pre-order, so Stripe saves the card for the single charge that may come weeks later, and Bongo keeps Stripe's reference to the saved card, which is what lets that charge be made when the countdown ends. Bongo keeps nothing about the card itself: not the number, not the brand, not the last four digits. The organization never sees any of it either, and neither the saved card nor its reference is used for anything but the one charge this countdown is for.
When the card is charged. At the moment the countdown ends, and only if the organization's minimum is in by then; where the organization set no minimum, the countdown goes ahead whatever the number and the sentence you are shown says so. The email you get when you pre-order names the amount and the exact date and time, weeks in advance, and it is the notice: nothing is sent between the end of the countdown and the charge, because there is no gap between them. If the card does not go through you get one email with a link to a page where you can fix the card, which is either confirming the card you already saved or typing another; anything you type goes to Stripe the same way, and you have 24 hours from that first failure to use it.
When the saved card is let go. Bongo asks Stripe to let go of a pre-order's saved card as soon as it is certain no charge will ever be made on it: a countdown that ended under its minimum, a countdown the organization stopped, a pre-order you cancelled, and a pre-order cancelled because the card was never fixed in time. After that it cannot be charged again, and what is left with Bongo is the record that the pre-order existed and that nothing was taken. A card that was charged stays saved at Stripe, because a payment dispute can arrive months after the charge, and a refund when a countdown is withdrawn, and both are made against that same card. A card saved in the moment the countdown ended, whose pre-order was refused because the countdown had closed, is let go at once. A card Stripe saves when no pre-order is then placed with it at all, because the page lost its connection at that moment or was closed before the pre-order was placed, stays saved at Stripe with nothing at Bongo pointing to it, and it can never be charged, because Bongo only ever charges a card for a pre-order. The same is true of a card saved on the page that fixes a card when that page is closed before the card is used. When you fix a card by typing another, the card you type becomes your pre-order's saved card and the one it replaces is let go at once, and a card you type there that your pre-order does not take, because the pre-order was paid, cancelled or out of time first, is let go too.
When you cancel. Asking to cancel sends a link to the email address on your pre-order. To recognise the link when you use it, Bongo stores a hash of it, with when it was sent, when it stops working and whether it was used; the copy of the email Bongo keeps in order to send it carries the link itself, which stops working a short while after it is sent or as soon as it is used. A cancelled pre-order stays on record as cancelled with nothing taken, and its saved card is let go as above.
Why. Bongo uses what it holds about you:
- To save your card and to charge it once, when the countdown ends and the minimum is met
- To send you your confirmation with the amount and the date, a reminder while the countdown is still open and a message when a countdown with a minimum reaches it, your receipt when the card is charged, a message if the card does not go through or the item is not going ahead, the email saying your item is ready and the last day to collect, a reminder 2 days before that day if you have not collected, and a note if a refund you asked for lapsed because the organization did not decide in time
- To send you the link that confirms a cancellation you asked for, and a note once the pre-order is cancelled
- To give the organization what it needs to have the right thing made and to hand you yours
- To keep the records Canadian tax law requires
- To detect and prevent fraud
Bongo does not sell your personal information and does not use it for marketing. Bongo emails you about the countdowns you pre-ordered on and about nothing else.
Cookies. A countdown page sets no cookie of its own: nothing is held for you in advance, there is nothing to unlock, and your pre-order is reached by the link in its confirmation. Stripe's own card form sets what it needs to show the field and to spot fraud. There are no advertising cookies, no third-party analytics and no tracking across other websites. A countdown page does keep two small notes in your browser's own storage, which is not a cookie and is never sent to Bongo: that this browser has already seen the message saying the countdown's minimum is in, so it arrives with a little motion only once, and, on your pre-order page, how far along your pre-order was the last time you looked. Neither holds your name, your email address or anything about your card.
Automatically. Standard server logs, which carry your network address, your browser and the pages you asked for, kept for security and troubleshooting. To slow abuse, Bongo counts pre-order attempts against a hash of your network address and of your email address, and requests to cancel against the pre-order and a hash of your network address, for a short while; the counter is not a record of who you are.
10. What the organization sees about its countdown
While the countdown is running, and until your card is charged, the organization sees how many pre-orders are in and what they come to, and its owner also sees your first name, your last name, your email address and the size you chose, so the organization can reach you about your pre-order; its members do not. Once a card has been charged the organization can see, for that pre-order, the fields in this table and nothing else about you. Its owner can see every field; the members it adds to work the pickup table see what that table shows them, which is built from these fields apart from the reason you gave when asking for a refund, which only the owner reads. Bongo's own staff can see the same, to run the service and to pay the organization, and, when it pays the organization, staff read a statement of what each thing it sold has taken in, which names no buyer.
| What | Why the organization sees it |
|---|---|
| Your first name | To find your pre-order when the items are handed out |
| Your last name | To find your pre-order when the items are handed out |
| Your email address | To reach you about your pre-order, and to fix a typo before a receipt goes astray |
| Your student number | A backup check of who you are at the table, never a gate |
| Whether you said you are not a student | So the table knows there is no number to ask for |
| The size you chose | To have the right size made for you |
| The state of your pre-order | Charged, collected, not collected, refund requested, refunded, disputed, charged back, so the table knows what is owed |
| The reason you gave when asking for a refund | The organization decides on the refund, so it reads your reason |
| The name of somebody who collected for you | Written down at the table when a friend collects on your behalf |
| Whether your bank is disputing the payment, the day it began, and the reason category the bank gave | The money for the pre-order is held back while the bank decides, and the organization answers for the sale, so it is told what is happening and why |
Beside each pre-order the organization sees its reference code and what was reserved, which are facts about the pre-order rather than about you. It never sees your card or anything about it, never a pre-order you placed on another organization's countdown, and never a pre-order that was cancelled or whose card did not go through when it was charged: those are never named to it. The organization's owner can download the charged pre-orders as a file carrying these fields, the dispute column among them, the reference code and the day the card was charged, and Bongo records every download.
11. Who else we share it with
Bongo uses these service providers, and only to run Bongo:
| Provider | What they do | What they see |
|---|---|---|
| Stripe | Processes the payment | Your name, your email address, your card, the amount, and the product code that shows on your statement |
| Render | Hosts the site and its database | Everything Bongo stores about your order |
| Resend | Sends Bongo's email | Your name, your email address and the contents of each email sent to you |
| Cloudflare | Stores the photos organizations put on what they sell | Nothing about you |
| Vercel | Hosts the system Bongo uses to make orders | What an organization sends with a design request |
| Supabase | Stores design requests and the files sent with them | What an organization sends with a design request |
| Sentry | Tells Bongo when a page or the site breaks, so it can be fixed | Technical details of the error: what broke, where in the code, and the page's address with the private part of an order or list link, and anything after a "?", removed. Bongo sends it no cookies, no form contents and no account details, and has it set not to keep IP addresses |
Bongo also discloses personal information where the law requires it.
12. Where your information is stored, and what that means
Your personal information is stored and processed outside Canada, mostly in the United States. The site and its database run with Render in Oregon, payments are processed by Stripe, and email is sent through Resend. Design requests and their files are kept with Vercel and Supabase, and error reports go to Sentry in the United States.
This means your information is subject to the laws of the countries where those providers operate, and may be accessible to the courts, law enforcement and national security authorities there. Canadian privacy law requires us to tell you this, and you should know it before you give us your details.
13. How long we keep it
Order records, which is your name, your email address, what you ordered and the payment records, are kept for as long as Canadian tax and business record law requires, generally six years from the end of the tax year they belong to.
The record of every change to an organization's stock, of every movement of money and of every change an organization makes to an order is written once and never edited; the record of a payment attempt is written before the payment is asked for and records its outcome once, and is never deleted.
An address you gave to be told about a restock is kept, marked as unsubscribed once you unsubscribe, so the same address is not emailed again about that size. Ask us to remove it and we will, subject to what must be kept by law.
An ask to be added is kept as long as the names it asked to join are.
A design request is kept until the organization deletes it, which it can do on its dashboard until its order is made; once it is an order, it is kept with the order's records.
Stripe sends Bongo a message about each payment, refund and bank dispute, which carries the name, email address and billing details given with the payment. Bongo keeps each message whole for 30 days after it has dealt with it, then deletes its contents and keeps only a note that it arrived, what kind of message it was and when.
Server logs are kept for a shorter period and then deleted. Where personal information is no longer needed and there is no law requiring it to be kept, it is deleted or anonymised.
14. Your rights
Under PIPEDA and BC PIPA you can:
- Ask what Bongo holds about you and get a copy
- Correct anything inaccurate, including a mistyped email address on an order, through the organization or through us
- Withdraw consent and ask for your information to be deleted, subject to what must be kept by law
- Complain to us and, if you are not satisfied, to the Office of the Privacy Commissioner of Canada or the Office of the Information and Privacy Commissioner for British Columbia
Email hello@bongomp.com and you will have an answer within 30 days.
15. Keeping it secure
The application connects to its database with an account that cannot delete the stock ledger, the money ledger, the record of payment attempts or the audit trail, and cannot edit any of them except to record a payment attempt's outcome, once. Card details never reach Bongo. All traffic to Bongo is encrypted. Access to production data is limited to the smallest number of people needed to run the service.
No system is perfectly secure. If a breach affects you and creates a real risk of significant harm, Bongo will notify you and the Privacy Commissioner as the law requires.
16. Changes
This policy may change. The current version is always at this address, with the date it last changed at the top.
17. Contact
Northern Peak Ventures Inc., #1317-1500 W Georgia St, Vancouver, BC V6G 2Z6, Canada. Email hello@bongomp.com: it is a monitored inbox and the fastest way to reach a person.