Flymebase.

Service policies

Privacy notice

Effective 2 November 2026. These policies describe the implemented service and its operating boundaries.

Data processed

IAMC provides subject, name and email for sign-in. Flymebase stores memberships, plan contracts, key hashes, invitation hashes, usage, quotes, invoices and payment events. Integration secrets are encrypted in the project database.

Purpose and service boundaries

Data supports access control, conversion evidence, quota enforcement and billing. IAMC manages identity, Elpixe renders authenticated dashboards, Qrisbill processes subscription payments, and Frankfurter supplies public reference rates. Each service receives information needed for its function.

Retention

Request activity stores operation, status, latency, workspace/key identifiers and timestamps for 90 days. Quotes, financial and audit records remain for reconciliation and integrity rather than disappearing at plan expiry. Revoking a key preserves existing evidence.

Your controls

Rotate or revoke keys and invitations, restrict team roles and review IAMC remembered devices. Do not put secrets or personal information in labels or idempotency keys. Public operators must publish applicable data-rights contacts and retention obligations before commercial launch.