TallyQuill / policies

Privacy Policy

This page describes data paths visible in TallyQuill's current application. It does not fill in provider or business practices that the app does not specify.

Who this page identifies

TallyQuill is the product name used by the app. The app does not state the operator's legal entity name, mailing address, or governing jurisdiction. The complete list of service providers and their data terms is also not specified here.

Account and session information

Creating an account uses your name and email address. Email-and-password sign-in and email verification are configured. Authentication records include password credential data. Session records have an expiry time and optional fields for an IP address and user agent. The app sends verification email through the Polsia email proxy; provider-side handling and retention details are not specified by the app.

Financial uploads

A signed-in account can submit a PDF, CSV, or .xlsx file up to 50 MB. The browser sends the file to the app's upload route. The route stores the file bytes and records the filename, media type, size, status, and timestamps in PostgreSQL. The route returns upload metadata and status, not file contents, and does not create a public file URL. Upload requests and reads are scoped to the signed-in account.

The app has one current upload record per account. Submitting another file updates that current record, and the workspace does not show upload history. There is no in-app upload deletion or account-deletion path. The app publishes no retention or deletion schedule: it does not specify when replaced file data, account data, or database-backup copies are deleted.

Payments

When you start checkout, the app passes your signed-in email address and offer and purchase metadata through the Polsia billing API to hosted Stripe Checkout. The app's purchase record contains the offer, status, checkout session ID, and timestamps; that record has no card fields. This describes the app's own record and does not specify all payment-provider processing or retention practices.

Optional visitor analytics

If a deployment provides POLSIA_ANALYTICS_SLUG, the app creates a random visitor ID in local storage and sends a page-load pixel to the Polsia analytics endpoint. Platform-side analytics use and retention are not specified by the app.

File processing and AI

In the current app code, the upload route stores a file and returns its status. No in-repository processing job, analysis route, or model call is present. This is a description of the inspected app flow only; broader provider practices and any provider-level AI-training use are not specified by the app.

Questions

Questions about this page can be sent to tallyquillfinance@polsia.app.

See also the Terms of Service.