Privacy Policy

Version: 2026-07-20
Effective date: July 20, 2026
Last updated: July 20, 2026

1. Who we are, and who to contact

Weddify ("Weddify," "we," "us") operates the Weddify mobile app and the website at weddify.com (together, the "Service"). Weddify is operated by Youcef Tchouar, a sole proprietor based in Laval, Quebec, Canada.

Weddify is responsible for the personal information described here. Quebec's Law 25 requires us to name the person accountable for it:

• Privacy Officer: Youcef Tchouar
• Title: Privacy Officer, Weddify
• Email: privacy@weddify.com
• Based in: Laval, Quebec, Canada

Email the Privacy Officer for any question in this policy, to exercise a right in section 9, or to complain. We do not publish a postal address, so email is the way to reach us.

2. What this version of Weddify does

This version is a private wedding-planning tool: guest lists and RSVPs, tasks, budget, timeline, seating and meals, a private event feed with photos, posts, polls, and messages, and a cash fund guests can contribute to. There is no vendor marketplace, no vendor accounts, and no vendor payouts in this version, so this policy does not describe any.

Cash-fund contributions are processed by Stripe, and money moves from the guest to the couple's own Stripe account -- Weddify does not keep it. What that means for your personal information is in sections 3, 5, 6, and 8.

3. What we collect

• Account information -- name, email address, password (never stored by us in readable form -- it is hashed by our self-hosted Keycloak identity server), profile photo, language preference, and, if you sign in with Google or Apple, the basic profile that provider returns (name, email, provider account id). Optionally a phone number.
• Your wedding -- event name, date, location, cover photo, description, and the collaborators you invite.
• Guest list -- guest names, email addresses, phone numbers where you enter them, RSVP status, plus-ones, meal choices, dietary restrictions and allergies, seating assignments, and any notes you add. Dietary and allergy information can reveal health or religious details, so we treat the guest list as sensitive.
• Planning data -- tasks and who they are assigned to, budget lines and amounts, timeline entries, checklists.
• Content you upload -- photos, videos, posts, comments, polls and poll answers, and messages in event chats and threads.
• Cash-fund contributions -- if you contribute to a cash fund we record the name you give, the email address you give (optional), the amount and currency, the note you write to the couple (optional), whether you asked to stay anonymous to other guests, whether you chose to cover the processing fee, and Stripe's reference for the charge. We never receive or store your card number -- card details are entered on Stripe's own payment pages. If a host connects a payout account, we store Stripe's identifier for that connected account and whether Stripe has enabled charges and payouts on it; the identity and banking details behind it are held by Stripe, not by us.
• Device and diagnostic data -- device model, operating system, app version, and push-notification token (needed to deliver a push). Crash reporting is not currently enabled, so the app does not send crash reports today. If we enable it, a crash report would contain a stack trace, device model and OS, app version, and your user id, and we will update this policy before turning it on.
• Server-side technical data -- IP address and request metadata in server logs, used for security, abuse prevention, and rate limiting.
• Address searches -- when you type in an address or venue field and address autocomplete is enabled, the text you type is sent to Google's Places API to return suggestions. See section 5.

We do not collect precise GPS location, and we do not use advertising identifiers (IDFA / AAID) or any cross-app tracking.

4. Information about your guests -- people who never signed up

Hosts enter personal information about other people. Most guests will not have a Weddify account.

• We use that information only to run the host's event: delivering the invitation, recording the RSVP, seating, meals, and event notifications.
• We do not market to guests, sell guest data, or use a guest list for any purpose outside the event it belongs to.
• If you are a guest, you can email privacy@weddify.com to ask what we hold about you and to have it corrected or deleted -- you do not need an account. We will action it and tell the host that a record was removed at the person's request.
• The host controls the guest list and can delete any guest at any time. Deleting the wedding or the host's account deletes the guest records with it.

Hosts: under our Terms you are responsible for having a legitimate reason to hold the contact details you upload.

5. Service providers we use

