Privacy Policy

This policy explains how Wedlog handles personal data when you use the Wedlog mobile app, visit this website, create a wedding, join one with an invite code, submit an RSVP, or contact support.

Wedlog is still preparing for public release. This policy describes the implemented service as of the date above. It is an operational draft and should receive independent legal review before store publication, particularly the section about children’s names.

1. Who is responsible for your data

The data controller is Marc Widmer, a natural person operating Wedlog from Spain.

For privacy questions or to exercise your rights, email support@wedlog.app. There is no appointed Data Protection Officer.

2. What Wedlog does not collect

Wedlog has no email-and-password accounts, public user profiles, advertising, tracking pixels, or advertising identifiers. Analytics is opt-in and off by default; see the section below. The public website does not set analytics or advertising cookies. Wedlog does not request your device location and does not offer photo uploads.

3. Data we process and why

Installation identity and security

When the app starts, Firebase Authentication creates an anonymous installation identity. Wedlog and Firebase also process technical installation identifiers, authentication credentials, device and app information, and security logs. These let the app remember which weddings your installation can edit or has joined, enforce access rules and rate limits, and protect the backend.

The legal bases are providing the service you request and taking steps at your request (Article 6(1)(b) GDPR) and Wedlog’s legitimate interest in keeping the service secure and reliable (Article 6(1)(f)).

Wedding details

If you create or edit a wedding, Wedlog stores the couple’s names, date and time, time zone, venue name and address, venue coordinates, Google place identifier when selected, invite code, editor installation identifiers, acceptance time, and the accepted Terms version. Guests who know the invite code can see the active wedding details.

This processing is necessary to provide the wedding service (Article 6(1)(b)). Access controls, invite-code abuse prevention, and moderation also rely on Wedlog’s legitimate interests (Article 6(1)(f)).

Venue search

When a wedding creator types a venue search, Wedlog sends the search text from a protected server function to Google Places and returns a small set of venue suggestions. Wedlog stores only the venue information the creator selects or enters; it does not store the unselected search results as wedding data. Google processes the request under its own service terms and privacy policy.

These requests provide features explicitly used by you (Article 6(1)(b)).

RSVP responses, including children’s names

An RSVP can contain the respondent’s name, attendance, one adult companion’s name, and up to ten children’s names. It also contains the respondent’s installation identifier and timestamps needed for ownership and deletion. Current wedding editors can see responses for wedding planning.

An adult respondent supplies children’s names. Wedlog asks only for a name—no date of birth, contact detail, health information, or account is requested for a child. The adult must have authority to provide that information. The basis is the legitimate interest of the adult, the couple, and Wedlog in organizing attendance with strictly limited data and short retention (Article 6(1)(f)). Because children deserve specific protection, you may ask for a child’s name to be removed at any time.

Updates and push notifications

Wedlog processes Firebase installation and messaging identifiers and a wedding topic subscription to deliver structured wedding updates. The app does not use notifications for advertising. You can disable notification permission in your device settings and leave a wedding to stop its topic subscription.

The basis is providing the requested wedding service (Article 6(1)(b)) and the user-controlled device permission. Security and delivery reliability rely on legitimate interests (Article 6(1)(f)).

Crash diagnostics

If Crashlytics is enabled, Google Firebase Crashlytics receives crash traces, installation identifiers, app version, operating-system and device details, technical state, and logged diagnostics. Wedlog’s logging rules prohibit intentionally sending invite codes, notification tokens, or personal form contents to Crashlytics. You can disable crash reporting in the app’s Settings.

The basis is Wedlog’s legitimate interest in detecting and fixing failures (Article 6(1)(f)), balanced by the in-app opt-out.

Product analytics

Wedlog collects Firebase Analytics data only if you enable the Analytics switch in Settings. It is off by default. When enabled, the app sends five aggregate events — wedding_created, wedding_joined, rsvp_submitted, wedding_deleted, and wedding_reported — and screen_view events without personal content for navigation destinations. These event payloads contain no wedding IDs, installation IDs, names, invite codes, or RSVP content. The purpose is to understand aggregate product usage and improve Wedlog. The legal basis is your consent (Article 6(1)(a) GDPR), which you can withdraw by turning the switch off.

Safety reports and support messages

If you report a wedding, Wedlog stores the selected reason, optional text of up to 500 characters, the wedding ID, your reporter installation identifier, status, and timestamps in a server-only collection. Reports are not shown to the couple or guests. Do not include unnecessary sensitive information in free text.

