What Wanasa is
Wanasa helps people create invitation pages, share them, collect RSVPs, and manage event participation. Guests do not need an account. Hosts can create and publish without signing in, then optionally save access through email recovery or a Google account.
Information we process
We process information you choose to provide and limited technical information needed to operate and secure the service.
- Event content, such as the title, host name, date, description, invitation design, photos, venue details, location coordinates, access settings, and polls.
- Guest activity, such as a display name, RSVP choice, additional guests, comments, poll votes, and an optional profile photo.
- If a guest joins a waitlist, their name, email, party size, and waitlist status. The event host can see these details in Manage. Verification and place-offer emails are transactional, not marketing.
- Host-access information, stored as protected credentials or one-way hashes rather than readable host tokens or event passcodes.
- Technical information, such as security cookies, browser-held event access, approximate request information used for abuse prevention, and limited first-party product analytics.
- If a host chooses Google sign-in, Google’s issuer, stable account identifier, verified email address, and optional profile name and picture.
How we use information
We use information only to provide, secure, maintain, and understand Wanasa.
- Publish invitations and display the information the host chooses to share.
- Process RSVPs, comments, polls, guest-list settings, and location reveal rules.
- Restore legitimate host access, prevent duplicate ownership, and protect private events.
- Detect abuse, rate-limit sensitive actions, diagnose failures, and improve essential product flows.
- Send transactional host-link receipts when the host explicitly requests one. These receipts are not marketing subscriptions.
Google sign-in
Google sign-in is optional and appears only after an event has been published. Wanasa uses the authorization code flow and validates Google identity server-side. We request only OpenID identity and verified email information. We do not request Google Contacts, Drive, Calendar, or advertising data.
Signing in does not automatically claim every event opened in a browser. Wanasa connects only events for which that browser already holds a valid host credential. A matching email address alone does not establish event ownership. Google data is used only for optional account access and event recovery.
Email sign-in
Email sign-in is optional. Wanasa sends a one-time link only when requested, stores the pending address in protected form, rate-limits requests, and does not use the address for marketing. The link expires quickly and creates a secure account session after verification.
Invitations and location privacy
Hosts control whether an invitation is public, uses a private invitation link, or requires a passcode. A private link can still be forwarded. For events configured to reveal the exact location only after RSVP, Wanasa withholds exact coordinates, map links, unit details, and entry instructions until an authorized guest submits a genuine RSVP.
Information intentionally placed on a public invitation can be viewed by anyone with its URL. Hosts should avoid adding information they do not want invitation recipients to see.
Cookies and analytics
Wanasa uses secure cookies and browser storage for language preferences, drafts, host ownership, guest RSVP continuity, private-event access, abuse prevention, and optional account sessions. Essential functionality may not work correctly if these are blocked.
Product analytics are designed not to include host credentials, event passcodes, guest names, event names, addresses, or email addresses. Analytics failures do not block publishing, sharing, RSVPs, email delivery, or sign-in.
On public home pages, you can choose whether to allow the X advertising pixel. It is not loaded before you allow it or after you decline it. You can change your choice from Ad measurement choices. Wanasa does not load it on private invitation, account, or management pages. We keep limited campaign labels from ad links for first-party measurement.
Service providers and sharing
Wanasa may use infrastructure, mapping, analytics, authentication, storage, and transactional-email providers to operate the service. Those providers process information only as needed for their service and under their own applicable terms. Wanasa does not sell personal information and does not use recovery emails for marketing.
We may disclose information when required by law, to protect users or the service, or as part of a lawful business transfer subject to appropriate protections.
Retention and deletion
We retain event and account information for as long as reasonably needed to provide the service, preserve legitimate host access, prevent abuse, and meet legal obligations. Security and rate-limit records may be kept for shorter operational periods. Hosts can cancel events without invalidating unrelated events or browser access.
Requests concerning access, correction, or deletion should be sent to the support address published in Wanasa’s Google authorization screen. We may need to verify host ownership before acting on an event.
Security
Wanasa uses measures such as encrypted transport, server-validated sessions, protected credentials, rate limits, and privacy-aware responses. No online service can promise absolute security, so hosts should protect management links and avoid forwarding them to guests.
Changes and questions
We may update this policy as Wanasa changes. The effective date above identifies the current version. Material changes will be presented through the service when appropriate.
For privacy questions, use the support contact identified on Wanasa’s Google authorization screen.