eotc.io
Privacy Policy
Last updated October 20, 2026 · Effective October 20, 2026
The short version
- Your church or community decides what it asks you and who sees it. We host it for them, take reasonable measures to protect it, and use it to run the Service.
- We do not sell your information, we do not show ads, and we do not use advertising or analytics trackers.
- Our servers and database are in Toronto, Canada. A few service providers help us, such as for email, text messages and payments.
- Card details are entered with Stripe and are not stored on our servers.
- You can see and correct your profile, download a copy of your information from your account, delete your account at any time, and ask us or your church for your information. Write to [email protected].
This summary is here to help; the full text below is what applies.
1. Who we are
eotc.io is operated by Alexander Maru, an individual in Ontario, Canada ("eotc.io", "we", "us"). It gives Ethiopian Orthodox Tewahedo churches and related communities ("Organizations") their own website, member area and tools, on the web and in our mobile apps (the "Service"). This policy explains how personal information is handled in the Service. It works together with our Terms of Service.
We are accountable for the personal information under our control and have designated a Privacy Officer who is responsible for our compliance with this policy. You can reach the Privacy Officer at [email protected].
2. Your church’s role and ours
Two parties handle your information, each for its own part:
- Your church or community is responsible for the information it collects about its members and others through its site: the profile questions it asks, its records (such as baptism, marriage and memorial records), giving, groups and units, meetings, care cases, prayer requests, spiritual-father links, its ledger and reports. It decides why and how that information is used and who in the Organization may see it. Under privacy laws it is the "controller" of that information, and we are its "processor" or service provider.
- We are responsible for the information we need to run the Service itself: your account and sign-in, security, fraud and abuse prevention, the public directory of Organizations, platform administration and support.
For questions about what your church or community collects, or to ask it for your information, please contact that Organization first; its contact details are on its site. We will help it answer, and you can always write to us at [email protected].
3. What we collect
| Kind of information | Examples | Where it comes from |
|---|---|---|
| Account and sign-in | Name, email address, phone number, password (stored only as a secure hash), preferred language, connected sign-in accounts (Google, Facebook, Instagram, X), one-time codes, devices you are signed in on | You; the sign-in provider you choose |
| Member profile | Christian (baptismal) name, date of birth, address, household and children, membership number and date, home unit, profile picture, and answers to questions your Organization chooses to ask | You; your Organization; a parent or guardian |
| Church and community life | Groups and units you belong to, chat messages, photos, files and reactions, posts and comments, meeting attendance, event RSVPs, training completion, documents | You; other members; your Organization |
| Religious and pastoral information | Sacrament records and certificates, memorials, your spiritual father (confessor) and private notes he keeps, prayer requests, care cases (which may include health or family circumstances) | You; clergy and staff of your Organization |
| Giving | Gifts, pledges, recurring gifts, campaigns, tax-receipt details, e-Transfer notices (sender name and email, amount, reference and message only). Card numbers are handled by Stripe and are not stored on our servers | You; Stripe; your Organization’s mailbox (if it connects one) |
| Organization administration | Ledger entries and receipts, reports and goals, roles and permissions, imported records, and data from tools your Organization connects (Google Workspace, UniFi, Level) | Your Organization and its admins |
| Technical and security | IP address, browser and device type, the time and kind of sign-ins and administrative actions, push-notification tokens for your devices, error logs | Your device and our servers |
| Messages to us | Anything you write to us, and our replies | You |
Some of this is sensitive: it can reveal your religious practice, and care cases may touch on health. Your Organization chooses whether to use those features, and they are designed so that access is limited to the people it authorizes. For example, a list of spiritual children is designed to be shown to the spiritual father, while others see counts. You and your Organization enter such information at your own discretion. As described in section 5, we may also access information where needed to operate, support or secure the Service or to comply with the law.
We do not use advertising, analytics or tracking tools, and we do not build profiles of you for marketing.
4. How we use it, and why
- To provide the Service you and your Organization ask for: your account, your Organization’s site, chats, calendar, giving, records and the rest. (Legal basis where it applies: to perform our contract with you, and on your Organization’s instructions.)
- To sign you in, verify your email or phone, and keep accounts secure: rate limits, detecting suspicious activity, and an audit trail of sensitive actions. (Our legitimate interest in a safe Service, and legal obligations.)
- To send you messages the Service needs, and the notifications you choose to receive.
- To answer your questions and give support.
- To keep the Service working and improve it, using technical logs, not your content.
- To comply with the law, such as keeping financial records, and to protect the rights and safety of people using the Service.
Where the law requires consent, for example for sensitive information or optional features, we or your Organization ask for it, and you can withdraw it at any time; withdrawing may mean a feature can no longer be offered to you. If we want to use your information for a new purpose, we will tell you and, where required, ask for your consent.
5. Who can see your information
- People in your Organization see what its settings and their roles allow. For example, members may see a member directory; clergy and staff with the right permissions may see records, giving or care cases. Your Organization’s admins can tell you who has access.
- Anyone on the internet can see what an Organization publishes on its public pages, such as its name, address, service times, events and blog posts. Member-only areas require sign-in.
- The Service is designed to keep each Organization’s information separate from other Organizations’.
- We and people acting for us may access information where needed to operate, maintain, secure and support the Service, to investigate misuse, or to comply with the law.
- Our service providers (section 6) process information for us under contract.
- We may disclose information where we believe the law requires or permits it, such as in response to a court order or other legal process, or to protect the rights, property or safety of people or the Service. Where we consider it appropriate and lawful, we will try to tell the affected Organization or person.
- If the Service, or the business of running it, is transferred to a new operator (for example a company we form), your information may move with it, and would remain subject to this policy unless you are told otherwise.
We do not sell personal information, and we do not share it for cross-context behavioral advertising.
6. Service providers and where data is kept
Our servers and main database run with DigitalOcean in Toronto, Canada. These providers help us run the Service:
| Provider | What it does | Location |
|---|---|---|
| DigitalOcean | Hosting of our servers and database, and its own short-term backups | Canada (Toronto) |
| Cloudflare | Network security and delivery, protection from attacks, custom domains, storage of uploaded photos and files, and our encrypted daily copy of the database | Global network; storage location chosen by Cloudflare |
| Resend | Sending email | United States |
| Twilio | Text messages with sign-in codes and account notices | United States |
| Expo, Apple and Google | Delivering push notifications to the mobile apps. A notification about a chat message or a reply may carry the author’s name and the first words of the message; you can turn message previews off for each device in the app | United States |
| Stripe | Card payments, into each Organization’s own Stripe account (Stripe acts under its own privacy policy) | Canada, United States and elsewhere |
| Google, Meta (Facebook, Instagram), X | Sign-in, only if you choose to use them | United States and elsewhere |
| Google Workspace, UniFi, Level, an email provider | Only if your Organization connects them; their credentials are stored encrypted | As chosen by your Organization |
Some providers are outside Canada, so your information may be processed in the United States or other countries, where it may be accessible to their courts and authorities. We aim to use providers that protect information to a standard comparable to Canadian law, under their contract terms. Where EU or UK law applies, transfers rely on adequacy decisions or standard contractual clauses.
When someone posts a link in a chat, our servers fetch that page to show a preview. The website being linked sees a request from our servers, not from you.
8. How long we keep it
| Information | How long |
|---|---|
| Your account and profile | Until you delete your account or your Organization removes you |
| Organization Data (records, groups, chats, documents and so on) | As long as your Organization keeps it, and until its site is deleted. A deleted site is closed at once and generally erased about 30 days later |
| Gifts and tax receipts | As long as your Organization needs them for its books, generally at least seven years as tax law requires. If you delete your account, gifts and pledges are kept without your name or contact details. Tax receipts already issued are kept as issued, with the donor’s name and address, because charities must keep copies of the receipts they issue; your email address is removed |
| Audit trail of sensitive actions | Generally two years (730 days; up to seven years for entries about gifts and receipts), then deleted automatically |
| Notifications shown in the Service | Generally 180 days, then deleted automatically |
| Messages you posted in chats | As long as the group keeps them. If you delete your account they remain in the group, shown as from a former member |
| Signed-in devices in the apps | Until you sign out, or generally after 90 days without use |
| Unconfirmed Organization registrations | Generally up to 48 hours |
| A spiritual father’s notes about someone who leaves him | Set aside, and generally deleted after 30 days |
| Backups | Our hosting provider’s backups of the database: 7 days. Our own encrypted daily copy of the database: generally 30 days. Then deleted |
| Data files you or your Organization download (Download my data, Export all data) | Kept for 7 days so they can be downloaded, then deleted |
When you delete your account, your profile, sign-in details, connected accounts, devices, group memberships and picture are removed, and your account is kept only as an anonymous placeholder so that existing records still make sense. Messages you posted in chats remain in their groups, shown as from "Former member". Records your Organization keeps about you, such as sacrament records, stay with it; ask the Organization if you want them changed. The periods above are typical; we may keep information longer where the law requires or permits, to resolve disputes, enforce our Terms, prevent fraud or abuse, or for security, and copies may remain in backups until they expire.
9. How we protect it
- Connections to the Service are encrypted (HTTPS/TLS).
- Our database, files and backups are encrypted at rest by our hosting providers.
- Passwords are stored only as strong one-way hashes (Argon2id). Credentials for connected tools are stored encrypted.
- Our servers are designed to accept traffic through our protected network, and limit repeated attempts to sign in or send codes.
- Access inside each Organization is role-based, can be limited to a department or center, and money workflows are designed to need a second person, so that no one approves their own ledger entry or report.
- Sensitive actions are recorded in an audit trail that users cannot edit through the Service.
We take reasonable measures to protect information, but no system is completely secure and we cannot guarantee the security of information. Please help by using a strong password and keeping your devices secure. Where required by applicable law, we will notify affected people, Organizations and privacy authorities of a breach of security, and keep the records the law requires.
10. Children
- You must be at least 13 to create an account, and under-18s need a parent’s or guardian’s permission.
- Children under 13 have no accounts of their own. A parent or guardian may add them as household members, and an Organization may keep records about them, such as baptism records, under its responsibility.
- For members under 18, a parent or guardian in the household chooses their spiritual father, and a priest receives the guardian’s contact details rather than the child’s.
- If you believe a child under 13 has created an account, write to [email protected] and we will take appropriate steps, which may include removing it.
11. Your choices and rights
Wherever you live, you can, subject to applicable law:
- see and correct your profile in your account;
- choose your notifications: the morning notification of the day’s feasts and fasts is on by default in the apps and can be turned off, message previews can be turned off for each device, and push notifications can be turned off on your device;
- delete your account at any time;
- download a copy of your information in each church, as a file, from your account (Download my data, once a day), or ask us for a copy, ask us to correct it, or ask what we do with it;
- withdraw a consent you gave; and
- complain to us or to a privacy authority.
In Quebec (Law 25), you may also ask that information be given to you or another organization in a structured, commonly used format; ask that we stop spreading information or remove links to it where the law allows; and be told about any decision made solely by automated means (we make none).
In the European Economic Area and the United Kingdom, you also have the rights to restrict or object to processing, to data portability, and to complain to your local data protection authority. Our legal bases are described in section 4.
In U.S. states with privacy laws, such as California, you have the right to know what personal information we collect and how we use it (this policy), to access, correct and delete it, and not to be treated differently for using these rights. We do not sell or share personal information for cross-context behavioral advertising, and we do not use sensitive personal information for anything beyond providing the Service. You may use an authorized agent; we will verify the request.
To make a request, write to [email protected]. We will handle requests as required by applicable law, generally within 30 days (or longer where the law allows, in which case we will tell you), and generally free of charge. We may need to verify your identity before acting, and we may decline or limit a request where the law permits, for example where it would reveal information about others or is clearly unfounded. For information your Organization is responsible for, we may refer your request to it.
12. Complaints
If you are unhappy with how your information is handled, please tell us first at [email protected]; we will look into it. You may also complain to:
- the Office of the Privacy Commissioner of Canada;
- in Quebec, the Commission d’accès à l’information;
- in the EU or UK, your local data protection authority, such as the UK Information Commissioner’s Office.
13. Changes to this policy
We will update this policy when the Service or the law changes, and post the new version here with its date. If a change is significant, we will give notice by email or in the Service, and ask for your consent where the law requires.
This document is provided in English. Any translation of it, by us or anyone else, is for convenience only, and the English version prevails.
14. Contact
Privacy Officer, eotc.io, Ontario, Canada. Email: [email protected]. For legal notices, see our Terms of Service.