Privacy notice
Last updated: November 15, 2026.
iSood helps wards and branches organize missionary meals. Here we explain, without legalese, what data we use, what we use it for, who can see each item and how you can ask us to correct or delete it.
1. What data we use
From families who book meals:
From the meal organizers: name, email and, if they want, a profile photo. From the unit: the address of the ward or branch (the meetinghouse), with its spot on the map, if the organizer marks it. The password is stored securely by the sign-in service; no one at iSood can read it. If the iSood team blocks an account, we keep the reason for as long as the block lasts.
From people who write through the “Email” form in the footer: name, email, subject and message. This isn’t kept in iSood’s database: it goes by email to the team’s inbox (contato@isood.org, on Zoho Mail) and is used only to reply.
To keep everything in order, we also record the change history of bookings (what changed and when) and, in a separate activity log, the iSood team’s actions in the admin panel, organizers’ sign-ins to iSood (date and time), profile name changes and unit deletions (see items 3 and 6). Nothing else is requested.
- name and phone number;
- the meal address and, if the family or the organizer marks it, the exact spot on the map;
- a note, if the family wants to add one (for example, a restriction);
- the booked days and, when there is one, the reason for a cancellation or a date change;
- the date and time when the family gave consent.
2. What we use it for
We don’t sell data and we don’t show ads. The family pages have no analytics tools at all; the OpenStreetMap map only loads when the person finishes typing the address or taps “Show on map”. On the home, sign-in and dashboard pages, we use Google Analytics to count visits and improve the service, only if you accept (see item 5).
- Building the unit’s meal schedule and showing which days are open.
- Letting the organizer reach the family (by phone or WhatsApp) when needed.
- Preparing the calendar that organizers hand to the missionaries.
- Showing the missionaries where the meal is: the PDF includes the address with an “Open in maps” link, which opens Google Maps only when they tap it.
- The “Check on Google Maps” and “Open in maps” links, in the forms and in the dashboard, open Google Maps with the address or the marked spot. Google only receives this data if the person taps the link.
- Emailing the organizers when there is an urgent cancellation.
- Protecting the system against abuse, such as fake bookings in bulk.
3. Who sees what
Each unit only sees its own data. Access to each item is as follows (what the iSood team sees and does is explained right below the table):
| Data | Public calendar (group link) | The family itself (private link) | Unit organizers | Missionaries (exported calendar) | iSood team (see below) |
|---|---|---|---|---|---|
| Whether a day is open, booked or unavailable | Yes | Yes | Yes | Yes | Yes |
| Family name | Only if the unit turns it on | Their own | Yes | Yes | In the schedule and the history |
| Phone number | Never | Their own | Yes | Yes | Never |
| Meal address (and the spot on the map) | Never | Their own | Yes | In the PDF, with the map link | Never |
| Ward or branch address (the meetinghouse) | Only the area (about 1 km), for the map | Only the area (about 1 km), for the map | Yes | No | Only the spot on the map |
| Note (e.g., a restriction) | Never | Their own | Yes | Yes | Never |
| Reason for a cancellation or date change | Never | Their own | Yes | No | Never |
| Family’s private link | Never | Their own | Can create and cancel it, but can’t see a link again once it’s been sent | No | Never |
The iSood team (admin panel)
The volunteers who run iSood have a separate admin panel, with its own sign-in, to support units (for example, when an organizer loses access), prevent abuse and keep an eye on how the service is used. Each team member can only see and do what their role allows.
- Organizer accounts: the team sees the name, email, profile photo, when the account was created and confirmed, the last sign-in and which units the person looks after. They can create accounts, correct the name and email, block and unblock accounts (a blocked account can’t sign in to iSood and stops receiving email alerts) and help change the password (by setting a new one or emailing the person so they can create another). No one can see the password.
- Units: the list of wards and branches and where each one is on a map, based on the spot marked by the organizer. The written ward address is not shown to the team.
- Schedules: the team can look up a unit’s meal schedule, with the booked days and only the family name. Phone numbers, addresses, notes and reasons never appear. Each lookup is logged.
- History: the units’ change history (what changed and when) is shown with phone numbers, addresses, notes, emails and reasons hidden.
- Support conversations: when an organizer opens a conversation on the Support screen of the dashboard, the team reads the subject and messages and replies there. The conversation belongs to the unit: all organizers of that ward or branch can see it. It is kept for as long as the unit exists and is erased together with the unit. We ask that no one write phone numbers, addresses or other family data in it. Email alerts only include the conversation number and subject, never the text of the messages.
- Activity log: the team’s actions in the panel (with what changed), each schedule lookup, organizers’ sign-ins to iSood (date and time), profile name changes and unit deletions go into a separate log. It is kept for 90 days (the team can set this period anywhere from 30 to 365 days) and then erased automatically.
4. Sensitive data and consent
Knowing that a family belongs to a ward or branch reveals their religion. Brazil’s General Data Protection Law (LGPD, Law 13.709/2018, art. 5, II) calls this sensitive personal data and requires special care (art. 11).
That’s why, on their first booking, the family reads a prominent notice and only continues if they agree. We keep the date of that consent. The family can withdraw consent at any time by asking for their record to be deleted (see item 7).
5. Services we use
iSood runs on services from companies based outside Brazil. Even with the data processed in São Paulo, these companies handle data on our behalf:
Your browser may also store some information on your own device to make your next visit easier, such as the organizers’ sign-in session, the family’s details so they don’t have to type them again (name, phone number and the address text, never the spot on the map; the form says so and lets you erase the remembered address) and your answer to the analytics notice.
- Vercel: hosts the website and the program that receives requests (data is processed in São Paulo).
- Supabase: stores the database and the organizers’ sign-in (servers in São Paulo).
- Resend: sends the emails: account confirmation, invitations, urgent cancellation alerts and contact form messages to the team.
- Zoho Mail: hosts the team’s inbox (contato@isood.org), where contact form messages arrive.
- Upstash: stores temporary counters that prevent abuse. They use a masked version of the internet (IP) address, never a name or phone number, and erase themselves.
- GitHub: stores iSood’s code and the daily backups, which are encrypted before they leave our system.
- Cloudinary: stores and serves the images uploaded by organizers (profile photo and calendar image) and the PDF copies of calendars that an organizer chooses to save in iSood. These PDFs are private: they only open through a temporary link requested by an organizer of the unit.
- OpenStreetMap Foundation (OSMF, in the United Kingdom), for maps: shows the map for checking the address spot and searches that map for the typed address (the Nominatim service). As soon as the person finishes typing the address (leaves the field or stops typing for a moment), or when they tap “Show on map”, the typed address, the device’s internet (IP) address and the website address (without the page path) reach the OpenStreetMap Foundation, and the map appears so the person can check the pin. If the ward has its pin marked, the search also includes an area of about 100 km around the ward’s area (the center rounded to about 1 km, never the ward’s address), only to find the address faster. An address the device remembered is not sent on its own: only if the person changes the text or taps “Show on map”. The map of units in the iSood team’s admin panel (item 3) also comes from it, but it only draws pins that are already marked: it doesn’t search for any address, and the map images reach it only with the internet (IP) address of the team member’s device and the website address (without the page path). Other than that, nothing is sent to it.
- ViaCEP (in Brazil) and Zippopotam (in other countries), for ZIP/postal code lookup: fill in the street, neighborhood, city and state from the ZIP or postal code typed in the address. Only the code reaches them, along with the device’s internet (IP) address: never the name, phone number, house number or link. The code is only sent when the person finishes typing it; a code already saved or remembered on the device is not sent on its own.
- Google (Google LLC), for Google Analytics: measures, only if you accept, how the home, sign-in and dashboard pages are used. It never runs on the family pages. Details right below.
Usage statistics (Google Analytics)
You can change your mind at any time. When you tap the button, we delete the Google Analytics cookies from this browser and forget your answer. Until you answer again, nothing is measured. The notice will show up again when you open the home page, the sign-in page or the dashboard.
- Where: only on the home page, the sign-in and sign-up pages, and the organizers’ dashboard. Never on the public calendar, the family page or this notice: those pages have no third-party services at all.
- When: only after you tap “Accept” on the notice at the bottom of the screen. The legal basis is your consent (LGPD, art. 7, I). If you decline, Google Analytics isn’t even loaded.
- What is measured: which screens are opened and when, with the codes in the address replaced by a placeholder (for example, “/app/u/:id/familias”), and technical details of the visit, such as the type of device and browser, the language, the screen size and the approximate region. To count visits from the same device, Google stores a random number in cookies in your browser (the ones starting with “_ga”) for up to 13 months.
- What is never sent: names, phone numbers, emails, notes, the families’ links or what appears on the screens. Advertising features and “Google signals” are turned off.
- Where the data is kept: Google may process this data outside Brazil, including in the United States. We ask Google to keep the detailed data for the shortest period it offers (2 months).
6. How long we keep it
- Data is kept for as long as the unit uses iSood to organize meals.
- When a family’s record is deleted, the record (with the phone number and address), their bookings and their links are removed from the system. The unit’s change history still records what was done and when, with the name and notes at the time (the address never goes into the history, only the fact that it changed), and is only erased together with the unit.
- PDF calendars saved in iSood are kept until an organizer of the unit deletes them. They show the name, phone number, address and note of that month’s families, including a family that later asked for their record to be deleted; so, when handling a deletion request, the organizer should also delete any saved files that mention that family.
- When a unit is deleted, all of its data is removed from the system, including the change history, the calendar image and the saved PDFs. Only a record of the deletion remains in the activity log: the unit’s name and type, how many calendars, families, bookings and organizers it had, who deleted it and when. No family names or phone numbers. Earlier activity log entries that mention the unit (such as schedule lookups) follow the retention period in the item below.
- The activity log (iSood team actions in the admin panel, schedule lookups, organizer sign-ins, profile name changes and unit deletions) is kept for 90 days and then erased automatically. The team can set this period anywhere from 30 to 365 days.
- Backups are erased automatically within 30 days.
- The counters used against abuse erase themselves after a short time.
7. How to ask for a correction or deletion
You can ask to know what data of yours is stored, have it corrected or deleted, and also withdraw your consent. The quickest way:
With the private link, the family can also view, change and cancel their own bookings.
- Talk to the meal organizer in your unit. They can correct or delete the family’s record directly.
- Or write to contato@isood.org, telling us your unit and the name used for the booking.
8. How we protect the data
- Always a secure connection (HTTPS).
- Families’ private links are not stored in full: we only keep a “fingerprint” of each one, which can’t be used to recover it. That’s why not even the organizers can see them again.
- Each unit can only access its own data.
- Exported calendars are created on the organizer’s device. They are only stored if the organizer chooses “Save to iSood”: then the PDF is kept in Cloudinary as a private file, with no public address. To download it, an organizer of the unit requests a link that is valid for 10 minutes, and each request is recorded in the history.
- The profile photo and the calendar image are public to anyone who has their address (like any image on a website), but they contain no family data.
- The iSood team’s admin panel has its own address and no analytics tools (Google Analytics never runs there). From outside, it only loads map images (OpenStreetMap Foundation) and profile photos (Cloudinary). Each team member can only access what their role allows, never sees families’ phone numbers, addresses or notes, and their actions are logged.
9. Who looks after the data and how to contact us
The data of each ward or branch is used by that unit’s meal organizers. iSood, run by volunteers, keeps the system working and handles requests about personal data. For this, the team uses the admin panel described in item 3.
Questions, requests or complaints: contato@isood.org.
10. Unofficial website
iSood is a volunteer project and is not an official website of The Church of Jesus Christ of Latter-day Saints. It is not run, sponsored or approved by the Church and does not use its logos or images.