1. Scope and who is responsible
This policy covers the Sculpt website, API, and the Sculpt plugin for Roblox Studio (together, the "Service"). The data controller is the operator of Sculpt, reachable through the support channel in Section 16.
It does not cover third-party platforms you use alongside Sculpt — Discord, Roblox, or payment providers each have their own privacy policies that govern what they do with your data.
2. Data we collect
Provided by Discord when you sign in
- Discord user ID (permanent identifier of your Discord account)
- Username and display name
- Email address associated with your Discord account
- Avatar image reference
We request only the identify and email OAuth scopes — we cannot read your Discord messages, see your servers, or act as you.
Created while you use the Service
- Chat content — your messages, the script context you attach by selecting scripts, and the AI's replies. Stored so chat history works across the website and the plugin.
- Usage records — per-request token counts (input and output), the model used, and the credits charged.
- Account and billing records — credit balance, plan and its expiry, wallet balance, and a ledger of top-ups and purchases (amounts, dates, what was bought). We never see or store card numbers or crypto wallet private keys.
- Session records — sign-in timestamps and issued session/plugin tokens.
Collected automatically
- Standard technical data needed to serve requests: IP address and user-agent as they appear in transient server logs. These are used for security and debugging, not for profiling.
3. Data we deliberately don't collect
- No Roblox account data. Sculpt never asks for or receives your Roblox credentials, cookies, or account information. The plugin runs inside Studio but does not read your Roblox identity.
- No identity documents. We never ask for your name, address, passport, or ID.
- No payment card numbers — payments are handled entirely by payment processors.
- No third-party analytics or advertising trackers. The site contains no ad pixels, no fingerprinting, no cross-site tracking.
- No background scanning. The plugin does not index or upload your place file, assets, or scripts you didn't select.
4. How and why we use your data
- Operating the Service — authenticating you, generating AI replies to your requests, syncing chats between the website and plugin, showing your balance.
- Billing — metering token usage, charging credits, maintaining your purchase ledger so you can verify every charge.
- Support — investigating issues you report; a support agent may view your account records and, with your permission, relevant chats.
- Security and abuse prevention — detecting multi-account credit farming, payment fraud, attempts to break rate limits or access other users' data.
- Legal compliance — keeping transaction records where bookkeeping or tax law requires it, responding to lawful requests from authorities.
- Service improvement — aggregate, de-identified statistics (e.g. "average request costs 0.1 credits") that contain no personal data.
We do not: sell or rent your data, use it for advertising, profile you for marketing, or make automated decisions with legal effect about you. Your chats are not used to train AI models — neither by us nor, per their API terms, by the model providers we use.
5. Legal bases (for GDPR-type jurisdictions)
Where a legal basis is required, we rely on:
- Performance of a contract — account, chats, AI processing, billing (Sections 2, 4): we need this data to provide what you signed up for.
- Legitimate interests — security logging, abuse prevention, service improvement with de-identified data; balanced against your rights and freedoms.
- Legal obligation — retention of transaction records for bookkeeping/tax.
- Consent — anything optional we might add later (e.g. a newsletter) would be opt-in and withdrawable.
6. Who we share data with
- AI model providers — to answer a request, its content (your message + selected script context + recent chat history) is transmitted to the model provider through an API gateway. See Section 7.
- Discord — only as your sign-in provider. The OAuth flow tells Discord you use Sculpt; we receive the profile fields in Section 2.
- Payment processors — when you pay, the processor handles the transaction and tells us it succeeded, the amount, and a transaction reference. Crypto processors see your wallet address; we do not.
- Infrastructure providers — servers that host the Service store the data described above on our behalf under data-processing terms.
- Authorities — only where a valid legal demand compels us, and no broader than required.
- Business transfer — if Sculpt is acquired or merged, data transfers with the service under the same protections, and you will be notified.
No selling, no renting, no data brokers, no advertisers — ever.
7. AI processing — what leaves for the model
When you send a request, the following is transmitted to an AI model provider to generate the reply:
- Your message text;
- The source code of scripts you selected (plugin) or the conversation context (web chat);
- Recent messages of the same chat, so the model has continuity;
- Image URLs you attached, if any.
The provider processes this to produce the answer and reports token counts back for billing. Per the API terms we rely on, this content is not used to train their models. Do not include secrets (API keys, passwords) in prompts or selected scripts — treat anything you send as leaving your machine, because it does.
8. What the plugin can and cannot see
- The plugin reads only the scripts you have selected at the moment you press Send — that is the entire context. Nothing else in your place is read, indexed, or uploaded.
- Output-window errors are read only when you press the "Fix errors" button, and only the recent error/warning lines.
- The plugin never modifies code silently: every change is behind an explicit Apply/Create click (or the Auto-apply setting you turn on yourself), passes through Studio's ChangeHistory, and is undoable with
Ctrl+Z.
- The plugin talks only to the Sculpt server over HTTPS; it makes no other network calls.
9. Cookies and tokens
- Session cookie — one first-party
httpOnly cookie holding a signed session token (JWT), valid up to 30 days. It exists solely to keep you signed in; page JavaScript cannot read it. No advertising or analytics cookies exist on the site.
- Plugin token — a bearer token issued when you enter a 6-digit pair code, valid 90 days, stored in Studio's plugin settings on your machine.
- Signing out clears the session; revoking Discord access invalidates the account link. Because only strictly-necessary cookies are used, no cookie consent banner is required.
10. How long we keep data
- Account profile — for the life of your account; deleted on account deletion.
- Chats — until you delete the chat or your account. Archived chats are hidden from your list but retained until account deletion.
- Usage records (tokens, credit charges) — for the life of the account, so billing stays auditable.
- Purchase ledger — retained as long as bookkeeping/tax law requires even after account deletion, in de-linked form where possible.
- Server logs (IP, user-agent) — short-lived, rotated automatically.
- After account deletion — personal data is removed or irreversibly de-identified within 30 days, except records law obliges us to keep.
11. Security
- Transport encryption (HTTPS/TLS) for the website, API, and plugin traffic.
- Signed, expiring tokens;
httpOnly session cookies; plugin tokens scoped to plugin endpoints only.
- Access to production data is limited to the operator; there is no third-party staff access.
- Payments handled by external processors — no card data ever touches our servers.
- No system is perfectly secure. If we learn of a breach affecting your personal data, we will notify affected users and, where required, supervisory authorities without undue delay.
12. International transfers
Our servers and the third-party providers we use (AI model providers, payment processors, infrastructure) may be located in countries other than yours. Where data-protection law regulates such transfers, we rely on the safeguards available in those laws (such as standard contractual clauses adopted by the provider, or your explicit understanding that the transfer is necessary to perform the service you requested).
13. Your rights and controls
Built-in controls
- Sign out — ends your browser session immediately.
- Revoke Discord access — Discord → Settings → Authorized Apps → remove Sculpt.
- Delete chats — remove conversations you no longer want stored.
- See your data — your profile page shows your stored account fields, usage stats, and full purchase history.
Rights on request (via support)
- Access / export — a copy of the personal data we hold about you, in a portable format.
- Correction — profile data comes from Discord; correct it there and re-sign-in, or ask us for anything else.
- Deletion — full account deletion (Section 10 timelines and legal-retention exceptions apply).
- Restriction / objection — to processing based on legitimate interests.
- Complaint — you may lodge a complaint with your local data-protection authority; we'd appreciate the chance to resolve it first.
We respond to verified requests within 30 days. Verification happens through the Discord account that owns the Sculpt account.
14. Children
The Service is for users 13 and older, matching Roblox's own minimum age. We do not knowingly collect data from children under 13; if we learn an account belongs to a child under 13, we will delete it and its data. Users between 13 and the age of majority need a parent or guardian's consent to use the Service, and purchases must be made or approved by that guardian. Guardians can contact support about a minor's account or data at any time.
15. Changes to this policy
Updates are posted on this page with a new "Last updated" date. For material changes — new data categories, new sharing recipients, changed retention — we will give notice through the Service at least 14 days before the change takes effect. Continued use after the effective date means the updated policy applies; if you disagree, stop using the Service and request deletion.