We share personal information only with the providers we need to run the Service. Each is bound to use it only for the service they supply to us.

• OVH Cloud -- hosting, databases, and object storage for all app data and uploaded media. Processed in Beauharnois, Quebec, Canada (region BHS).
• Twilio SendGrid, Inc. -- transactional email: invitations, email verification, password resets, notification emails. United States.
• Apple Inc. -- Apple Push Notification service, for push notifications to iOS devices. United States.
• Google LLC -- Places API for address / venue autocomplete: the text you type into a location field is sent to Google. Also "Sign in with Google," if you use it. United States.
• Apple Inc. -- "Sign in with Apple," if you use it. United States.
• Functional Software, Inc. (Sentry) -- crash and error reporting for the mobile app. Not in use today: crash reporting is not enabled, so no data is sent to Sentry. It is listed because the app ships with the library and we would turn it on in a future release. United States.
• Stripe Payments Canada, Ltd. (with Stripe, LLC, United States, as an additional party for the processing of personal data) -- card processing and payouts for cash-fund contributions and paid features, and the identity checks Stripe runs before it will pay a host out. Card details are entered on Stripe's own pages; Weddify never receives or stores card numbers. Canada and the United States.

Our identity server (Keycloak) is self-hosted on our own OVH infrastructure -- it is not a third-party service and your credentials do not leave our environment.

We may also disclose information where the law requires it -- a valid court order, warrant, or legal demand -- or where it is necessary to protect someone's safety. We do not sell personal information, we do not share it for anyone else's marketing, and we do not use your event content to train machine-learning models.

6. Where your data lives, and cross-border transfers

All Weddify application data -- accounts, weddings, guest lists, planning data, messages, and uploaded photos and videos -- is stored in Canada, on OVH Public Cloud in Beauharnois, Quebec. Media is held in OVH Object Storage in the same region and served through our own media service, so uploaded files are never in a publicly readable bucket.

Some of our providers are based in the United States, so limited personal information is transferred there:

• SendGrid receives the recipient's email address and the content of the email we send (for example an invitation naming the couple and the event).
• Apple receives your device push token and the notification payload.
• Google receives the text you type into an address field, and -- if you use "Sign in with Google" -- your Google account identity.
• Sentry receives nothing today, because crash reporting is not enabled. If we turn it on, it would receive crash reports including your user id.
• Stripe receives the card details you enter on its pages, the amount and currency of a contribution, and the name and email address you give with it. If you are a host connecting a payout account, Stripe also receives the identity and banking information it asks you for during its own onboarding.

This matters for cash funds specifically. Weddify's own records of your wedding stay in Canada, but a payment is not a Canadian-only event: the charge is created on Weddify's Stripe platform account, transferred to the couple's connected Stripe account, and Stripe processes and stores that transaction data in the United States. Weddify's Stripe platform account settles in Canadian dollars (CAD).

Information held by a US provider can be accessed by US authorities under US law. We use each provider's data-processing terms and keep the data sent to them to the minimum needed.

7. Why we use your information

• To run the Service: create your wedding, send invitations, record RSVPs, deliver messages and notifications, host your photos.
• To process cash-fund contributions: take the payment through Stripe, transfer it to the couple's connected account, show the couple who contributed and how much, and handle refunds.
• To keep the accounting and tax records the law requires for payments.
• To keep accounts secure and to prevent fraud and abuse.
• To provide support when you ask for it.
• To fix crashes and keep the app working.
• To meet legal obligations.

We rely on your consent, given when you create an account and accept these documents, and on the consent implied by using a feature (entering an address sends that text to the autocomplete provider; enabling push sends a token to Apple). You can withdraw consent as described in section 9.

We do not carry out automated decision-making that produces legal or similarly significant effects about you, and we do not profile you for advertising.

8. How long we keep it