If you email support, Wedlog processes your email address, message, wedding ID, installation ID, and any information you choose to include to answer the request. The in-app support contact can prefill the app version and build, device model, operating-system version, installation ID, and active wedding ID; you choose whether to send that draft and may add screenshots manually. The bases are handling your request (Article 6(1)(b)) and the legitimate interest in operating, supporting, and moderating the service (Article 6(1)(f)). Legal obligations may also apply (Article 6(1)(c)).

This website

Firebase Hosting processes request IP addresses and standard web request information to deliver and protect this website. Wedlog does not add analytics, advertising trackers, or forms to the site.

4. Who receives data

Wedlog uses these providers:

• Google LLC and its affiliates: Firebase Authentication, Firestore, Cloud Functions, Cloud Messaging, Crashlytics, Firebase Analytics/Google Analytics, and Hosting; and Google Places for venue search.
• Email providers involved in support: Proton handles email sent to support@wedlog.app; your own email provider processes the message as well.

Wedding details and RSVP responses are also disclosed to the current editors of that wedding as described above. Wedlog does not sell personal data and does not share it for behavioural advertising.

5. International transfers

Google may process data outside the European Economic Area. Its cloud data-processing terms provide transfer mechanisms including the European Commission’s Standard Contractual Clauses where required. Email may pass through infrastructure in other countries depending on the sender’s provider.

You can ask for more information about the applicable safeguards by contacting support.

6. How long data is kept

• Wedding data remains while the wedding exists. Its owner can permanently delete the wedding in the app; this cascades the wedding, invite-code reservation, structured updates, and RSVP responses. Wedlog may also delete illegal, abandoned, or suspended content when justified.
• RSVP responses become unreadable at the wedding date plus 30 days and are scheduled for automatic physical deletion by Firestore. The respondent can delete a response earlier.
• Safety reports are kept for no more than 12 months, unless a longer period is necessary for an active legal claim or statutory duty.
• Crashlytics data is retained by Firebase under its published retention schedule; Google currently states that crash traces and associated identifiers are kept for 90 days before deletion begins.
• Analytics data is retained according to the setting configured for Wedlog’s Google Analytics property. Google currently documents 2 or 14 months for user-level data and 2 or 14 months for event-level data in standard properties; aggregated reports are treated separately. See Google’s published Analytics retention terms.
• Firebase Hosting IP data is retained by Google for a few months under its published Firebase privacy information.
• Support correspondence is kept only as long as needed to resolve the request and document any resulting legal or security action.
• Anonymous installation and messaging identifiers remain while needed to operate the installation and its memberships, subject to provider deletion windows after a deletion request.

Backups and provider deletion queues can take additional time to expire securely.

7. Your choices and rights

You can edit or delete your RSVP in the app, leave a wedding, disable notifications at operating-system level, disable Crashlytics, and opt in to or out of Analytics in Settings. A wedding owner can delete the wedding in the app.

Under the GDPR, where applicable, you may request access, rectification, erasure, restriction, portability, or object to processing. You may withdraw consent where processing relies on consent; withdrawal does not affect earlier lawful processing. Some rights depend on the legal basis and circumstances.

Email support@wedlog.app and include the wedding ID and installation ID shown in the app’s Settings. Wedlog may ask for proportionate information to verify that the request concerns your installation or data. Requests are normally answered within one month.

You may complain to the Spanish Data Protection Agency (AEPD) or the supervisory authority where you live or work. For a complaint about an unanswered rights request, contact Wedlog first so the request and response can be evidenced.

8. Children

Wedlog is a wedding utility, not a service directed at children. A child should not independently create or administer a wedding. An adult may include a child’s name in an RSVP only when authorized to do so. The name is visible only to current wedding editors, is used for attendance planning, and follows the same 30-day post-wedding deletion rule as the rest of the response.

To remove a child’s name sooner, delete or edit the RSVP or contact support. This limited treatment should receive independent legal review before public release.

9. Security

Wedlog uses encrypted network connections, Firebase-managed encryption at rest, anonymous authentication, server-side access rules, rate limits, private RSVP documents, and server-only moderation reports. No online service can guarantee absolute security. If you believe data has been exposed, contact support promptly and do not include secrets in the initial message.

10. Changes to this policy

The current version is always published at this URL. Material changes will update the date and version and, when appropriate, will be communicated in the app. The version recorded when a wedding is created identifies the legal documents accepted at that time.