Security at ROAR Circle
What ROAR Circle does to keep your church’s records safe, in plain words. Each line is true in the app today; where something is still being checked, it says so.
Each church’s records are kept apart by the database itself
Every table that holds a church’s records carries that church’s mark, and the database (PostgreSQL row-level security, switched on and forced) shows a church only its own rows, whatever the app asks. The app signs in to the database as a limited user that cannot switch this off. Each new table must come with an automatic test that one church cannot read another’s.
People see only what their role allows
A page or action nobody has been given is locked by default. Phone numbers and email addresses are hidden from other members unless the church chooses to show them. Money records are seen only by the people the church chooses.
Two-step sign-in where it matters
The owner, administrators and anyone who handles money must use two-step sign-in (a code from a phone app after the password), set up within 14 days of their first sign-in. Anyone else can turn it on. ROAR Circle’s own support staff sign in the same way.
Encrypted on the way
Everything between your phone or computer and ROAR Circle travels encrypted (HTTPS), and browsers are told to use nothing else (HSTS). Backup copies are encrypted before they leave the server, with a key that is not kept on the server. Whether the live server’s own disk is encrypted at rest is being confirmed with our hosting company; this page will say so once it is.
Backed up every day, kept off the server, and tested
A full backup every night, more often on weekdays, and every hour on Sundays during the day. Encrypted copies go every day to two other storage companies, one in the United States and one in Western Europe, and a copy is kept on ROAR Circle’s own computer. On the 1st of every month the newest backup is restored automatically into a spare database and checked table by table. Daily copies are kept for 35 days, one a month for 13 months and one a year for 7 years.
What ROAR Circle’s own staff can do
ROAR Circle support does not use a church’s screens or read its records. Support can switch a church off or on, change its plan and invoices and, when the church asks, send a password reset to the church’s administrator (the link goes only to the administrator). Every support action on a church is listed for that church under Settings, Support access. Like any hosting company, the people who run the servers could technically reach the database; they do so only to keep the service running, to restore a backup, or when the law requires it.
A record nobody can change
The activity log shows who changed people, users and roles, every sign-in and every money entry. Nobody, not even an administrator, can change or erase a line; lines go only after 2 years, as the Privacy Policy says.
Your records are yours: export and deletion
On every plan, including the free one, the owner can download everything (one ZIP file with every record and file) and administrators can download spreadsheets at any time. A member can delete their own sign-in in the app; an administrator can erase a person for good, and that erasure is done again if a backup is ever restored. When a church leaves, its records are deleted within 30 days unless a law requires keeping them.
Children
A parent approves a child’s own sign-in. A chat that includes children needs two leaders before anyone posts. A child’s allergies and medical notes can be read only by their parents, the leaders of their room and the church’s safeguarding lead or deputy, and the database itself enforces it. AI helpers never read children’s records, and there is no face recognition.
Money
ROAR Circle never sees card numbers and never collects, holds or moves a church’s money. Members give through the church’s own bank, payment page, mobile money or cash; ROAR keeps the records.
No ads, no tracking, no AI training
There are no adverts and no tracking. A church’s data is never sold and never used to train AI.
If something goes wrong
If a church’s information is seen or taken by someone who should not have it, we tell each church affected within 72 hours of finding out: what happened, what information, what we have done and what it should do. We follow a written incident plan. Whether ROAR is working is shown at roarcircle.org/status, and on a status page kept away from our own server, at status.roarcircle.org.
Report a security problem
If you think you have found a security problem in ROAR Circle, please write to support@roarcircle.org with what you saw and how to see it again. Please do not read, change or delete another church’s records, and give us time to fix it before telling anyone else. We reply as soon as we can and tell you what we fixed.
The same address is in our security.txt file, where security researchers look for it.
What we do not have yet
- No outside security audit (such as SOC 2) and no outside penetration test yet. Every release runs our own automatic tests, among them checks that one church cannot read another church’s records.
- Whether the live server’s disk is encrypted at rest is being confirmed (above).
More in our Privacy Policy (what we keep, where, and for how long) and Data Processing Terms.