Nimanto (“we”, “us”), operated by Nimanto Inc, provides digital invitations with RSVP collection at nimanto.com. This policy explains what personal data we process, why, and the choices you have. It applies to hosts who create invitations and to guests who open them.
What we collect
- Account data from hosts: name, e-mail address, optional phone number, and a password hash if you sign up with e-mail. If you sign in with Google we receive your name, e-mail address and profile picture from Google. If you sign in with Apple we receive the name and e-mail address you choose to share; if you hide your e-mail, Apple gives us a private relay address that forwards to you.
- Invitation content that hosts create: text, photos, music files and event details such as dates and venues.
- Guest lists that hosts add or import: guest names, e-mail addresses, phone numbers and group tags. Hosts are responsible for having permission to share this information with us.
- RSVP responses submitted by guests: name, attendance, number of guests, optional e-mail, phone, dietary notes and messages.
- Messages and feedback you send us: your name, e-mail address and message in the contact form, and your answers in the Feedback form together with the page you sent them from, the type of browser and device, and the size of its window. Feedback is linked to your account only if you are signed in when you send it.
- Usage data: when an invitation is opened, server logs, and a hashed IP address on RSVP submissions used only to prevent abuse.
- Payments: card details are entered on Stripe and never reach our servers. We store the order amount, status and Stripe identifiers.
How we use it
- To provide the service: render invitations, deliver personal guest links, collect RSVPs and show hosts their responses.
- To send transactional e-mail such as invitations on a host’s behalf, RSVP confirmations, event updates the host writes, collaborator invites and receipts.
- To keep the service secure, prevent spam and comply with legal obligations.
We do not sell personal data and we do not use guest data for advertising.
Who we share it with
We use service providers who process data on our behalf under contract: Railway and Hostinger (hosting), Neon (database), Google (sign-in and, with your consent, Analytics), Apple (sign-in), Stripe (payments), Amazon Web Services (Amazon SES, e-mail delivery), Twilio (SendGrid e-mail delivery), Telnyx (text messages), Anthropic (Design Genie, our AI designer) and Magic Hour (design artwork). Guests see only the invitation a host shares with them. Hosts and their collaborators see the guest list and RSVPs for their own events.
E-mail we send, and how to stop it
Every e-mail Nimanto sends is about a specific event or account: an invitation from a host who added you to their guest list, an RSVP confirmation, an update the host wrote to their guests, new photos in an event album, or account mail to hosts (welcome, publish receipts, RSVP alerts, receipts). We do not send marketing or newsletters, we do not buy, rent or share address lists, and a host cannot upload a list to send anything other than their own invitation and updates to it.
- Who can send to you: only a signed-in host who typed or imported your address into their own guest list. Each e-mail names the host and the event and carries a Reply-To that reaches the host directly.
- Unsubscribe: every guest e-mail has an Unsubscribe link in its footer and the standard list-unsubscribe headers that Gmail, Apple Mail and Outlook turn into a one-click button. You can stop e-mails about one event or everything from Nimanto; it takes effect immediately, and you can undo it on the same page.
- Bounces and complaints: when a mailbox rejects our e-mail permanently, or you mark one as spam, our mail provider reports it and the address goes on our do-not-mail list automatically. No host can e-mail it again through Nimanto, and the host sees why in their guest list so they can reach you another way.
- No tracking: our e-mails contain no open-tracking pixels and links are not rewritten through tracking redirects. We keep a delivery record of each e-mail and text message we send: its type, when it was sent, the account and invitation it belongs to (and the co-host or Nimanto staff member who sent it, when that was not the host), whether it was delivered, bounced or refused, and a one-way fingerprint of the address or phone number with its domain or country code, never the address itself, the subject or the body. We use it to track use against plan allowances, prevent abuse, keep our e-mail deliverable and understand what sending costs.
- Limits: each account has a fair-use weekly sending allowance, which keeps any single host from sending in bulk.
To be removed by hand, or to ask which hosts have your address, write to privacy@nimanto.com from the address in question.
Text messages we send, and how to stop them
Nimanto sends one kind of text message: an RSVP alert to a host, at a number that host entered on their own invitation and ticked a box to agree to. Nothing is sent until that box is ticked, and it is recorded with the number it was given for, so changing the number asks for it again. Guests are never texted. A phone number a guest leaves on an RSVP goes to the host so they can reach the guest; we do not message it.
- What they say: that a named guest replied, and their answer, with a link to the host’s dashboard. Never marketing.
- How often: one text per reply, within the account’s plan allowance. Message and data rates may apply.
- Stopping them: reply STOP to any text, or untick the box on the invitation. Reply HELP for help. The e-mail alert is unaffected.
- Your number is not shared: we do not sell phone numbers, and mobile opt-in information and consent are never shared with third parties or affiliates for their own marketing. The number reaches only the network operator carrying the message (Telnyx, and the mobile operator beyond it). The delivery record we keep of a text holds a one-way fingerprint of the number and its country code, never the number or the message itself.
The programme in full is set out in our SMS Terms.
Retention
Invitation content, guest lists and RSVPs are kept for as long as the host’s account exists or until the host deletes the event. Deleting an event removes its guests and RSVPs. Deleting an account removes everything associated with it. Delivery records of the e-mails and text messages we send are kept for at most 13 months and are deleted with the account; deleting an event keeps them but removes their link to it. Backups are purged on a rolling basis. The do-not-mail list is kept indefinitely so that an unsubscribe or a bounce is honoured even after the event that caused it is gone.
Your rights
You can access, correct, export or delete your data. Hosts can do this from the dashboard; guests can ask the host who invited them or contact us directly. Depending on where you live you may have additional rights under GDPR, the UK GDPR, India’s DPDP Act or US state laws, including the right to complain to a supervisory authority.
Cookies
We use a strictly necessary session cookie to keep hosts signed in and a security token to protect forms, and we remember your cookie choice for 180 days. We do not use advertising or cross-site tracking cookies.
Google Analytics loads only after you choose “Accept all” in the cookie banner. Until then no request goes to Google, and afterwards its cookies (_ga, _ga_*) last at most 13 months. Choosing “Essential only” later stops it and removes those cookies. Fonts are served from our own servers, so opening a page does not contact Google Fonts.
An invitation can include a Google Maps map or music from YouTube if the host added one; those load from Google when a guest opens that invitation.
Children
Accounts are for people aged 16 or over. Guests of any age may open an invitation, but we do not knowingly collect personal data from children beyond what a host enters.
Contact
Questions or requests: privacy@nimanto.com. The controller of your data is Nimanto Inc. We will update this policy when our practices change and show the date above.