Privacy policy

1Who we are

Jamaatna (jamaatna.net) is a platform for wedding and occasion invitations and for checking guests in at the door. In this policy, "we" means Jamaatna, a "host" is the person an event's account belongs to, and a "guest" is someone a host invites. You can reach us at support@jamaatna.net, or on WhatsApp from the link at the foot of this page.

2Host accounts

There's no public sign-up: our team creates an account after you contact us. For each account we keep your name, email address and phone number, your organisation's name if you give one, and your password, stored in a form we can't read. You sign in with your email or phone number and your password.

We also log important actions on an account, such as editing an event or adding a scanner, with the time and the IP address they came from, so we can trace faults and misuse.

3Your events and your guests' details

When you create an event we store what you enter: its title, date, venue, invitation text and design choices, any logo you upload for the initials monogram, and your guest list. For each guest the list can hold a name, family name, phone number, email address, number of companions, table number, tags and your own notes.

• You're responsible for having the right to share your guests' details with us, and for letting them know, where needed, that you use Jamaatna to send their invitations.
• We use guest details only to run your event: to make each guest's invitation link and entry code, show you their replies, and check them in at the door. We don't sell them, we don't use them for our own marketing, and we don't contact your guests other than with the invitation itself.
• On the Premium package our team can add your guests, send the invitations and set up your gates for you, so they see your guest list for that purpose only.
• Scanner accounts you create for your door team hold a username, the gate's name and a password. We keep that password readable on purpose, so you can share it with your team again. Each check-in records which scanner and gate recorded it.
• A monogram logo you upload is stored as a public file: anyone with its address can open it, as they can when they see it on your invitation.

4What we keep when a guest opens an invitation

Guests need no account and no app: each guest gets a personal link. Anyone holding that link can open the invitation, so it's best shared only with the guest. When a guest uses their invitation we keep:

• their reply, attending or not, and how many people are coming with them;
• any wish they leave: the name they type and their message. The host chooses whether wishes are shown to the other guests or kept for the host alone;
• their check-in at the door: the time, the gate and the scanner that read their code, and any undo of that check-in.

The entry code (QR) holds no name or phone number. It's a signed code that only our system can check.

Saving the invitation as an image, the attendance story image and sharing the event's details all happen on the guest's own device. None of it is sent to us.

5The free announcement maker

The announcement maker at /announce builds your story image inside your browser. The photo you add never leaves your device: it isn't uploaded to us or to anyone else. The names, date and text you type stay in your browser too, and the finished image is made and saved on your device. We only count steps such as starting, changing the design and downloading, without the names you typed (see analytics below).

Before your first download or share on a device, the maker asks for your name and mobile number, and your email if you like. These do reach us: we keep them so our team can contact you about Jamaatna and your occasion, and only our admins can see them. Your device only remembers that you already filled the form, not what you wrote. We keep these details.

6Analytics and session recordings

We use analytics tools to understand how the site is used and to fix what goes wrong. They record page views, clicks and steps such as opening a design or downloading an announcement, and some record sessions to replay how a page was used.

• Recordings mask everything typed into form fields, but the rest of the page's text is recorded as it appears on screen, which can include names shown on the page.
• The personal code in an invitation link is removed from page addresses before anything is sent, and session recordings never run in the admin console.
• We don't sell personal data, and we don't share it with advertisers.

These tools set their own cookies or browser storage to recognise a returning browser. You can block them in your browser's settings or with a content blocker, and the site keeps working without them.

7Audio on invitations

A host can add an audio file to their invitation with a link. When they do, the invitation loads a player from the site the link comes from as soon as it opens, before the guest presses anything, so that site receives the guest's IP address and browser details. We pass it only our site's address, never the invitation link itself.

Once the audio plays, that site may store its own data in the browser and show ads, under its own privacy policy. Invitations without an audio link load nothing from it.

8Cookies and browser storage

• A language cookie remembers whether you chose Arabic or English. It lasts a year.
• Sign-in cookies keep hosts, scanners and our team signed in. The account pages can't work without them.
• Analytics cookies and storage, as described above.
• The audio player's own storage, only on invitations that have audio.

9How long we keep data

• Your account, your events and their guest lists, replies, wishes and check-in logs are kept while your account exists, so you can come back to an event after it's over.
• When you delete an event, its guest list, replies, wishes, check-in logs and uploaded logo are deleted with it.
• When you ask us to close your account, we delete it and all its events within 30 days of your request.
• Deleted data can stay in our database backups for up to 30 days, until those backups are replaced.
• Session recordings are kept for up to 30 days, and other analytics data for up to 13 months.
• Names and numbers left in the announcement maker's form are kept.
• The log of account actions is kept for as long as the account exists.

10Your rights and choices

You can ask us to:

• show you the personal data we hold about you;
• correct it;
• delete it, or close your account;
• stop using it for something you didn't expect.

Hosts can edit or delete their guests' details and their events themselves, from the event's pages. A guest who wants their details changed or removed should ask the host who invited them; if that doesn't work, write to us and we'll help.

Send your request to support@jamaatna.net from the email address on your account, or tell us which event and invitation it's about. We answer within 30 days at the latest.

11Keeping data safe

Data travels encrypted over HTTPS. Database rules decide who sees each event: a host sees only their own events, and a scanner only the events they're assigned to. Invitation links and entry codes are long random or signed values that are hard to guess. No system is perfectly secure, so keep your password to yourself and tell us straight away if you think someone else has used your account.

12Children

Accounts are for adults organising their own events. We don't knowingly collect children's details, beyond a name a host may put on their guest list.

13Changes to this policy

If we change this policy, we update the date at the top of this page. If a change affects how we use data you've already given us, we tell hosts by email or WhatsApp before it takes effect.