Skip to content

Privacy policy

BFarah is a private photo-sharing service for celebrations. This page explains, in plain words, what we collect, why, who can see it, how long we keep it and what you can ask us.

Last updated: October 2026

Who we are

BFarah is operated by Essa Farah and Bshara Andrawes (“we”). For anything about your data, write to [email protected].

What we collect and why

It depends on how you use the service.

  • Guests: the name you type when you join (shown to the hosts next to your moments and in their downloads; never shown to other guests), the time you joined and the time of your last upload, the photos and videos you upload, the time each one was taken (read from the file, so the album can be sorted), the event you joined, and whether the hosts blocked you.
  • Voice messages: if the hosts turn the feature on, you can record a short voice message for them. It is stored like a photo, cleaned of hidden data, heard only by the hosts, and you can delete it yourself.
  • Hosts: your email address (to sign you in with a link and to send you notices), the name and date of your celebration, the names and settings of its events, its PIN (stored only as a hash, never readable), and a history of what was done in the celebration (approvals, deletions, blocks, settings changes, by whom and when).
  • People who send us the inquiry form: the name, phone number, optional email, event details and message you enter. They are emailed to us and are not stored in our database.
  • To limit abuse, we keep a keyed hash of your IP address for one day (wrong PIN attempts, upload starts, inquiry submissions), never the address itself. Error reports go to our monitoring service without photos, names, cookies or web-address parameters. Our hosting providers keep their own connection logs, which we do not control.

Photos and the data inside them

Camera files carry hidden data: where a photo was taken, the camera model, the exact time. The copies shown in the album and to anyone other than the hosts have all of it removed; we read only the capture time, to sort the album. The original file, with everything inside it, is kept for the hosts alone: they can download it one by one or as a zip, where files are named with the date, the guest’s name and an id.

Who sees what

  • The hosts of the celebration (and anyone they add as a co-host) see everything uploaded to it, including moments marked “only the hosts”, together with the name of the guest who uploaded each one.
  • Other guests see your moments only according to the visibility the hosts chose for the event (open, after approval, private, or revealed at a set time) and your own choice for each moment (everyone, or only the hosts). They never see your name. The capture time is shown with each moment to anyone who may see it.
  • People with the family view link see what guests see, read-only, for as long as the hosts keep the link on.
  • No one else. Event pages are hidden from search engines. The link to an event cannot be guessed, but anyone who has it (and the PIN, if one is set) can join, so hosts should share it with care.

How long we keep it

  • Photos and videos stay until the storage date agreed with the hosts for their celebration. The owner is emailed 14 days before that date and can download everything. After it, a nightly job deletes every photo, video and download zip of the celebration, and the celebration is archived.
  • A moment deleted by a guest or a host can be restored by the hosts for 7 days; after that a nightly job removes it from storage for good. Files we refuse (wrong type, too large) are deleted at once.
  • Download zips are available for 7 days.
  • Guest names, the celebration’s events and settings, and its history remain after the storage date until we delete the celebration. There is no self-service button for that yet: hosts, or a guest who wants their record gone, write to us and we delete it.
  • Host accounts (email) are kept until you ask us to delete them. Sign-in links work for 15 minutes; sessions last 30 days.
  • Hashed IP addresses: one day.
  • A copy of the database is saved every night and kept for 30 days, so a deleted record can remain in those backups for up to 30 days. Photos and videos are not part of these backups.
  • On your phone: files waiting to upload are kept by your browser for up to 24 hours so an interrupted upload can resume, and the upload page (with your name on it) is kept for offline use. Your browser clears both; nothing is sent to us.

Your rights and requests

  • Guests: you can delete any of your own moments at any time from the album, and change whether other guests may see each one.
  • Hosts: you can hide or delete anything in your celebration, block a guest, and download all originals.
  • Anyone: you can ask us what we hold about you, ask us to correct it, or ask us to delete it, by writing to [email protected]. Tell us the event link or the celebration so we can find it. We answer by email.
  • If you appear in a photo you do not want kept, ask the hosts or write to us with the event link and a description of the photo; we look into it and can remove the photo.

Who else handles the data

We use a few providers to run the service. They process data on our behalf; we never sell data, and we use no analytics or advertising services.

  • Cloudflare R2 (European Union) stores the photos, videos, download zips and the nightly database backups. Your phone uploads to it and downloads from it directly, through links that expire after 15 minutes.
  • Railway hosts the website, the database and the processing of uploads.
  • Resend (Ireland) delivers our emails: sign-in links, notices to hosts, and the inquiry form.
  • Sentry (European Union) receives error reports, without photos, names, cookies or web-address parameters.
  • Cloudflare also provides the domain and sits in front of the website, so page requests pass through it. Photos and videos do not; they go straight to the storage.

If we ever add a feature that sends photos to an artificial-intelligence provider, it will be clearly disclosed, switched on only by the hosts, and limited to the photos they select.

Cookies and browser storage

  • A cookie per event that remembers you joined it, holding only your guest id and the event id (kept for up to 90 days).
  • A cookie that remembers your language (one year).
  • For hosts, sign-in session cookies.
  • On the upload page, your browser keeps files waiting to upload for up to 24 hours, as described above.

There are no advertising or tracking cookies.

How we protect it

Everything travels over HTTPS. Photos and videos sit in private storage and are reached only through links that expire after 15 minutes; only the hosts ever get a link to an original. Event PINs are stored as hashes, guest cookies are signed, and every request is checked against who may see what. Limits on PIN attempts and uploads slow down abuse, and the database is backed up every night. No service can promise perfect security; if you notice a problem, write to us and we will act on it.

Photos of other people and of children

Guests upload photos of people at the celebration, including children. The hosts are responsible for telling their guests that photos are being collected and for removing anything a person, or a child’s parent or guardian, does not want shared. If that is you, ask the hosts or write to us; we can remove a photo.

Changes and contact

If this policy changes in a way that matters, hosts are told by email and the date at the top of this page changes. Questions, requests and complaints: [email protected].

Terms of service