# Security and PCI

Card numbers are entered into Stripe's payment form and go straight to Stripe. OutwardOps never receives or stores them. The service runs on Google Cloud, separates each company's data in the database, signs people in through Firebase Authentication, and limits what staff can see and do with permission groups.

## How are card payments handled?

Guests and staff pay with Stripe's Payment Element, which Stripe serves from its own domain inside our checkout. The card number goes from the browser to Stripe. Our servers receive only Stripe's references (payment and refund IDs, and event notices through a signed webhook). Each operator company takes payments on its own Stripe account, connected to OutwardOps through Stripe Connect.

Because card data never touches our systems, we expect to qualify for self-assessment questionnaire A (SAQ A), the PCI DSS category for merchants whose payment pages are fully hosted by a PCI-compliant provider. Each operator is the merchant on its own Stripe account. We do not claim a PCI certification of our own. Stripe is a PCI Service Provider Level 1, which is Stripe's own published status.

## Where is the data hosted?

On Google Cloud, in the us-central1 region (Iowa). The API and web app run on Cloud Run. Data is in Cloud SQL for PostgreSQL 17. Passwords and keys are kept in Google Secret Manager, not in code. Marketing-site pages are served from Firebase Hosting.

## How is each company's data kept separate?

Company data is protected by row-level security, and the app connects as a role that cannot bypass it. Owners with access to several companies can see across them. Our automated tests run as that role against PostgreSQL on every change, so isolation is tested.

## How do people sign in?

Two-step verification (TOTP) is available to staff; it isn't required yet. Staff, owners and affiliates sign in through Firebase Authentication (Google account, email link, or email and password). Guests check out without an account. The API verifies the sign-in token on every request and checks whether it has been revoked.

## What can staff see and do?

Each person has a role (owner, admin, staff or affiliate) and belongs to a permission group, including a built-in crew group. A group switches individual permissions on or off, for example: view amounts, view private fields, cancel bookings, refund any amount, edit the catalog, edit company settings, manage staff, export contacts, view reports. Crew can be limited to their own trips and kept away from money. Affiliates see only what an operator grants them. The server enforces these permissions on every request, not just in the screens. Staff actions such as customer record edits are written to an audit log.

## Is data encrypted?

In transit: all traffic uses HTTPS (Cloud Run and Firebase Hosting; the site sends a Strict-Transport-Security header), and the database accepts only encrypted connections in production. At rest: Google Cloud encrypts stored data by default, which is Google's published behavior. We do not use customer-managed encryption keys.

## Are there backups?

The production database has daily automated backups (kept 14 days), point-in-time recovery (7 days) and deletion protection turned on. We have not published a restore-time target.

## Which certifications do you hold?

None yet. OutwardOps has no SOC 2 report or other third-party audit today, and we do not claim one. Stripe and Google Cloud hold their own certifications, published on their sites.

## How do I report a security problem?

Email info@outwardops.com with the details. We read every report. We do not promise a response time and do not offer a bug-bounty or legal safe-harbor program.

## Questions

Ask us in a demo, or write to info@outwardops.com.

Source: https://outwardops.com/trust/security
