Skip to content

Privacy

Updated 22 October 2026

EverAfter · Operated by

Floriel Fedry, sole proprietorship
Franklinstrasse 20
8050 Zürich
Switzerland
support@full-human.com

Who is responsible

Floriel Fedry operates EverAfter at ever-after.ch. Contact support@full-human.com for privacy questions or requests concerning your data. The couple manages the guest information and responses for their wedding; EverAfter provides the service that stores and displays them.

Information we use

We use account details to sign you in, invitation content and translations to display your website, guest names, contact details, groups and personal messages to personalize invitations, and RSVP responses to help the couple organize the wedding. Replies may include companions, children, optional dietary needs, allergies and messages. Only provide sensitive information you want the couple to receive. We record when guest links are opened and when replies are submitted; the couple can see these records. If the couple uses Planning, we keep their budget, costs, payments and to-dos, including the supplier contact details they add, such as a business name, contact person, email, phone number and website. Planning is private to the couple’s account, is never shown to guests and is included in the data export. With your account we store the kind of link through which it was created (such as Pinterest, an invitation or a direct visit) or the app it was created in, but not the link itself or the pages visited before.

App Store payment data

Apple processes iOS in-app payments. We associate Apple transaction references, product, environment, purchase and revocation status, and access dates with your wedding. Apple receives a random wedding identifier to link the purchase to your EverAfter account; this identifier contains no guest names or contact details. We do not receive your full payment card details from Apple.

Google Play payment data

Google processes Android in-app payments through Google Play. We associate the purchase token, product, purchase and expiry dates, and refund or revocation status with your wedding. Google receives a pseudonymous wedding identifier, a hash derived from your wedding’s internal ID, to link the purchase to your EverAfter account; it contains no guest names or contact details. We do not receive your payment card details from Google.

Payments, translation and hosting

Stripe processes payments and related fraud checks. We store payment references, status and access dates; card and TWINT payment details are entered with Stripe. On the website, translations are entered manually; invitation text and personal messages are not sent to an automatic translation service. Neon provides database storage and account authentication. Vercel hosts the website, stores uploaded invitation photos in Vercel Blob, and processes technical request data for delivery and security. Uploaded photos are resized and their embedded metadata is removed. Photos have public image links: anyone with a photo’s link can view it. Uploaded photos remain stored until account deletion, including photos replaced in the editor.

Printed invitations

If you order printed invitations, Gelato prints them in Switzerland and Swiss Post delivers the parcel to you. For each card we send Gelato its print file: your invitation’s design, the guest’s name and greeting, and their personal invitation link as a QR code. We also send the delivery name and address and the email address you enter at payment. Print files are stored in Vercel Blob with unguessable links so that Gelato can fetch them. Gelato keeps order data under its own retention rules; we keep the order, the chosen guests and the delivery address until account deletion.

Language suggestions in the apps

The apps can suggest a translation or smoother wording, but only when you ask. On Android, translation uses Google ML Kit and rewording uses Gemini Nano; both run on your device. Their language models are downloaded from Google, and Google may receive diagnostic and usage information about these features under its own terms. On iPhone, suggestions use Apple’s translation and Apple Intelligence on the device. The text you are working on is not sent to EverAfter or Google to make a suggestion; what you then save is stored like any text you type. Review every suggestion before saving it. If you report a suggestion from the app, the suggestion, the original text, your optional comment and the language are sent to EverAfter and linked to your account. We keep them to improve this feature and to handle your report, until you delete your account.

Reply notifications

If you turn on reply notifications in an app, we store a device token issued by Apple Push Notification service (iPhone) or by Firebase Cloud Messaging, a Google service (Android), with the app’s language and platform, linked to your account. When a guest replies, we send the guest’s name and answer, for example “Coming · 3 people”, through Apple or Google to your device. Turning notifications off or signing out of the app removes the token, as does deleting your account. Tokens the service reports as no longer valid are deleted.

External content and international processing

Invitation images may load from Unsplash or a media address supplied by the couple. Loading this content shares technical information such as your IP address with that provider. External links, including maps or payment pages, have their own privacy terms. Our service providers operate internationally, including in Europe and the United States; their privacy notices describe their processing and transfer arrangements.

Cookies and link privacy

We use authentication cookies and local preferences to make the service work. We do not run advertising. We use Vercel Web Analytics without analytics cookies to measure visits to public marketing pages, including demos, blog articles, support and legal pages. On those pages it also counts a few clicks, anonymously: for example which sign-up button was pressed, which design was chosen in the demo and whether a reply was tried there, which help video was started, and the kind of link a visit came from (such as Pinterest, a search engine or an invitation). These counts hold no names, email addresses or invitation links, and nothing is stored on your device for them. Private invitations, account and workspace pages, authentication, owner previews and printed invitations are excluded. Analytics URLs omit query strings and fragments, except the campaign parameters of the link that brought the visit (utm_source, utm_medium, utm_campaign). Personal invitation links act as access keys: anyone who receives or forwards one can view that invitation and submit or change its reply. Guest invitations are marked not to be indexed by search engines; this is not a password barrier.

Retention and deletion

Invitation and response data remain in your account after publishing access expires, until deletion. You can delete your account in the apps (Android: Settings → Your data → Delete account; iPhone: Account → Delete account), in settings on the website, or by writing to support@full-human.com from your account’s email address; we handle requests manually when self-service deletion is unavailable. Our Neon database uses a six-hour restore-history window. This recovery window is not a guarantee that every provider backup copy is erased within six hours. Account deletion removes your wedding data, uploaded photos, devices registered for notifications and reported suggestions from the active application; it does not instantly erase provider backups or the payment records that Stripe, Apple or Google keep. You can export your wedding data in settings or ask support for access, correction or deletion. Guests can contact the couple or support. We may verify your identity before fulfilling a request.

How to delete your account

Your choices

You can update a reply through your invitation link, ask the couple to correct guest details, and request information or deletion from support. You may also contact the Swiss Federal Data Protection and Information Commissioner about privacy concerns. Changes to this notice will be shown on this page.