TILLAR TECHNOLOGIES
AI Reliability Apps Privacy Policy
Last updated: September 2, 2026
The AI Reliability family—Claim Checker, Compliance Overlay, Conversation Anchor, Drift Guard, FreshReceipt, Instruction Monitor, Knowledge Freshness Guard, Memory Consistency, Model Compare, Source Alerts, Work Audit, and the unified AI Reliability Suite—is published by Tillar Technologies LLC.
The service provides modular reliability checks including source/version monitoring, conversation anchors, evidence-grounding checks, instruction checks, model comparison, audit history, policy routing, human review, incident timelines, trusted-source labels, safe remediation suggestions, sensitive-data scanning, agent-action checks, and optional usage budgets.
Data we process
- Google account identifier, email, and display name used for account access.
- Identifiers, names, version numbers, and modification times for Drive files the user explicitly selects.
- Encrypted Google OAuth credentials needed to monitor those selected files.
- Device notification tokens used to send freshness alerts.
- Google Play subscription status and encrypted purchase token for entitlement verification.
- User-created anchors, instructions, policies, trusted-source labels, review decisions, incident records, audit events, and usage-budget records.
- Sensitive Data Guard stores check results and counts, not the raw text submitted to that guard.
What we do not require
The core freshness check does not require uploading or storing the contents of selected documents. FreshReceipt compares source version metadata and dependency receipts. Conversation Anchor does not require access to ChatGPT, Claude, Gemini, or another AI account; users may paste responses for checking.
Use and sharing
Data is used only to provide account access, Drive monitoring, notifications, subscription verification, support, security, and deletion. Google, Firebase, and Google Play process data as necessary to provide those functions. Tillar Technologies does not sell personal data.
Security
Production deployments must use HTTPS. OAuth and purchase tokens are encrypted at rest. Access is isolated by shared reliability account and user ID.
Retention and deletion
Account data is retained while the account is active. Deleting the account removes the shared AI Reliability user record and associated sessions, tracked sources, artifacts, dependencies, anchors, checks, policies, trusted-source records, human-review items, incident timelines, remediation proposals, sensitive-data check metadata, action-guard rules/checks, usage budgets/events, OAuth credentials, notification tokens, capabilities, and subscription records from the service database.
Contact
Privacy questions: james@tillartechnologies.com