• Account and profile -- until you delete your account.
• Wedding, guest list, planning data -- until the host deletes the wedding or their account. There is no automatic expiry today.
• Photos, videos, posts, messages -- removed from view immediately when deleted; hard-purged from storage 30 days later.
• Encrypted database backups -- up to 28 days (daily snapshots kept 7 days, weekly snapshots 28 days, off-site copies 14 days).
• Push notification tokens -- until you sign out, delete the app, or delete your account.
• Server and security logs, including IP addresses -- rotated by size, not on a fixed time window: each service keeps at most three log files of 50 MB each, and the oldest is deleted when a new one is started. How far back the logs reach therefore depends on how busy the service is.
• Crash reports -- none. Crash reporting is not currently enabled, so we hold no crash reports.
• Email delivery records held by SendGrid -- kept by SendGrid under its own retention rules and plan settings, not by us.
• Cash-fund contribution records (contributor name and email, amount, message, Stripe reference) -- kept while the fund exists, and after that for as long as accounting and tax law in Canada requires us to keep a record of the transaction.
• Transaction data held by Stripe -- set by Stripe under its own retention rules, not by us.

Records we are legally required to keep -- for example accounting and tax records for cash-fund contributions -- are kept for the period the law requires and then deleted. That means deleting your account does not necessarily erase the record that a payment happened.

9. Your rights, and how to use them

Under PIPEDA and Quebec's Law 25 you can:

• Access -- get a copy of the personal information we hold about you. In the app: Settings → Data & Privacy → Export my data. It returns a JSON file.
• Correct -- fix anything inaccurate. Profile fields are editable in the app; for anything else, email us.
• Delete -- delete your account and content: Settings → Account & Security → Delete Account. Guests without an account can email us.
• Portability -- the export is machine-readable JSON you can take elsewhere.
• Withdraw consent -- turn off notification categories in Settings → Notifications, or delete your account to withdraw entirely. Some features stop working without the data they depend on, and we will tell you which.
• De-indexing / cessation of dissemination (Law 25) -- ask us to stop disseminating information about you or to de-index it, where the law allows.

Email privacy@weddify.com for any of these. We will respond within 30 days, as PIPEDA and Law 25 require. We may need to verify who you are before acting.

If you are not satisfied, you can complain to the Office of the Privacy Commissioner of Canada or, in Quebec, the Commission d'accès à l'information du Québec.

10. Security, and what happens if there is a breach

We protect your information with TLS encryption in transit, encryption at rest for backups, a firewalled single-tenant production environment where only the API gateway is reachable from the internet, hashed credentials handled by Keycloak, access-controlled media URLs, and least-privilege access for the small number of people who can reach production.

No system is perfectly secure. If a confidentiality incident creates a risk of serious injury, we will notify the affected people and the relevant regulators (the Office of the Privacy Commissioner of Canada and, for Quebec residents, the Commission d'accès à l'information) promptly and without unreasonable delay, and we will keep the register of confidentiality incidents Law 25 requires.

11. Cookies, storage, and similar technologies

The mobile app does not use cookies. It stores your session token in the device keychain and caches data locally so the app works offline. None of that is tracking.

The website (weddify.com) is a marketing and legal-information site. It sets no analytics, advertising, or tracking cookies today. If we ever add analytics, we will update this policy and -- where consent is required -- ask before setting anything non-essential.

There is no cookie-preferences screen in the app or on the site, because there are no optional cookies to configure.

Our full Cookie Policy has the details.

12. Children

The Service is for people 18 and over. We do not knowingly collect personal information from anyone under 18. If you believe we have, email privacy@weddify.com and we will delete it.

A host may enter a child's name on a guest list (for a meal count or a seat). That information belongs to the host's event, is not an account, and is deleted with the guest record.

13. Changes to this policy

We may update this policy. If a change is material we will show a notice in the app at least 30 days before it takes effect and ask you to accept the new version. The version identifier and dates at the top of this policy always identify the current one.

14. Contact

Privacy Officer, Weddify
Youcef Tchouar
privacy@weddify.com
Laval, Quebec, Canada

We do not publish a postal address; email reaches us fastest.