A narrow request is a safer request.

Security model

Rerit is designed around explicit user action, minimum necessary input, separated account records, and revocable device access.

Desktop permissions

Rerit requires operating-system accessibility permission to read and replace selected text. It does not need access to entire documents or application databases. You can remove the permission from system settings at any time.

Rewrite transport

Selected text is sent over an encrypted connection only after the shortcut is invoked. Requests are authenticated and processed through controlled server endpoints.

Authentication

Website sessions use secure authentication flows. Desktop access uses device-scoped credentials that can be listed and revoked from the account page.

• Do not share sign-in links or device tokens.
• Revoke machines you no longer control.
• Keep the operating system and Rerit current.

Payments

Checkout and card data are handled by Paddle. Rerit receives subscription and transaction references needed to activate or manage a plan; it does not store full card numbers.

Operational controls

Rerit applies access controls, environment separation, validation at API boundaries, minimal logging, dependency updates, and deployment review. Sensitive configuration is kept outside source code.

Responsible disclosure

If you believe you found a security issue, avoid accessing other users' data or disrupting the service. Send a clear report through the contact page with reproduction steps and impact. We will acknowledge and investigate it.

Limitations

No online service can guarantee perfect security. This page describes current design boundaries and may be updated as the product and infrastructure change.