abs
POLICY · PRIVACY

Privacy.

What we collect, what we don't, and which third-party services see what during private beta.

IN PLAIN ENGLISH
We collect what's needed to run readings — your account, the questions you ask, the parcels you research, and diagnostic traces. We don't sell anything. We don't use your readings to train foundation models.
§ 1.0

Who this is from

This page explains how Agentic Bylaw Systems ("ABS", "we") handles information when you use our website, the ABS application, or contact us by email.

ABS is currently operated as a sole proprietorship out of Halifax, Nova Scotia. The application is in private beta.

§ 2.0

What we collect

We collect three categories of information, all of them in service of producing a reading you can trust:

  • (a)Account information: name and email address (handled by our auth provider), and your acceptance of the Terms.
  • (b)Reading inputs: the parcel or address you're researching, the questions you ask the agent, and the agent's response history.
  • (c)Diagnostic data: timing, errors, and the agent's intermediate retrieval / reasoning steps — used to debug bad readings.
§ 3.0

How we use it

Account information is used to authenticate you and bill you (where billing is enabled on your deployment). Reading inputs and diagnostic data are used to produce readings, to investigate bad readings you report, and to improve the agent.

NOTEWe do not sell your information. We do not use the contents of your readings or your questions to train third-party foundation models.
§ 4.0

Third parties that receive your data

Operating ABS involves a small number of third-party service providers. Each receives only the data needed for the function they perform:

  • (a)Authentication: an identity provider handles account creation, email verification, and session tokens. They see your email address and authentication metadata.
  • (b)LLM inference: a third-party large-language-model provider receives the request payload — your question text and the bylaw fragments we retrieve — to generate the reading.
  • (c)Payments (when billing is enabled): a payment processor handles checkout. We never see or store your card details. If billing is not enabled on your deployment, the payment processor does not receive any data about you.

Each provider operates under its own privacy terms. We will tell you who they are if you ask.

§ 5.0

Where data lives, and for how long

Account, reading, and diagnostic data are stored in our application's database on a server located in the European Union. LLM inference calls leave our server to reach the model provider; the request payload (your question and the retrieved bylaw fragments) is included.

We retain reading history for the life of your account so you can re-open past cases. Deleting a thread from the app removes it from the live database. We do not currently publish a backup-purge SLA — during beta our backups are manual and short-lived.

§ 6.0

Your rights

You can request a copy of, or the deletion of, any data we hold about you. Email the request from the address associated with your account.

Beta means turnaround on these requests is hands-on rather than automated; we will respond as quickly as we can.

§ 7.0

Children

ABS is not intended for, and we do not knowingly collect information from, anyone under the age of 16.

§ 8.0

Changes

We will update the consolidation date at the top of this page when we change this policy. Material changes will trigger a re-acceptance prompt on next login, the same way the Terms do.

Questions about this policy: info@agenticbylawsystems.com.

Questions about this document? Email info@agenticbylawsystems.com.
END OF DOCUMENT