Privacy

Privacy Policy

Last updated: May 12, 2026

This Privacy Policy explains how Arconath collects, uses, shares, protects, and retains information for Release Passport public pages, checkout, licensing, support, and customer runtime workflows.

1. Information we collect

We may collect account and contact information such as name, email address, company name, workspace identifier, role, support messages, and commercial contact details.

We may collect checkout, subscription, entitlement, license, registry-access, and billing status information. Payment details such as full card numbers are handled by the payment provider or Merchant of Record and are not stored by Arconath.

We may collect technical information such as IP address, browser, device, request logs, timestamps, diagnostics, product usage events, API activity, CLI metadata, and security or abuse-prevention signals.

2. Customer runtime and release evidence

Customer self-hosted runtime data may include release records, service names, deployment metadata, policy results, evidence summaries, connector health, runtime-check output, audit events, and report metadata.

Customer-owned infrastructure credentials, kubeconfigs, private keys, passwords, and tokens should be stored in the customer secret-management system and should not be submitted through public support, checkout, or contact forms.

3. How we use information

We use information to operate the website, provide checkout and subscription workflows, issue or validate entitlement, deliver package access, support customers, improve product reliability, prevent abuse, protect security, and comply with legal obligations.

We may use diagnostic and usage information to troubleshoot onboarding, package installation, checkout status, connector behavior, report performance, and public-safe contact requests.

4. Payments and commercial entitlement

Checkout and payment information is used to create payment sessions, verify successful payment events, activate paid entitlement, manage subscriptions, issue receipts, handle billing questions, and prevent fraud.

A created checkout session does not by itself activate a paid plan. Plan status changes after a verified successful payment event or authorized owner-issued entitlement is recorded.

5. Cookies, analytics, and local storage

We may use cookies, local storage, server logs, and analytics tools to keep sessions working, understand public website usage, detect abuse, measure reliability, and improve product experience.

Browser and analytics settings may allow you to limit some tracking. Some operational cookies or storage may be required for login, checkout, or console functionality.

6. Service providers and subprocessors

We may share limited information with service providers that help operate hosting, infrastructure, analytics, payment processing, email, support, security, monitoring, registry, and delivery workflows.

Service providers may process information only as needed to provide their services to Arconath, subject to their own legal and contractual obligations.

7. Third-party integrations

If you configure connectors or identity providers, Release Passport may exchange data with systems such as Git providers, CI systems, registries, Kubernetes, GitOps tools, log systems, metric systems, incident tools, security scanners, or OIDC providers.

You control the credentials, scopes, and configuration used for customer integrations. Third-party systems are governed by their own privacy practices and terms.

8. Security

We use reasonable technical and organizational measures intended to protect information against unauthorized access, misuse, loss, and alteration.

No system is perfectly secure. Customers are responsible for securing self-hosted deployments, network access, identity providers, backups, logs, secret stores, and registry credentials under their control.

9. Retention

We retain information only as long as needed to provide services, maintain accounts, process billing, deliver licenses and packages, meet legal obligations, resolve disputes, prevent abuse, and enforce agreements.

Customer self-hosted runtime retention depends on the customer deployment, configured storage, active license, and retention settings.

10. Data location and international transfers

Information may be processed in countries where Arconath, infrastructure providers, payment providers, or support providers operate.

Where required, we rely on appropriate safeguards, contractual terms, or other lawful transfer mechanisms.

11. Your choices and rights

Depending on your location, you may have rights to access, correct, delete, export, restrict, or object to certain processing of personal information.

To make a request, contact support@releasepassport.com. We may need to verify your identity and may retain information where required for security, legal, billing, or operational reasons.

12. Children

Release Passport is intended for professional and business use. It is not intended for children, and we do not knowingly collect personal information from children.

13. Changes to this policy

We may update this Privacy Policy as the product, legal requirements, or operational practices change. The updated date shows when the current version became effective.

14. Contact

For privacy, billing, legal, or support questions, contact support@releasepassport.com. Do not include secrets, private keys, tokens, kubeconfigs, or sensitive release evidence in public support email.