Privacy Policy

Last updated October 30, 2026

Quorasen, LLC (“Quorasen”, “we”) helps a building or community account for everyone during a safety incident. This page says plainly what information that involves. We do not sell personal information, we do not run advertising, and we do not track people across the web.

Who is responsible for member information. A building (the people who run it) chooses who is on its roster and uses Quorasen to message them. For that information, the building decides what is collected and why, and Quorasen handles it on the building's behalf. If you are on a building's roster and want your information corrected or removed, ask the person who runs your building first; you can also write to us and we will help.

What we collect

Administrators and Managers (the people who run a building)

Name, email address and, if they choose to be an incident contact, a phone number.
If they sign in with Google, we receive their verified email address and name from Google, and nothing else from their account. Otherwise they sign in with a link or code we email them.
Sign-in records: a hashed form of the email address, the time, and whether it worked. We do not keep IP addresses for sign-in.

Members (the people on a building's roster)

Name, mobile number and room or unit, as entered by the people who run their building, and an email address if they add one (used only to send that person their own check-in link).
What they report or answer during an incident (for example "safe", "away" or "help"), where they say they are, and when.
Members do not create an account and do not sign in. They use a private link we send them.

Organizations that register as a text sender, and their authorized person

The organization's legal name, EIN (tax ID), address and website, and the authorized person's name, job title, email address and phone number.
When the authorized person confirms the sender, we record the time, the wording they agreed to, and the IP address and device they used, as proof of who agreed. This is the one place we keep an IP address.

Records that someone agreed to receive texts

The time, the wording they were shown, their reply (such as YES or STOP), and a one-way keyed hash of their phone number so the record can be found if they ask. These records hold no name and no phone number.

Visitors to quorasen.com

Page views and where visitors come from, counted by Cloudflare Web Analytics. It uses no cookies and stores no personal information about individual visitors.

How we use it

To run the service: confirming who is safe, sending alerts and check-in requests by text, showing the people who run a building a live picture of an incident, and keeping a record of what happened.
To sign Administrators and Managers in and keep their accounts secure.
To register an organization as a text sender with the phone carriers, and to keep a record that people agreed to receive texts.
To email Administrators and Managers about their account (invitations, role changes, sign-in links).
To keep the service working and safe, and to fix problems.

We do not use anyone's information for advertising, and we do not sell or rent it.

Who can see a building's information

The people who run a building see its roster and incidents. If a building belongs to an organization that pays for several buildings, that organization's Owners and Organization Managers can see only what the building agreed to share: counts only, the roster, or full detail. Every look at the roster or full detail is logged, and the building's Managers are told.

Who else handles it

We use a small number of providers to run Quorasen. They process information only to provide their service to us.

Cloudflare: hosting, data storage, email delivery and website analytics.
Twilio, The Campaign Registry and mobile carriers: delivering and receiving text messages, and registering the sender of those texts. For registration they receive the sender's business details and its authorized person's contact details, never a building's members. The phone numbers texts are sent from belong to Quorasen; they are held in our account with Twilio and are released when a building's information is deleted.
Google: only if an Administrator or Manager chooses to sign in with it.
Paddle, our payment provider: when paid plans begin, for billing. We do not store card numbers.

We may also disclose information if the law requires it, or to protect someone's safety.

Text messages

Quorasen sends safety notifications and check-in texts, and test and account texts for the people who run a building. Each person agrees by replying YES to the first text they receive; nothing else is sent before that. Message frequency varies. Message and data rates may apply. Reply STOP at any time to stop, and HELP for help. How the program works, and the exact wording people agree to, is on the Text Message Program page.

No mobile information will be shared with third parties or affiliates for marketing or promotional purposes.Information is shared with the providers that deliver the messages and support the service, such as customer service. Text message opt-in data and consent are not shared with any third parties. We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes.

How long we keep it

A building's information is kept while the building uses Quorasen.
When a building stops, names, phone numbers and private links are wiped straight away, and the rest of the building's records are deleted after a year.
When a building removes a member, they stop receiving messages and their link stops working.
Sign-in records are kept for a limited time and then deleted.
Records that someone agreed to receive texts, and records of who confirmed a text sender, are kept for four years so we can show them if a carrier or the person asks. They hold no names or phone numbers of members.
The record of a sender's confirmation also keeps the details that were confirmed (the organization's legal name, EIN and address, and its authorized person's name, title, email address and phone number) for the same four years, because a carrier may ask us to show them.
A record of who changed what on an account (for example a role or an access level) is kept without any member information.

How we protect it

Everything travels over encrypted connections.
Each building's data is kept in its own separate store, so one building cannot see another's.
Sign-in tokens and codes are stored only as hashes, and the phone number in a consent record is stored only as a keyed one-way hash.
Members' links are private and can be revoked by the people who run their building.

No system is perfectly secure, but we design Quorasen to collect the least it needs and to keep it separate.

Your choices

You can ask us what we hold about you, to correct it, or to delete it. If you are a member, start with the person who runs your building. Write to hello@quorasen.com and we will respond.

Reply STOP to any text to stop receiving texts, and HELP for help. Stopping texts may mean you are not reached by text during an incident, so tell the person who runs your building.

Children

Quorasen is for adults who run and live in buildings and communities. It is not directed at children under 13, and we do not knowingly collect their information.

Changes

If we change this policy in a way that matters, we will update the date above and, for the people who run a building, tell them by email.

Contact

hello@quorasen.com