Privacy and Cookies
Last updated: 20 October 2026
This English translation is provided for information only. The Turkish version is the binding text; if the two differ, the Turkish text prevails.
In short: we do not use advertising or tracking cookies. The few cookies we use remember your sign-in and the choices you make. Photos are kept in storage that is not public and open only through short-lived, signed links. Albums do not appear in search engines.
What this page covers
In plain language, how your data is protected when you use Biranda and what is stored in your browser. The details of which data we process, on what legal basis, and your rights are in the Data Protection Notice.
What we collect and what we don't
- Couples: an email address to sign in, event details and billing details when ordering. We no longer accept physical product orders; shipping details for any past orders are preserved as part of the relevant records.
- Guests who upload photos: only the name they enter, their photos and an optional note. We do not ask for an account, a phone number or an email address.
- Invited guests: the name and contact details entered by the couple, and the reply the guest gives.
We do not sell your data, use it for advertising or share it with ad networks. We do not use photos from albums for promotion or to train AI models. We do not use facial recognition.
How photos are protected
- Private storage: photos and videos are kept in storage that is not public. They cannot be reached through a direct address.
- Signed, short-lived links: a time-limited link is created each time a photo is viewed. For small previews this is 24 hours; for large images, videos and downloads, 1 hour. An expired link no longer works.
- Unguessable address: the album address carries a random suffix; attempts to find albums by scanning addresses are limited.
- Optional PIN: the couple can protect the album with a PIN. Wrong PIN attempts are limited. The upload page is always open, regardless of the PIN.
- Approval: if the couple wants, photos appear in the album only after they approve them.
- Hidden from search engines: the upload, album and invitation pages tell search engines not to index them (noindex). Marketing visit statistics tools do not run on these pages. Optional first-party technical performance samples are described separately below.
- No location data: GPS data in photos and videos is removed before the file leaves the device. HEIC files from a computer are converted on the server into JPEGs without location data.
- IP addresses are not stored: to prevent abuse we keep only a salted hash of the IP address; the IP address cannot be recovered from it.
- Encrypted connection: all traffic on the site is encrypted with HTTPS (TLS).
Albums may include photos of children or of people who did not upload them. Anyone who wants a photo removed can write to the couple or to us.
Who sees what
- The couple: sees all photos uploaded to their event (including those awaiting approval), guest names and notes, the guest list and the replies. They cannot access another event's data.
- Guests: if the album is open, see only approved photos; if there is a PIN, they enter it first. Invited guests do not see each other's replies.
- Partner photographer or venue: cannot access your album or guest list. For an order placed with their code, only the order date and amount may be shared, to calculate commission.
- Our team: accesses albums only when a support request, a complaint or security requires it, with an authorised account.
Mobile app
- Notifications: if you allow them, we store your device's notification token, only to send notifications about your own event (new photos, RSVP replies, payment). You can turn them off in Settings or in your phone's settings.
- Contacts: when adding guests, your contacts are read only on your phone. Only the name, phone and email of the people you choose reach the server.
- Photos and camera: only the photos you choose are uploaded; write permission is requested to save the album to Photos.
- In-app purchases: payment is taken by Apple or Google; we do not see card details. To verify the purchase, the transaction record (product, transaction number, amount) is matched with your account; we do this through our service provider RevenueCat, which is based abroad.
- No tracking: the app has no advertising ID, tracking or analytics tool.
Browser storage
We keep some information in your browser's own storage (localStorage), without sending it to the server:
| What | Why |
|---|---|
| Guest name | So your name is filled in next time you upload. |
| Upload session | A random ID; keeps your uploads together and is also sent to the server for abuse limits. Renewed if unused for 12 hours. |
| Unfinished large upload | If the connection drops, the upload resumes where it left off when you choose the same file again. Deleted when the upload finishes. |
| Invitation message template | So the WhatsApp/SMS invitation text you edited on the dashboard is ready next time. |
You can clear this information at any time by deleting your browser's site data.
Visit statistics
To see which of our marketing pages are visited and how fast they load, we use Vercel Web Analytics and Speed Insights (we may also use Plausible). These tools use no cookies, do not store your IP address and collect no personal data; they produce only aggregate numbers such as the page path (without the query part), the referring site, country, device type and page speed. They do not run on the dashboard, upload, album or invitation pages.
Technical performance samples
Separate from visit and marketing statistics, first-party technical performance measurement is disabled by default. If the operator enables it, the website, customer dashboard and guest pages send LCP, INP and CLS samples about loading, responsiveness and layout shifts to our own server. Admin pages and the store app shell are excluded.
A sample contains the metric name and value, the general page group when the document opened (such as /a/[event] or /panel), the initial mobile/desktop category, and a random key for that metric in that document. The key only keeps updated values of the same metric as one sample; each metric gets a separate key held only in the open document’s memory. It contains no account or event identifier, person's name, contact details, full URL or query string; it creates no tracking cookie or persistent browser identifier. The server adds the environment and recording time. Samples are retained for 28 days, then deleted by scheduled cleanup. An IP hash is used separately in short-lived abuse rate-limit records and is not written into performance samples.
Anonymous page-view counts
On public marketing pages we keep only daily aggregate view counts on our own server. Each counter contains the Europe/Nicosia calendar day, a predefined page group, coarse source and campaign-medium categories, and a mobile/tablet/desktop category. Opening a page again may increase the count; it is not a unique-visitor count and is not matched to accounts that register or pay. Aggregate counts are retained; historical visits are not reconstructed.
This measurement creates no cookie, browser storage, persistent visitor ID or fingerprint. Counters contain no raw IP address, full page URL or query string, full referring URL or domain, arbitrary campaign name, location, email, account or event ID. The browser reduces the source to a controlled category. The existing abuse-prevention mechanism uses a separate IP-hash rate counter; that hash is not joined to aggregate measurement. Browsers with DNT or Global Privacy Control, the store app, private customer/admin, sign-in and guest pages are excluded. Advertising consent and Meta Pixel preferences remain separate.
Deletion and retention
Album files are kept for the purchased storage period; when it ends they are frozen for 30 days and then deleted. The couple can choose "Delete all data" on the dashboard; after 7 days the files are deleted and personal details are anonymised. Details are in the Data Protection Notice, and purchase terms in the Distance Sales Agreement.
Contact
For any question or request about privacy, write to merhaba@biranda.net. Our postal address for written applications: Fuse Digital Advertising, [Adres — bekliyor].