Privacy
Your information at Aletheca.
The public archive
Public request pages show the reviewed scope, status, available clock evidence, costs and published records. Incoming correspondence and extracted text need review before publication. Public correspondence entries show milestones; raw messages, contact details and delivery evidence stay private. Records selected for release are reviewed for information that needs to be withheld.
An embargo hides a request’s subject and scope until it expires; the existence of the request and aggregate activity can remain public. Docket votes, contribution totals and backer counts are shown in aggregate, without publishing the account identities behind them.
Account and operational information
Account contact details, payment details, unsubmitted drafts and private operational evidence are not part of the public archive. Authorized requesters and operators have separate access to the information needed to manage a filing. An agency or delivery provider receives the approved letter and the identity, recipient and return details needed to process it. Keep unnecessary personal information out of proposed scopes and uploads.
To limit repeated AI requests across servers, we retain a hash of the account identifier and up to eight recent attempt timestamps per account. Old timestamps are replaced when that account next uses the assistance. This limit record contains no prompts, answers or contact details and is not published.
Email-fetch tracking is not enabled. Aletheca does not place tracking pixels in agency or account messages. Delivery receipts and agency acknowledgements are recorded separately; neither is described as a human read.
Usage and performance
We use Vercel Web Analytics and Speed Insights to understand traffic and page performance. These tools can receive page URLs, referring sites, browser and device information, and performance measurements. Read Vercel’s Web Analytics privacy information and Speed Insights privacy information for their data handling.
App recommendations and referrals
Where enabled, Swapply shows recommendations for other apps and measures impressions and clicks. Its widget receives the page path, which may identify the public request being viewed. Requests to Swapply and resources displayed by the widget also expose ordinary network information, including your IP address and browser type.
Swapply caches recommendations and settings in browser session storage and remembers dismissals in local storage. A referral click identifier can also be stored locally for signup attribution within seven days. An expired referral record may remain in browser storage until it is cleared. Aletheca does not pass account or payment fields to Swapply and does not currently report successful signups; account creation happens at Thaumatica. See Swapply’s privacy policy for its processing and retention practices.
Third parties
The Thaumatica house handles authentication through Clerk and membership billing. Stripe processes request-scoped payments. Vercel hosts this site. Filing and correspondence services process approved letters, delivery details and incoming records for their respective email, fax, postal or portal functions.
Questions: hello@aletheca.com.