Operational context deserves careful boundaries.
Security is built into the application’s authorization and database model. Hosted configuration still requires verification before launch.
An organization is the data boundary
Business records belong to an organization. PostgreSQL row level security, server-side membership checks and tenant-bound foreign keys restrict access. Admins manage settings and invitations; agents coordinate operations; readers can view records.
Collect less, expose less
Traveler passports and payment-card information are not collected. Private pages are excluded from search indexing. Provider keys, billing secrets and privileged database keys are kept on the server.
Payment information stays with Paddle
Paddle Billing hosts the payment interface when enabled. Flight Ops verifies webhook signatures and processes notifications transactionally. A payment return URL cannot grant subscription access.
Retention and requests
Archiving stops monitoring. The supplied cleanup job removes archived monitoring records after 90 days, notification content after 30 days and audit records after 365 days. Contact contact@rankup.cloud for an access, correction or erasure request. Hosting regions, backup retention and operational controls must be confirmed before commercial launch.
Clear limits, no invented badges
No certification, uptime SLA or independent security audit is claimed. Please report a suspected security issue privately to contact@rankup.cloud without including passwords or traveler documents.
The next change deserves a clear response.
See how your team could handle it. No account needed.