SEOnorita

SEOnorita · information

Account and data security

Practical account protection and reporting issues.

Version: 2026-09-07

Protect sign-in

Use a unique password of at least 12 characters and enable two-factor authentication. Save recovery codes separately. Review sessions and end those you do not recognize.

Telegram sign-in requires explicit linking to a verified account. Compare the browser code with the bot message and confirm only your own sign-in request.

Limit access

Grant members and API keys only the permissions and projects they need. Revoke departing members and rotate exposed keys. Integration secrets are not shown again after saving.

Anyone who receives a public note link can read that note. You can revoke sharing. Do not publish passwords, keys or personal data there.

Report an issue

Contact @ker4ik13 with the route, time, operation identifier and a safe reproduction description. Do not send other users' data or real secrets. Stop testing if it reaches another account or disrupts users.