Information we process

Account and authentication records such as your name, email address, password representation, sessions, team membership, and access permissions.
Workspace, project, stack, application, database, domain, deployment, build, runtime, configuration, log, metric, and resource-status information needed to operate your workloads.
Technical request and session metadata such as IP address, user-agent information, timestamps, request paths, and security or audit events.
Subscription, transaction, invoice, usage, and payment-provider reference information. Payment providers handle payment data according to their own terms.
Support and communication information that you send to StackShift, including email, bug reports, feedback, and business enquiries.

How we use information

To create accounts, authenticate users, manage teams, enforce permissions, and protect sessions.
To deploy, provision, monitor, troubleshoot, recover, and otherwise operate projects, stacks, applications, databases, and related platform resources.
To provide billing, usage reporting, support, diagnostics, fraud prevention, abuse prevention, security operations, and auditability.
To investigate incidents, enforce platform rules, respond to lawful requests, and protect StackShift, customers, and third parties.

Operational access and workloads

StackShift needs limited operational access to perform actions customers request, such as deploying workloads, checking health, restarting services, provisioning databases, connecting domains, and showing logs or metrics.This access is for operating and supporting the platform. Customers remain responsible for the content, code, credentials, dependencies, and third-party services used by their workloads.

Secrets and sensitive configuration

Selected stored credentials and sensitive configuration values are encrypted when the platform encryption key is configured for that storage path; this is not a claim that every stored data field is encrypted by the same mechanism.
Secret values are masked in product surfaces where masking is implemented and should not be placed in logs, screenshots, support messages, or chat prompts.
Customers are responsible for rotating credentials that may have been exposed outside the platform.

Sharing and service providers

StackShift may use infrastructure, storage, payment, email, DNS, monitoring, security, and support providers to operate the platform. The active production provider set depends on verified deployment configuration; optional code integrations are not automatically treated as active subprocessors.We may disclose information when required by law, to investigate abuse or security issues, to protect users and the platform, or in connection with a business transaction.

Retention and deletion

We retain records for as long as needed to operate StackShift, maintain backups, support billing, prevent abuse, investigate security events, resolve disputes, and meet legal or accounting obligations. The current implementation does not support a single universal deletion period for every record type.Deleting a project, resource, or account may not immediately remove backups, audit records, billing records, security records, or other records that must be retained for operational or legal reasons.

Your choices and requests

Update account information, revoke sessions, remove credentials, and delete supported resources through the product where those controls are available.
Contact us to request access, correction, export, or deletion of personal information. We may verify the request and apply operational or legal limits.
Manage non-essential browser storage or marketing communication preferences where the relevant controls are available.

Contact

For privacy questions or privacy requests, contact jesse@stackshift.cloud.

Privacy Policy