FocusRuler

Privacy Policy

Last updated: May 2025

FocusRuler does not collect, transmit, or share any personal data. All information used by the extension stays on your device.

Data We Do Not Collect

FocusRuler does not collect, store on external servers, or transmit:

Browsing history or visited URLs
Page content or text you read
Clipboard contents
Personally identifiable information of any kind

Clipboard Access

FocusRuler requests the clipboardRead permission solely to power the Text Echo feature. When you copy text (Cmd+C / Ctrl+C) while the ruler is active, the extension reads the clipboard contents to display contextual references within the current page.

This data is held only in memory for the duration of your browsing session and is never written to disk, synced, or sent anywhere. It is discarded when you close the tab or navigate away.

Local Storage

Your display preferences (ruler height, blur intensity, overlay opacity, accent color) are saved locally using Chrome's built-in storage.sync API. This data is limited to your personal Chrome profile and is never accessible to any third party.

Permissions Summary

activeTab — Inject the ruler UI into the currently active tab only
scripting — Load the ruler when activated via keyboard shortcut
storage — Save your display preferences locally
clipboardRead — Read copied text for the Text Echo feature (on-device only)
host_permissions (<all_urls>) — Allow the ruler to work on any webpage, including local PDFs

Third-Party Services

FocusRuler does not integrate with any analytics, advertising, or third-party tracking services.

Children's Privacy

FocusRuler does not knowingly collect any information from children or any other users, as no data collection occurs.

Changes to This Policy

If this privacy policy is updated, the new version will be published at this URL. Continued use of the extension constitutes acceptance of the updated policy.

Contact

If you have questions about this privacy policy, please contact us at hokaka.dev@gmail.com or open an issue on the extension's support page in the Chrome Web Store.