1. A separate database per person#
Every account has its own database file.
Version 1.0 · effective 9 November 2026
Every account has its own database file. Nobody else's rows are physically in it, so swapping in someone else's record number to read their journal is impossible by construction, not by a check that could be forgotten. There is one shared database — the feed and the rating — and it holds only what you published yourself.
2. Sign-in#
There are no passwords — nothing to steal.
There are no passwords — nothing to steal. Sign-in is a one-time code by email: it lives 10 minutes, burns on first use, and attempts and codes are rate-limited. A second factor (an authenticator app) with backup codes; an account with a second factor cannot bypass it through Google, Microsoft or Apple, and those accept only an email the provider has verified. A list of active sessions you can revoke. Session cookies are unreadable to page scripts and travel only over HTTPS.
3. Encryption#
All connections are TLS-only, and the browser remembers this for a year (HSTS).
All connections are TLS-only, and the browser remembers this for a year (HSTS). Broker keys, model keys and connection tokens are stored encrypted with AES-256-GCM and shown on no page; the secret addresses of bridges, the executor and TradingView webhooks are stored only as a hash — a copy of the database cannot be used to send trades through them. Nightly database copies are encrypted with AES-256-GCM before they leave for storage in the EU, and we check that they restore.
4. The application#
Requests that change data are rejected when they come from other sites; the application answers only on its own addresses; the server will not reach internal network addresses even if one is slipped in; upload sizes are capped; images are accepted only in safe formats; pages cannot be framed by another site.
Requests that change data are rejected when they come from other sites; the application answers only on its own addresses; the server will not reach internal network addresses even if one is slipped in; upload sizes are capped; images are accepted only in safe formats; pages cannot be framed by another site. Broker connections read only wherever possible — with an investor password or a read-only token.
5. Server and access#
The server is in Germany (Hostinger), with only web ports open to the outside.
The server is in Germany (Hostinger), with only web ports open to the outside. Only the operator has access to the server, and enters a specific account's data only at your request to support or when the law requires it. There is no web admin panel at all — nothing to brute-force.
6. If something happens#
If a breach threatens your rights, we will tell you and the supervisory authority within the time the law requires — what happened, which data was affected and what to do.
If a breach threatens your rights, we will tell you and the supervisory authority within the time the law requires — what happened, which data was affected and what to do. If a service key leaks, we revoke it with the provider first and investigate after.
7. Reporting a vulnerability#
Found a vulnerability — write to security@aqrevi.com.
Found a vulnerability — write to security@aqrevi.com. Please do not touch other people's data, do not disrupt the service, and give us reasonable time to fix it before publishing. We do not pursue people acting in good faith. There is no paid bounty programme yet. The same address is in /.well-known/security.txt.