Account-based access
Dataset access is tied to the signed-in buyer account so downloads stay traceable and supportable.
This page explains how AEXO protects buyer access, handles payments, stores account records, and presents its compliance posture in a factual way.
Dataset access is tied to the signed-in buyer account so downloads stay traceable and supportable.
Paddle processes payments so card details are handled by the billing provider rather than stored in the app.
Products are reviewed before publication so the catalog reflects the fields, pricing, and download path buyers should expect.
The business emphasizes public and verifiable source material instead of opaque or unverifiable data claims.
Operational data is kept in Firebase-backed services to support the site, accounts, and purchase records.
Security statements are kept factual and modest so buyers can use them in procurement review without overclaiming certifications.
AEXO keeps its security description grounded in what the product actually does: account-based delivery, controlled billing, public-source data, and a narrow retention footprint.
Request Security SummaryBuyer access is tied to the authenticated account and can be reviewed through the dashboard.
The site and supporting APIs are monitored through standard platform and hosting tooling so issues can be detected quickly.
Any claim about encryption, certifications, or audits should be added only when it is verifiable and current.
Account and purchase records are kept only as long as needed to support service delivery and support requests.
No. Billing is handled by Paddle, which keeps payment credentials out of the application database.
Access is tied to the authenticated account, and product pages point to a specific download URL when the buyer is allowed to retrieve the file.
No. The page only describes controls and operational posture that are actually present. Any formal certification should be added only after it is completed.