Privacy Policy
This policy explains what information the Bricked app for Android and iOS and the website getbricked.app collect, why, where it goes, and the choices you have. Bricked is provided by Da Zhou, an individual based in Toronto, Ontario, Canada ("Bricked", "we", "us").
The short version
- Your blocked apps, schedules, usage, stats and house stay on your phone. We never receive them.
- If you sign in and turn on accountability emails, we store your name and email address, and your contact's email address. We use them only to send the alerts you asked for.
- No ads, no analytics, no tracking, and we never sell or rent your information.
- You can delete your account and its data from inside the app at any time.
1. Information that stays on your device
Most of what Bricked does happens on your phone and is never sent to us or anyone else. This includes:
- the list of apps installed on your phone, and which ones you restrict or group;
- your blocks, schedules, daily limits and timers;
- app usage time and your focus statistics;
- your house, village and game progress;
- your settings.
On Android, Bricked asks for these permissions to do its job:
- Accessibility service: lets Bricked notice which app is on screen so it can cover a blocked app with the block screen. Bricked does not read, record or send what you type or what appears inside other apps.
- Usage access: lets Bricked count how long you use each app, for daily limits and your stats.
- Notifications, and starting at boot: so blocks keep working and Bricked can tell you when a block starts or ends.
On iPhone, Bricked uses Apple's Screen Time framework, with your permission, to block apps and measure usage. Apple doesn't tell Bricked which apps you have or use: Bricked works with anonymous tokens that only your phone can turn back into app names, and the usage figures Bricked shows you stay inside Apple's protected area on the device.
If you uninstall Bricked, your phone deletes this on-device information. It may be included in your phone's own backups if you have those turned on; those backups are handled by Google or Apple under your account with them, not by us.
2. Information we collect if you use accountability emails
Accountability emails are optional. If you never sign in, we collect nothing about you. If you do sign in and turn them on, we handle the following:
| What | Why | How long we keep it |
|---|---|---|
| Your email address, and your name if you sign in with Google | To create your account, sign you in, and show your contact who an alert is from. Alerts use your address as the reply address so your contact can answer you directly. | Until you delete your account. |
| A one-time sign-in code, if you sign in by email | To confirm the address is yours. | Stored only in scrambled (hashed) form, and deleted once used or after 15 minutes. |
| Your accountability contact's email address, and whether they agreed | To ask your contact for permission, and then to send them your alerts. | Until you remove them or delete your account. If your contact declines or unsubscribes, see section 3. |
| The content of each alert: which app, group or block you overrode or paused, the time, and any reason you typed | To send the alert to your contact. | We do not keep alert content after sending. We keep only the date and time each alert was sent, to enforce a daily limit on alerts, for 30 days. |
| Technical data such as IP address, device type and sign-in times | Processed by Google to run sign-in and protect accounts against abuse. | As set out by Google (see section 4). |
Alerts are always sent from Bricked's own address (for example, alerts@getbricked.app). Bricked never asks for, sees or stores your email password.
3. If someone named you as their accountability contact
If a Bricked user enters your email address as their contact, we send you one email asking whether you agree to receive their alerts. Until you agree, you won't get any alerts. Every email we send includes a link to stop receiving them.
If you decline or unsubscribe, we keep a record that your address must not be emailed for that user, so we can honour your choice. You can ask us to delete that record at any time using the contact details in section 9. Deleting it means the user could invite you again.
4. Who processes the information
We use a small number of service providers to run the accountability feature and this website. They process information only on our behalf and under their data protection terms:
- Google Firebase (Google LLC / Google Ireland Ltd): sign-in, the database, the server program that sends alerts, and hosting of this website. The database and server program run in Google Cloud's Toronto region in Canada; sign-in services may process data in the United States and other countries where Google operates. Firebase privacy information.
- Resend (Resend, Inc.): delivers our emails. Email addresses and message content pass through Resend's servers in the United States, and Resend keeps delivery records for a limited period under its own policy. Resend privacy policy.
We don't share your information with anyone else, except if we are required to by law, or to protect the rights and safety of people using Bricked. If Bricked were ever sold or transferred, we would tell you in advance, and this policy would continue to apply to your information.
5. International transfers
Bricked is run from Canada and its database is in Canada. Some processing by Google and Resend takes place in the United States. If you are in the European Economic Area, the United Kingdom or Switzerland, these transfers are protected by the safeguards in our providers' data processing terms, such as the European Commission's Standard Contractual Clauses and, where they apply, the EU-U.S. Data Privacy Framework and its UK and Swiss extensions. Information stored or processed in another country may be accessible to that country's courts and authorities under its laws.
6. Legal bases (EEA and UK users)
- Contract: we need your email address, your contact's address and the alert content to provide the accountability feature you turned on.
- Consent: your contact only receives alerts after agreeing, and can withdraw that agreement at any time.
- Legitimate interests: keeping accounts secure, preventing abuse (such as the daily alert limit), and remembering who asked not to be emailed.
7. Your choices and rights
- Delete your account in the app under Setup. This deletes your account, your contact entry and your alert records straight away. Copies in our providers' short-term systems are cleared within 30 days.
- Turn off accountability emails or remove your contact in the app at any time.
- Wherever you live, you can ask us to access, correct, delete or export your information, or object to how we use it, by contacting us (section 9). We'll reply within 30 days.
- If you are in the EEA or UK you can also complain to your local data protection authority. In Canada, you can contact the Office of the Privacy Commissioner of Canada, or the Commission d'accès à l'information if you are in Québec. We'd appreciate the chance to sort out your concern first.
8. Security, children, and this website
Security. Information is encrypted in transit and at rest by our providers. Database rules let each person read and change only their own account. No system is perfectly secure; if a breach affects your information and creates a real risk of harm, we will notify you and the relevant authorities as the law requires.
Children. Accounts are for people aged 16 or over. Bricked's on-device features don't collect anything, but we don't knowingly create accounts for younger children. If you believe a child under 16 has an account, contact us and we'll delete it.
This website. getbricked.app uses no cookies, analytics or trackers, and loads nothing from other sites. Like any web host, Firebase Hosting records basic request logs (such as IP address and browser type) to deliver and protect the site.
9. Contact
Da Zhou is responsible for your information and for how Bricked handles it. For any question or request, email privacy@getbricked.app.
10. Changes to this policy
If we change this policy, we'll update the date at the top. If a change affects how we use information you've already given us, we'll tell you in the app or by email before it takes effect.