The useful data. Nothing theatrical.
This notice explains what Yakparty processes to operate accounts, invitations, RSVPs, and event coordination.
WHAT WE PROCESS
Information you choose to provide.
Hosts provide an account identity, event details, and visibility choices. Guests may provide a name, email address, RSVP response, plus-one count, note, and comments. Technical records include session identifiers, timestamps, and security logs needed to operate the service.
WHY
To run the event—not build an audience profile.
Yakparty uses this information to authenticate hosts, render invitations, accept and update RSVPs, operate private links, provide host exports, prevent abuse, diagnose failures, and deliver notifications after the recipient has provided the required consent. Yakparty does not currently sell personal information or use it for third-party behavioral advertising.
PROCESSORS AND RETENTION
Small surface, explicit purpose.
The service runs on Cloudflare infrastructure, and Google processes identity information when Google sign-in is used. When a host shares through the device share sheet, the selected messaging app handles recipients and delivery; Yakparty does not receive that address book or delivery data. Information is retained while it is needed to operate the account or event, meet security and legal obligations, and resolve disputes. Capability URLs should be treated as sensitive.
YOUR CHOICES
Control starts with the host and guest.
Hosts can change event visibility and rotate private links. Guests can update an RSVP from the browser session that created or privately claimed it; knowing an email address alone does not grant access. Hosts choose the recipients of each device-shared message in their own messaging app. Account export and deletion workflows are still being completed; requests will be handled manually in the beta period.