Privacy policy

bricks is a place to log what you do and share it with people you choose. We collect what the app needs to work, and this page tries to list all of it rather than the flattering half. We don't sell your data and there are no ads. You can delete everything, for real, from Settings.

• Your email address, and a password if you use one
• Your username, display name, bio and profile photo
• Your date of birth, if you choose to add one. It is optional, kept private, and used for birthdays
• Your home city and the interests you pick during onboarding
• The bricks you log: titles, ratings, your highlight, notes, photos and their captions, who you were with, and, for places, the venue and its coordinates
• Private thoughts on a brick, which only you can ever read
• Your lists and collections
• Direct messages you send
• Feedback and any screenshot you attach to it

• Who you follow, who follows you, your close friends and anyone you block
• Which screens you open and which actions you take, tied to your account
• Crash reports when something breaks: the error, the screen you were on, the app build, your device and browser, and your account id
• Your device type and OS version
• A push notification token, if you turn notifications on
• Sign-in records, including the IP address the request came from

If you join the waitlist on joinbricksapp.com, we store the email address you give us, the date you joined, and where you came from, meaning the link or site that first brought you to joinbricksapp.com (for example Instagram, or a friend's link). If you answer "Where are you?" after joining, we also store the city you give us, and nothing more precise. We use it to send you one email confirming you're on the list, to tell you when you can join bricks, to decide who gets in first, and to learn which links work. It is stored with Supabase, like everything else on this page. To be taken off the list, email kohav@joinbricksapp.com.

bricks asks for your location in one place only. When you tap "Find me" while logging somewhere, the app asks your device for your current position and uses it to show nearby places. That position is sent to Google Places to run the search. We don't store it, and we never ask for your location in the background.

If you don't tap "Find me", place search is biased toward places you have already logged, using your own history. Where that isn't available, a coarse estimate of your region may be derived from your network address.

Privacy comes from your account, not from each brick. On a public account, your finished bricks can be seen by anyone signed in, and appear on your public profile page. On a private account, they can be seen only by people you are mutually connected to.

Saved-for-later is the exception on both: something you mean to do is only ever shown to friends, never to strangers, even on a public account.

Photos are served only to people allowed to see the brick they belong to. Every image request is checked at the moment it is made, so blocking someone, making your account private or deleting a brick takes their access away immediately.

A share link is different and deliberate: it opens exactly the one brick or one collection it was made for, to anyone holding it, until you revoke it.

Blocking someone hides your profile, bricks, lists, collections and photos from them, and stops them contacting you.

Everything written in bricks (brick text, comments, direct messages, profile fields, list and collection names) is checked automatically as it is saved, against a list of terms we do not allow. Anything that matches is refused rather than published. No human reads your messages as part of this, and the check happens at the moment you press save.

Reported content is reviewed by a person. See the Terms for how reporting and blocking work.

These companies handle some of your data because the app needs them to:

• Supabase: our database, file storage, sign-in and server functions. Everything you give us is stored there
• Google Places: restaurant and place search. Receives your search text, and your coordinates if you tapped "Find me"
• TMDB, OMDb, Open Library and Apple's iTunes catalogue: film, TV, book and podcast search. They receive what you type into search
• Resend: the emails we send you, such as confirming your address or resetting your password. Receives your email address
• Cloudflare: serves the web app, and may be used for a coarse regional estimate as described above. On joinbricksapp.com, Cloudflare Web Analytics may count visits. It uses no cookies and doesn't identify you

None of them are sent your data for advertising, and we don't sell it to anyone. bricks does not track you across other apps or websites.

We keep your data while your account exists. Deleting your account from Settings removes your profile, bricks, photos, lists, messages and connections. It is not a flag on a row we keep: the data and the files go.

Two things survive, and neither identifies you: aggregate counts that never name an account, and moderation records of content that was reported, which we keep so the same problem can't simply be repeated.

Messages you have already sent remain visible to the person you sent them to, in the same way an email you have sent does.

• Edit or delete any brick, list or photo
• Make your account private, or public again
• Block anyone, and revoke any share link you have made
• Turn notifications off
• Delete your account and everything in it, from Settings
• Ask us for a copy of your data by email

You must be 18 or older to create a bricks account. We ask you to confirm that when you sign up, and we record that you confirmed it.

Adding your date of birth is separate and optional. It lives in Settings, it is only used for birthdays, and a date that would make you under 18 is refused outright. If we learn an account belongs to someone who isn't old enough, we remove it.

We don't use advertising cookies and there are no third-party trackers. The app keeps a sign-in token and some of your own data on your device so it opens quickly and works offline. The website keeps one note on your device: which link first brought you there, which is only sent to us if you join the waitlist.

If this page changes in a way that affects you, we'll say so in the app rather than quietly updating the date at the top.

Privacy questions, or a request for your data: kohav@joinbricksapp.com. A person reads that address.