// short read on how the leaob page app deals with your data. no fluff, no legal theater.
leaob page — dev team, russia-based. app — this binary you're running. personal data — anything that fingerprints you. usage data — runtime telemetry. you — the operator.
credentials you push (name, email) + auto-capture (ip, device fingerprint, os, event stream, diagnostic signals).
run the service. ship patches. ping you when it matters. stay on the right side of the law.
zero sale. scoped vendor access under contract. affiliates. partners on joint ops. other users in public buffers. your explicit opt-in for anything else.
min viable duration. extended per legal. usage data cycled faster unless flagged.
processing may occur offshore. safeguards travel with the payload.
GET / PATCH / DELETE on your data — on request, served promptly. most self-service via app settings.
legal process. judicial orders. corporate transitions. credible safety events.
tls in transit. rbac in the stack. periodic audits. not bulletproof — best effort, not absolute.
not for ops under 13. accidental capture → purged on detection.
outbound links run their own stack. different policies apply.
revisions announced at the header. material changes broadcast before activation.
ping: rea.app.eg+root@gmail.com