Privacy Policy

This policy explains what we collect when you use SandyWP, why we collect it, and the choices you have. We keep it short because we collect little. It covers the SandyWP website and app, and includes a dedicated section for the SandyWP for Slack app.

What we collect

• Account data. If you sign up, we store your email address and, for password accounts, a securely hashed password. If you sign in with Google, we store the basic profile your provider returns.
• Sandbox data. Metadata about the sandboxes you create — names, WordPress/PHP versions, status, and expiry. Disposable sandboxes and their contents are deleted automatically when they expire.
• Billing data. If you upgrade, payments are handled by our payment provider. We store a customer reference and subscription status — never your card details.
• Operational data. Limited logs and abuse-prevention signals (such as hashed IP/session identifiers) used to keep the service reliable and stop misuse.

How we use it

To provide and operate the service, authenticate you, enforce plan limits, prevent abuse, process payments, and communicate about your account. We do not sell your personal data.

Demo launch links

If you open a public demo launch link, we provision a throwaway sandbox for you. When the link owner has enabled email capture, the email you enter is shared with that owner as a lead. Anonymous demos are identified only by a short-lived session cookie and expire automatically.

SandyWP for Slack

If your workspace installs the SandyWP for Slack app, we process the following so the bot can deploy to your sandboxes when you mention it:

• Workspace identity. Your Slack team (workspace) ID and name.
• Bot token. The per-workspace bot token Slack issues on install, stored encrypted at rest (AES-256-GCM). It is decrypted only in memory to call the Slack API on your behalf.
• User identity. The Slack user IDs of people who interact with the bot, used to link a Slack user to their SandyWP account and to route replies. Linking a Slack user creates a personal SandyWP API token, also stored encrypted at rest.
• Message content. The text of messages that mention the bot is processed to understand your command (for example which site to deploy to). It is not retained beyond ordinary operational logs.
• Uploaded files. Plugin .zip files you attach are downloaded and deployed to your sandbox; they are stored as deploy artifacts on your account. We do not read other files or your message history — the bot only scans a thread for a .zip when you ask it to deploy one.

Retention & deletion. When your workspace uninstalls the app (or Slack revokes its token), the stored installation and every account link under it are deleted. You can unlink your own account at any time by mentioning @SandyWP logout, which revokes the API token and removes the mapping. We do not sell any Slack data, and we do not use it for advertising.

For a walkthrough of the app itself, see the Slack app guide.

Data retention

Sandboxes are ephemeral and are removed when they expire. Account and billing records are kept while your account is active and for as long as needed to meet legal and accounting obligations. Slack installation and account-link data is removed on uninstall or unlink, as described above. You can request deletion of your account at any time.

Subprocessors

SandyWP runs on hosting virtual private servers (VPSs) that store the data described above, and uses a payment provider to process paid subscriptions. Slack Technologies operates the messaging platform the Slack app connects to. We do not share your data with third parties for their own purposes.

Your choices

You can access, correct, export, or delete your account data by contacting us. Where required by law, you may also object to or restrict certain processing.

Contact

Questions about privacy, or to exercise any of the rights above? Email [email protected].

Placeholder notice. SandyWP is operated by an individual during beta. The legal entity / data controller and a dedicated support address will be substituted here before general availability. Until then, the contact address above reaches the operator directly.