Privacy Policy
1. Introduction
This Privacy Policy describes the categories of information that Aquinian (the “Service”), operated by FIA Labs, collects, how that information is used, and the choices available to you. Aquinian is currently in a closed private beta; this policy is a draft and remains subject to owner and legal review prior to public launch.
Aquinian is an intellectual formation tool. It is not an ecclesial authority, a priest, a confessor, a spiritual director, a canon lawyer, a therapist, a physician, or a lawyer, and does not provide sacramental, pastoral, medical, psychological, legal, or canonical advice.
2. Authentication Data
Access to the Service requires sign-in through a third-party Google authentication flow brokered by the Service’s authentication provider. From that flow, Aquinian receives and stores:
- Your email address.
- Your display name (as provided by Google).
- A stable internal user identifier generated by Aquinian.
- A server-side session token used to maintain your signed-in state, stored in an httpOnly, Secure cookie scoped to the Service.
Aquinian does not receive or store your Google password. The underlying OAuth credentials remain with the third-party authentication provider.
3. Prompts, Outputs, and Saved Work
The Service stores the following data so that you can review and re-use your work:
- The text of prompts that you submit to the Service.
- The structured outputs generated by the Service in response, including any refusal blocks, quotation cautions, identity summaries, and notices.
- The mode (e.g. Disputation, Doctrine Check, Natural Law, Cultural Diagnosis, Talk/Article Builder), rigor level, and tone selected for each generation.
- Any verification notes attached to a saved output, together with the verification status (verified, discrepancy, or pending) for each citation category.
- Timestamps indicating when each output was generated and saved.
Saved outputs are scoped to your user account. Other users cannot read your prompts, your outputs, your verification notes, or your settings through the Service.
4. User Settings
The Service stores your default mode, default rigor level, and default tone so that they can be applied automatically the next time you sign in.
5. Usage Records
To enforce per-user rate limits and the daily live-model generation ceiling, the Service stores a usage record for each generation request. Each record contains:
- Your internal user identifier.
- The mode of the request.
- Whether the request invoked the live large language model.
- Whether the request completed successfully.
- The character length of the submitted prompt.
- A timestamp.
Usage records do not contain the text of the prompt or the generated output. They are used to apply per-user limits and to show you a usage line on the Settings screen.
6. Server Logs
The Service’s infrastructure may generate ordinary server logs (for example, request paths, response status codes, error stack traces, and approximate timestamps) for operational and security purposes. These logs are not used to build advertising profiles.
7. Third-Party Processors
Aquinian relies on a small number of third-party processors to operate the Service:
- An authentication provider that brokers Google sign-in and issues short-lived session identifiers.
- A large-language-model provider that processes the prompt text and Aquinian system instructions in order to generate responses for the live modes.
- Database and hosting infrastructure that stores the data described in this policy.
Prompts submitted to the live modes are transmitted to the large-language-model provider for the sole purpose of generating a response. Aquinian does not sell your prompts, outputs, settings, or usage records.
8. Retention
Saved outputs, settings, and account records are retained for as long as your account remains active. Session tokens expire on a rolling basis and are deleted on logout. Usage records are retained for the time required to enforce rate limits and to provide aggregate operational metrics during the beta.
9. Your Choices
You may delete individual saved outputs through the History screen. You may sign out at any time. You may request deletion of your account and associated saved outputs by contacting the Aquinian operator through the channel provided to you with your private beta invitation. Deletion of authentication metadata held by the third-party Google sign-in flow is governed by the provider’s own policy.
10. Children
The Service is not directed to, and must not be used by, children under the age of thirteen (13) or any age threshold imposed by applicable local law. Beta access is restricted to adults aged eighteen (18) or older.
11. Security
Aquinian uses ordinary industry-standard measures to protect the data it stores. No system, however, can be guaranteed to be perfectly secure. You are responsible for securing the Google account used to access the Service.
12. Changes to This Policy
This Privacy Policy may be revised during and after the beta. Material changes will be communicated through the Service or by updating the “Last updated” date above.
13. Contact
For privacy-related questions or deletion requests, please contact the Aquinian operator through the channel provided to you with your private beta invitation.