Subprocessors and service providers

FirstReq runs on the retained Contabo, PostgreSQL, Redis, Docker, and Caddy infrastructure.

• Hosting and backups are restricted to approved operational purposes.
• Database and cache data remain inside the retained infrastructure boundary.
• Provider changes require owner review before production use.

Stripe processes paid registration and subscription billing when live billing is explicitly enabled by the owner.

• Paid access activates only after a signed Stripe webhook.
• Pilot applications do not create Stripe customers or subscriptions.
• Stripe live mode remains disabled until the owner approves production rollout.

Transactional email is used for magic links, account and billing notices, and allowed product notifications.

• FirstReq customer notifications use in-product and email delivery only.
• Transactional email cannot be repurposed for commercial outreach.
• Delivery retries are idempotent to reduce duplicate messages.

Official vacancy sources and approved company-data providers support evidence and company-quality workflows.

• Customer-visible opportunities require official-source evidence.
• Company datasets require recorded commercial-use approval before production use.
• Contact operations remain suppression-safe and owner-controlled.