Privacy
Pre-launch information: legal and retention policies are awaiting final review.
Who runs First Diaries
First Diaries is operated by Marcos Y., Bergstrasse, 8708, Mannedorf, Switzerland. Contact: [email protected]. Please do not attach private memories or identity documents to an initial enquiry.
Information we process
For owners, Google Sign-In supplies an account identifier, name and email address. We store your language preference, diary details, contributions, declared authors, invitation permissions, approved revisions, gift editions and their access permissions. Photos, short videos and original contributions are personal information too. Security sessions, limited audit events, resource counters and processing records support the service.
Why we use information
We use this information to provide your private diary, accept and moderate contributions, prepare the book, grant access to a gift edition, export originals, process deletion requests and protect the service against abuse. Operational statistics measure usage and reliability; they do not include the text of memories. We do not automatically translate memories or publish them for marketing.
Who can see a diary
The owner manages the living diary and reviews contributions before publication. Contributors can submit through their private invitation and preview their own safe uploads; they cannot read the diary. A gift recipient can read only the published edition assigned to them. A forwarded invitation permits someone else to contribute and does not verify their identity. Keep links private and revoke them when necessary. Authorized operators may access data when necessary to provide support, investigate abuse or carry out a privacy request.
Service providers and international transfers
Google provides owner sign-in. Hosting, private object storage and backups require service providers. The final register of active providers, processing countries, retention and any international-transfer safeguards must be confirmed before the public pilot. Email activation is currently paused. We will publish the verified register here before enabling the affected integrations for real family data; no unverified location or contractual safeguard is claimed.
Retention and deletion
We keep diary content while it is part of an active diary or delivered edition, subject to withdrawal and deletion. Deletion blocks access immediately and queues removal of originals and derivatives. Unsafe or abandoned uploads and temporary exports have bounded, configurable expiry. Encrypted backups expire under the operational retention schedule; they are not erased instantly. A minimal deletion record is reapplied before restoring access from a backup. Exact active-storage and backup periods remain subject to verification and policy approval before launch.
Access, correction, export and privacy requests
Owners can export safe originals and metadata, change their diary presentation and request deletion in settings. Contributors and people mentioned in a diary can contact us to request access, correction, withdrawal or deletion, or object to processing as applicable. We may ask for proportionate evidence to verify the request without disclosing another person’s diary. A copy already downloaded by a recipient cannot be remotely erased. You may contact the Swiss Federal Data Protection and Information Commissioner about data-protection concerns; other rights can apply depending on your circumstances.
Children and other people
Memories can concern children and people who do not use this service. Owners and contributors must consider their privacy and have the necessary authority or permission to share the material. Do not provide unnecessary identification, health or other particularly sensitive details. Contact us if a contribution should be restricted or removed. An invitation is not proof of a person’s identity, age or parental authority.
Security and cookies
Private access is checked on the server. Invitations and recipient permissions can expire or be revoked. Uploads stay unavailable until validation, malware scanning and restricted processing succeed. We use necessary session and anti-forgery cookies, and local browser storage for language and reader preferences. Google Sign-In loads Google’s identity service on the sign-in page. We do not use advertising cookies or session recordings. No security measure can guarantee that a service will never fail; verified infrastructure and recovery remain launch requirements.
Changes and status of this notice
Version: 23 October 2026. This pre-launch notice describes the implemented controls and the outstanding provider and retention decisions. Material changes will be reflected here before the affected processing begins. Final legal review is still required.