AlgoZap Privacy and Retention Policy

Effective date: April 14, 2026

AlgoZap is a browser extension that helps users analyze online posts for manipulative or coercive rhetoric. This policy explains what information AlgoZap processes, how it is used, how long it is kept, and how deletion requests are handled.

1. Who operates AlgoZap

AlgoZap is operated by Christopher W. Mahl (also known as Anaximander Aletheia).

For support, privacy questions, or deletion requests, contact:

Email: anaxaletheia@proton.me

2. What AlgoZap does

AlgoZap allows users to:

• analyze pasted text
• analyze selected or highlighted text on supported sites
• receive a summary of persuasive or manipulative tactics
• receive suggested replies
• sign in by email
• use a free trial
• purchase prepaid credit packs for continued use

3. Information AlgoZap processes

A. Text submitted for analysis

When a user asks AlgoZap to analyze text, the submitted text is sent to the AlgoZap backend at:

https://algozap-api.anaxaletheia.com

AlgoZap does not store submitted analysis text in its Cloudflare D1 database during normal operation. Submitted text is processed to generate the requested analysis result.

B. Sign-in information

When a user signs in, AlgoZap processes:

• email address
• sign-in code request data
• sign-in code verification data

This is used to authenticate the user and issue a browser device token.

C. Device token

After sign-in, AlgoZap stores a browser device token locally in the browser. This token is sent with analysis requests to verify that the browser is authorized for the account.

D. Account and billing records

AlgoZap stores service records required to operate the product, including:

• users
• trial entitlements
• credit ledger records
• extension tokens
• usage events
• sign-in code records
• payment and fulfillment linkage records needed to grant prepaid credits

E. Usage metadata

AlgoZap stores limited usage metadata in the usage_events table, including:

• user ID
• timestamp
• input character count
• model name
• result status

AlgoZap does not store the full submitted text in D1 usage records during normal operation.

4. How information is used

AlgoZap uses information to:

• authenticate users
• verify browser authorization
• process analysis requests
• return results and suggested replies
• manage free trial access
• manage paid credit balances
• operate payments and credit fulfillment
• monitor service health and troubleshoot failures
• prevent abuse and unauthorized access

5. Third-party services

AlgoZap uses third-party infrastructure and AI services, including:

• Cloudflare Workers
• Cloudflare D1
• OpenAI API
• Stripe
• Resend

Text submitted for analysis is sent to AlgoZap’s backend and processed using OpenAI API services to generate analysis results and suggested replies.

Email sign-in codes are delivered using Resend.

Payments and prepaid credit purchases are processed using Stripe.

6. Local browser storage

AlgoZap may store the following locally in the user’s browser:

• browser device token
• account email
• trial summary
• credit summary
• most recently selected text, when needed for extension features

This local data is used only to make the extension function properly on that browser.

7. Data retention

AlgoZap retains different categories of data for different periods:

A. Usage events

Usage event records are retained for 30 days, then automatically deleted.

B. Revoked device tokens

Revoked device tokens are retained for 30 days after revocation, then automatically deleted.

C. Expired device tokens

Expired device tokens are retained for 30 days after expiration, then automatically deleted.

D. Sign-in codes

Sign-in code records are short-lived and are cleaned up automatically after expiration or after they are no longer needed.

E. Trial, account, credit, and payment linkage records

User account records, trial entitlement records, credit ledger records, and payment linkage records may be retained as needed for service operation, support, fraud prevention, abuse prevention, accounting, and valid deletion requests.

F. Activation code records

Legacy activation code records may still exist for operational or administrative purposes.

8. Deletion requests

Users may request deletion of account-linked records by contacting:

anaxaletheia@proton.me

When a deletion request is fulfilled, AlgoZap may delete records linked to the user account, including:

• usage events
• extension tokens
• user account record
• trial entitlement records
• credit ledger records
• sign-in code records

Some limited records may be retained where reasonably necessary for security, fraud prevention, abuse prevention, operational continuity, payment reconciliation, or legal compliance.

9. Data sharing

AlgoZap does not sell personal information.

AlgoZap does not share user data with advertisers.

User-submitted text is processed only as needed to provide the requested analysis functionality.

10. Security

AlgoZap uses reasonable technical measures to protect service data, sign-in systems, and billing flows. No internet-connected service can guarantee absolute security.

11. Children’s privacy

AlgoZap is not intended for children under 13, and AlgoZap does not knowingly collect personal information from children under 13.

12. Changes to this policy

This policy may be updated from time to time. If material changes are made, the updated version will be published with a revised effective date.

13. Contact

For support, privacy questions, or deletion requests:

anaxaletheia@proton.me