Privacy Policy
Last updated: September 3, 2026
Block Your Addiction is designed to keep browsing rules private and local while using a small payment service only when a user chooses a paid temporary unlock.
Information stored in your browser
The extension stores the websites you choose to protect, blocking modes, schedules, settings, temporary unlocks, and related activity in Chrome's local extension storage. This information is used only to provide the blocking features you configure. The domains and URLs you protect are not sent to the Block Your Addiction backend.
Information sent to our payment service
When the extension registers with the payment service or uses a paid rule, it sends random installation and rule identifiers, the extension version, the configured payment amount and currency, the requested unlock duration, and payment status requests. These identifiers are not tied to a Block Your Addiction account because the extension does not require an account.
Payments
Payments are processed through Stripe Checkout. Stripe receives the payment and billing information entered on its hosted checkout page. Block Your Addiction stores Stripe transaction identifiers, amounts, currencies, statuses, and relevant timestamps so it can verify payments, grant the purchased temporary access, prevent duplicate processing, handle refunds, and maintain necessary accounting records. We do not receive or store full card numbers. Stripe's handling of payment information is governed by Stripe's Privacy Policy.
How information is used and shared
Information is used only to operate, secure, troubleshoot, and support the extension and its optional paid-unlock feature. We do not sell personal information, use it for advertising, or share it with data brokers. Information is shared with Stripe only as necessary to process and verify a payment, or when disclosure is required by law.
Retention and deletion
You can delete locally stored rules, settings, and activity by using the extension's reset function or uninstalling the extension. Payment records may be retained for accounting, fraud prevention, dispute handling, and legal obligations. To request deletion of eligible backend data, contact us using the address below. We may ask for the anonymous installation identifier needed to locate the records.
Security
Communication with the payment service and Stripe uses HTTPS. Payment confirmation is accepted only after server-side verification with Stripe. No method of storage or transmission is completely secure, but we use reasonable safeguards appropriate to the limited information processed.
Changes
We may update this policy when the extension's functionality or data practices change. Material changes will be disclosed through the extension, its store listing, or this page as appropriate.
Contact
Questions and privacy requests can be sent to francobetteo@gmail.com.