Privacy Policy

1. Data We Collect

• ▸Account data: email and authentication data needed to provide access and billing.
• ▸Usage & gateway logs: tenant/App ID, user identifier, model or service, method, route path, token counts, estimated cost, status, request/response byte counts, latency, and timestamp, depending on the route. The application log tables do not store AI prompt/response bodies or REST request/response bodies. Routed content is sent to the upstream service you configure; hosting and error-monitoring services may also process technical event and request metadata as described below.
• ▸Credentials you upload: third-party API keys, stored encrypted at rest (AES-256-GCM) and decrypted only server-side at call time. They are never returned to the browser — only a masked tail is shown.
• ▸Authentication and preference data: Supabase session cookies and a browser localStorage value that records your analytics choice.
• ▸Network and technical data: the application uses the request IP address for rate limiting; hosting and monitoring providers may process additional technical data under their own services.

2. How We Use Information

We use information to provide and administer accounts and subscriptions, route requests, enforce budgets, rate limits and quotas, display usage information, maintain and secure the Service, and provide support. When configured, optional product analytics run only after you accept them. We do not configure Gatekeeper for behavioral advertising. Contact us with a privacy question or request; we may ask you to verify your identity before acting.

3. Service Providers & Recipients

• ▸Supabase — database for configs, logs, and encrypted credentials
• ▸Upstash — rate-limit counters and operational markers for webhook idempotency and budget-warning email de-duplication
• ▸Vercel — application hosting; platform telemetry and log contents or retention depend on configuration not verified here
• ▸Stripe — payment processing for paid plans (handles your payment details directly)
• ▸Sentry — error and performance monitoring. The app configures masked browser replay for error sessions, with visible text masked and media blocked. Server-side events remove authorization, API-key, cookie, and Stripe-signature headers and redact request bodies on proxy routes. Error messages, stack traces, URLs, and technical context may still be processed.
• ▸Resend — transactional email delivery; receives your email address and message content, which may include plan, billing, and budget-warning details
• ▸PostHog — optional product analytics, initialized after you accept. Configured analytics may include your account user ID, email, plan and role, page views, and events with instance label, budget, or App ID properties; these are not anonymous events.
• ▸Upstream APIs you configure — receive the Customer Content and Credentials needed to process the request you route. Their own terms and privacy notices govern their handling; their practices can differ. Nextera makes no promise about their retention, training, or confidentiality practices.

4. International Transfers

Nextera is based in the United States. Service providers and upstream services may process information in other locations under their own terms and configurations. We have not verified or made a representation here about the locations or transfer mechanisms used for every provider; review their current privacy information before routing data. Nextera does not train its own models on Customer Content. Requests sent to third-party AI providers are subject to the provider’s current terms and practices; we make no representation about their training or retention.

5. Data Retention

A scheduled cleanup job is configured to delete application usage and gateway logs older than 180 days, administrative audit records older than 365 days, and monthly gateway quota counters older than 12 months. These windows depend on the cleanup job running successfully; records may remain longer if it fails. Closing an account does not immediately delete historical usage and gateway logs, which remain subject to the normal cleanup schedule. Saved credentials and tenant configuration are removed with the associated account data when account deletion completes. Account deletion does not trigger deletion requests to analytics, error-monitoring, email, hosting, or payment providers; information held by them is handled under their own policies. Stripe retains its own customer, subscription, payment, and invoice records under its policies and applicable requirements.

6. Security

Saved upstream credentials in the application database are encrypted with AES-256-GCM; inbound gateway keys are stored as hashes. Credentials are decrypted server-side when needed to make a routed request. Database access uses server-side credentials. Per-minute rate checks may fail open during a Redis outage, while database-backed budget and quota checks fail closed. No system is perfectly secure. We do not claim a security certification or guarantee; we will provide notices when required by applicable law.

7. Privacy Requests

You may contact us with questions or requests about information associated with your account. We may need to verify your identity before acting. Account deletion is available in Dashboard → Settings; when it completes successfully, it removes account and tenant configuration after linked subscription cancellation succeeds. Historical usage and gateway logs follow the retention schedule above. For other requests, email consulting.nextera@gmail.com. We do not currently publish a Data Processing Addendum.

8. Children & Sensitive Data

Gatekeeper is for adults aged 18 or older. Do not create an account or use the Service if you are under 18. Do not route protected health information (PHI), including information subject to HIPAA, through Gatekeeper.

9. Cookies

Supabase uses cookies for authentication. The browser stores your analytics choice in localStorage. PostHog initializes only after you accept analytics in the consent banner. See our Cookie Policy for details.

10. Changes & Contact

We may update this Policy and will revise the effective date for material changes. Questions or requests: Sol King Inc. d/b/a Nextera Consulting — consulting.nextera@gmail.com. Please do not email credentials, PHI, prompts, or request/response contents.