Your identity remains yours.

Information used today

When you create an account, ArcsReach uses your name, email address and securely handled authentication information to create and protect your account. Passwords are handled by our authentication provider; ArcsReach does not display or store a readable copy of your password.

Why it is used

This information is used to verify your email address, sign you in, maintain your session, recover your account and keep private identity records separated between authorised accounts.

Contact and account requests

If you contact ArcsReach, we store the request type, your name, your reply email and the details you provide so the request can be reviewed and followed up. If you are signed in, the request is also linked to your account. Do not include passwords, recovery codes or other secrets.

Identity and access

Selecting a Person is never treated as proof that the operator is that Person. Household access, delegated access and private identity access are separate. Access does not automatically escalate from one kind to another.

Service providers

ArcsReach currently relies on Supabase for authentication and database services and Vercel for hosting and delivery. These providers process the limited information needed to operate and secure the service.

What is not part of the service yet

ArcsReach does not currently offer subscriptions, billing, Learning For All integration or Lilah functionality through this website. If future features require different information, this notice will be revised before those practices apply.

Your choices

You may choose not to create an account. If you do create one, use accurate details that you are entitled to provide and keep your sign-in information private. You can submit a requestfor privacy information, correction, account closure or identity and account support.

Submission starts a review; it does not immediately change or delete anything. ArcsReach may need to verify your identity and clarify the scope before completing a request. A formal retention schedule for operational requests requires review before wider public release.