Security

Sellers connect Navexa to their stores and marketplaces, so we hold their order, product and inventory data and their buyers' shipping details. This page lists the controls we run today. It does not list anything we plan to do later. Our written policies are published in the Navexa Information Security Program.

1. Hosting and network

• Production runs on DigitalOcean managed Kubernetes in the SFO3 region (San Francisco, California). All seller and buyer data is stored and processed in the United States.
• The PostgreSQL database and the Valkey cache are DigitalOcean managed services on a private network. Their firewalls accept connections only from our production cluster.
• Public traffic reaches the API only through an HTTPS ingress. The web app is served as static files from Cloudflare Pages.
• Shipping labels and packing slips are stored in a private DigitalOcean Spaces bucket. Packing slips are deleted automatically after 7 days.

2. Encryption

• All traffic to the web app and the API uses TLS 1.2 or higher.
• Marketplace and store credentials (OAuth access and refresh tokens, API keys) are encrypted with AES-256-GCM in our application before they are written to the database.
• Buyer names, email addresses, phone numbers and street address lines on marketplace orders are encrypted the same way.
• DigitalOcean encrypts the managed database storage and its backups at rest.
• Production application credentials are kept encrypted with SOPS and are decrypted only when we deploy.

3. Access control

• Every API request is scoped to one seller account. A seller can only read and change their own data.
• Inside an account, team members get one of four roles: Read, Write, Admin or Owner.
• Sign-in is handled by Firebase Authentication (Google). Navexa never stores user passwords.
• Access to production infrastructure, the database, source code and our cloud accounts is limited to Navexa's founder. Two-factor authentication is on for every one of those accounts.

4. Payments

Card payments to Navexa are processed by Finix, a PCI DSS Level 1 service provider. Card details go straight to Finix. Navexa stores only Finix's payment-method references, never card numbers.

5. Development and monitoring

• Every code change runs our automated test suite in CI before it can merge.
• Production deploys happen only from tagged releases.
• Dependabot checks our Go, JavaScript and CI dependencies weekly for known vulnerabilities.
• Sentry reports backend errors to us as they happen.

6. Backups and deletion

• The database is backed up daily by DigitalOcean with point-in-time recovery. Backups are kept for 7 days.
• When a seller disconnects a marketplace, syncing stops immediately. 30 days later we delete that shop's credentials, orders, buyer details, products, inventory and label files, unless the seller reconnects first. Deleted rows leave our backups when those backups expire.

7. Incidents

If we confirm a breach of seller or buyer data, we notify affected sellers, and the marketplace the data came from (for example TikTok Shop), by email within 72 hours. The full procedure is in our incident response policy.

8. Certifications

Navexa does not currently hold ISO 27001 or SOC 2 certification. Our hosting provider DigitalOcean and our payment processor Finix publish their own certifications.

9. Reporting a vulnerability