Effective date: [DATE]
Version: Beta
MemoryLane is a shared photo album for events: people join an event with an invite code, share photos to it, and save each other's photos to their own devices. This policy explains what we collect, why, who can see it, and how you can delete it.
MemoryLane is currently in public beta. Features and this policy may change; we will update the effective date and, for material changes, tell you in the app.
1. Who we are
MemoryLane is run by [YOUR FULL LEGAL NAME], a private individual, [POSTAL ADDRESS] ("we", "us"). I am the controller responsible for your personal data.
Contact for anything privacy-related: [PRIVACY EMAIL, e.g. privacy@kona.works].
2. What we collect
Account information — when you sign in with Apple or Google we receive:
- a unique account identifier from Apple or Google,
- your email address, if the provider has verified it. With Sign in with Apple you can choose "Hide My Email", in which case we only receive an Apple relay address,
- your name, and a profile picture link (Google only).
You can change your display name in the app. You can optionally upload a profile photo.
Photos you share — the photos you upload to an event, plus their capture time and file size.
- The original file is stored as uploaded and may contain embedded metadata (for example the camera model or, if your camera recorded it, the location where it was taken). Event participants can download originals at full resolution.
- The smaller preview images shown in the app have this metadata removed.
Event information — events you create or join:
- the event name, dates and settings, invite code, your role (organizer or participant), and join requests;
- for organizers who use pre-approval: the email addresses they enter for people who may join without approval.
Device and sync information
- a random identifier created when the app is installed (not your device's hardware ID or advertising ID),
- for photos you save from MemoryLane to your photo library (or upload from it): the library's internal reference to that photo, and whether you kept, updated or deleted your copy. This is how the app shows each photo's sync status and asks before removing anything from your library.
Face data — only if you switch on "Find photos of me" (see §5). This is a numerical description of your face (a "face template") made from your profile photo, plus a list of the event photos you appear in.
Reports and moderation — reports you file about a photo (reason and optional details), and the result of our automated safety check on each uploaded photo (see §4).
Crash reports and diagnostics — when the app or our servers run into an error, a report is sent to our error-monitoring provider, Sentry (see §6). A report contains:
- what went wrong (error message, the code location, and the steps leading up to it),
- your device model, operating system version and app version,
- your MemoryLane account ID, so we can investigate a problem you report. Not your name, email or photos.
We set Sentry up not to store IP addresses, and not to record screens or photos. DECIDE: confirm these settings when integrating (sendDefaultPii: false, "Prevent Storing of IP Addresses" on, no session replay), or change this paragraph.
Server logs — our servers record requests (time, requested address, IP address, response status) to keep the service running and secure.
What we do not collect:
- no advertising identifiers, no advertising SDKs;
- no usage analytics or behavioural profiling. Crash reports are used only to find and fix errors;
- no tracking across other apps or websites.
We do not sell or share personal data for advertising.
Your photo library stays on your device. The app reads your photo library only to let you pick photos and to suggest photos taken during an event. That matching happens on your device. Nothing leaves your device unless you choose to share it.
3. Why we use it, and on what legal basis
| Purpose | Legal basis (where the law requires one) |
|---|---|
| Providing the service: your account, events, sharing photos with participants, keeping your device's copies in sync | Performance of our contract with you |
| Safety and moderation: detecting and acting on illegal or harmful content, handling reports, enforcing the Terms | Legitimate interests (a safe service), legal obligations |
| Crash reports, security and reliability: fixing errors, preventing abuse, keeping backups | Legitimate interests (a working, secure service) |
| "Find photos of me" | Your explicit consent, which you can withdraw at any time |
| Communicating with you about your account or the beta | Performance of contract, legitimate interests |
4. Automated safety check
Every uploaded photo is analysed by Google Cloud Vision ("SafeSearch") before other participants can see it. The check estimates whether the photo contains explicit or violent content.
- A photo the check flags is hidden from other participants and reviewed by a person.
- The result is stored with the photo; Google does not keep the photo for its own purposes.
- We may report content that appears to be child sexual abuse material to the relevant authorities, as required by law.
This check does not identify people.
5. "Find photos of me" (optional face matching)
This feature is off unless you switch it on in Settings → Profile photo. The app asks for your consent before it starts.
What it does. When it's on, MemoryLane finds the photos you appear in, in the events you're part of, so you can filter an event to photos with you.
How it works
- When you switch it on, we create a face template from your profile photo. A face template is a set of numbers that describes your face. It cannot be turned back into a picture.
- When a photo is uploaded to an event you're in, faces in it are converted to templates in the same way. Each one is compared with the templates of event participants who have switched the feature on.
- When a face matches, we store only that it matched: which photo, which person, and a similarity score.
- Templates made from faces in event photos are discarded immediately after the comparison. They are never stored, whether or not they matched. We store no face data about anyone who has not switched this feature on.
- When you switch it on (or join a new event), photos already in your events are scanned once in the same way.
- The analysis runs on our own servers (Google Cloud, Singapore), using open-source models. Face data is not sent to any other company.
Who sees the results. Only you. Nobody else, including event organizers, can see which photos you are in, or whether you use the feature. Matching is automatic and can be wrong: it may miss photos of you or include someone else.
How long we keep it. Your face template and matches are deleted:
- immediately when you switch the feature off,
- when you remove or change your profile photo (changing it creates a new template),
- when you delete your account,
- and at the latest [3 years] after your last use of MemoryLane. DECIDE: no job enforces this yet. BIPA requires a maximum retention period. Either build an inactivity sweep before V1.0, or rely on the beta being shorter and do it by hand.
We never sell, lease or trade face data, and never use it for any other purpose.
Biometric data. Face templates are biometric data under many privacy laws (for example the GDPR, or US state laws such as Illinois' BIPA). The retention rules above are our published retention schedule for this data. By switching the feature on, you give your explicit (written, in-app) consent to this processing. You can withdraw that consent at any time by switching it off. Withdrawing consent does not affect matching already done before.
6. Who can see your information
- Participants of an event see the photos shared to it, and the uploader's display name and profile picture. Exception: if the organizer has made the event anonymous, participants see "A participant" instead of your name.
- Organizers always see participants' identities, join requests, and which photos have been reported. Organizers never see who reported a photo.
- Any signed-in user with the invite code sees the event's name, dates and cover picture, and the organizer's name and profile picture, before joining. This applies even to anonymous events.
- Service providers who process data for us under contract:
- Google Cloud (servers, database, file storage, the safety check, face matching), located in Singapore;
- Sentry (Functional Software, Inc.) for crash reports and error monitoring, with data stored in [the EU (Germany) / the US];
- Apple and Google for sign-in;
- Apple TestFlight for distributing the beta. Apple collects some tester and crash information under its own privacy policy.
- Authorities, when the law requires it or to protect people's safety.
7. Where your data is stored
Your data is stored on Google Cloud servers in Singapore. Crash reports are stored by Sentry in [the EU / the US]. Our providers may process data in other countries under their own safeguards. If you are in a region with transfer rules (for example the EU/UK), we rely on the providers' standard contractual clauses.
8. How long we keep it
- Your account: until you delete it.
- Photos and events: events are designed to expire 30 days after the event ends. At that point the event is archived and its photos are deleted from our storage. DECIDE: the automatic expiry job is not built yet. Until it is, either write "during the beta, expired events are cleaned up manually within [N] days", or build the job before publishing.
- A photo you remove disappears from the event immediately.
- A deleted event is removed from the app immediately for everyone. DECIDE: the stored files of a deleted event are not purged automatically yet. State the manual window, e.g. "files are deleted from our storage within [N] days".
- Face data: see §5.
- Copies others have saved: photos that participants saved to their own devices are in their photo libraries, which we cannot access or delete. When you remove a photo, people who saved it are asked whether to delete their copy. They decide.
- Crash reports: [90] days.
- Server logs: about 30 days.
- Database backups: up to [7] days. After that, deleted data is gone from backups as well.
9. Deleting your account
You can delete your account at any time in Settings → Delete account. Deleting your account:
- removes your name, email, sign-in identifiers and profile photo;
- deletes your face data, if you used "Find photos of me";
- deletes every photo you uploaded, from all events, from our storage;
- removes you from all events and deletes your device and sync records.
Events where you were the only organizer are archived. Events with other organizers continue under them. We keep an anonymous placeholder record ("Deleted user") so that other people's events, reports and any purchase records stay consistent. It contains no personal information.
Signing in again later creates a new, empty account.
10. Your rights
Depending on where you live (for example under Singapore's PDPA, the EU/UK GDPR, or US state laws such as California's), you may have the right to:
- access the personal data we hold about you, or receive a copy;
- correct it;
- delete it;
- object to or restrict certain processing;
- withdraw consent (for example by switching off "Find photos of me").
Most of this you can do in the app. For anything else, email [PRIVACY EMAIL]; we will answer within 30 days. You may also complain to your local data-protection authority.
11. Children
MemoryLane is not intended for children. You must be at least [16] years old to use it. If you believe a child has given us personal data, contact us and we will delete it.
12. Security
- All traffic is encrypted (HTTPS).
- Storage is private: photos are only reachable through short-lived signed links issued to signed-in event participants.
- Face data is stored only in our database, is never included in what the app downloads, and is never shown to anyone.
- Your sign-in session is stored in your device's secure keychain.
No system is perfectly secure. If a breach affects you, we will notify you and the authorities as the law requires.
13. Changes
We may update this policy. The effective date above shows the current version. Material changes will be announced in the app before they take effect. We will ask for your consent again before using face data in any new way.
14. Contact
[YOUR FULL LEGAL NAME], [POSTAL ADDRESS] — [PRIVACY EMAIL]