Privacy Policy

Information we collect

When you create or use an account, we process account information such as your email address, account identifier, and the name or profile information you choose to provide. If you sign in with Google, Google supplies basic identity information permitted by the authorization flow, such as your email address, name, and profile image. We do not receive your Google password.

You may add information such as a company name or country to your profile. If you contact us, request a quote, or submit a support request, we process the name, email address, company (if supplied), topic, product reference, and message you submit.

The developer workspace stores information needed to provide its features, including workspace and project names, membership and role records, API-key metadata, product and license records, invoices or receipt snapshots, and support history. API keys are stored as hashes for verification; customer screens are designed to display key metadata rather than stored hashes or raw credentials.

For operational security and usage reporting, API activity may be recorded with fields such as the API key, organization or project identifier, HTTP method, endpoint, response status, response time, timestamp, and IP address where collected. Do not include passwords, payment credentials, or other sensitive information in project names, API keys, support messages, or API payloads unless the relevant product expressly requires it.

How we use information

We use information to create and secure accounts; authenticate users; initialize and administer workspaces; provide projects, API access, customer dashboards, support, and requested services; process quote and contact requests; generate and deliver requested receipts or invoices; and maintain service reliability.

We also use relevant records to prevent abuse, investigate security incidents, enforce access controls, troubleshoot errors, meet legal obligations, and protect the rights and safety of users and the service. We do not use account information to sell personal data or to serve third-party behavioral advertising.

Authentication and account security

Authentication is provided through Supabase and may include Google sign-in. Supabase processes the credentials or identity-provider response necessary to authenticate you and maintain your session. We use authenticated identity to scope access to your account and workspace; database access controls are also used to protect customer records.

Keep your sign-in method and any API credentials secure. You can sign out in the application and revoke API keys through the relevant workspace controls. Contact us if you believe your account has been accessed without permission.

Cookies, local storage, and similar technologies

The application uses browser storage that is necessary for its operation. Supabase authentication persists a sign-in session in browser storage so you remain signed in between page loads. The cart stores product identifiers and quantities in local storage; published prices are re-read by the server during checkout. A small preference cookie may remember whether the navigation sidebar is open.

We do not currently use third-party advertising trackers or a third-party behavioral analytics script in the web application. Browser settings can clear or block storage, but doing so may sign you out, clear your cart, or reset interface preferences.

Payments, receipts, and invoices

Card payments are processed through Stripe Checkout. Card details are entered directly with Stripe and are not stored by DevOps Playground. We retain order and invoice records, including product and price snapshots, payment status, currency, and transaction references, to provide your account history and support billing inquiries.

Payment processing is subject to Stripe's applicable terms and privacy notice. Do not submit payment credentials through the contact or support forms.

When information is shared

We use service providers to operate the application and deliver requested features. These may include Supabase for authentication and database services, Google when you choose Google sign-in, Vercel for hosting and delivery, and Resend for contact and other configured transactional email. Providers process information under their own terms and privacy notices and our service arrangements.

We may disclose information when required by law, to respond to valid legal process, to protect users or the service, to investigate suspected abuse or security incidents, or in connection with a business transfer. We do not sell personal information.

Retention and security

We retain account and workspace information while it is needed to provide the service and for legitimate operational purposes, including security, dispute resolution, and legal or accounting requirements. Retention periods can differ by record type and provider. Contact us to request account closure or deletion; some records may need to be retained where law permits or requires it.

We use access controls and other safeguards intended to protect information. No internet transmission or storage system can be guaranteed completely secure. You are responsible for protecting your account and promptly revoking exposed API keys.

Your choices and privacy rights

You can update profile details and manage workspace records through the application where those controls are available. You may stop using Google sign-in, sign out, or contact us to request access to, correction of, or deletion of personal information associated with your account.

Depending on where you live, you may have additional privacy rights, including rights to access, correct, delete, restrict, or object to certain processing, or to complain to a privacy regulator. We will review and respond to requests as required by applicable law and may need to verify your identity before acting.

International processing and children

Our providers may process information in countries other than the country where you live. Where required, applicable safeguards for international transfers are handled through the relevant provider arrangements.

The application is intended for business and developer use and is not directed to children. If you believe a child has provided personal information, contact us so we can review the request.

Changes to this notice

We may update this Privacy Policy as the application, our providers, or legal requirements change. The current version will be published on this page with its update date. If a change materially affects how information is handled, we will provide additional notice where required.