Our approach
Three principles guide how PUZL is built:
- Least access. People, systems and AI connections get only the access they need, and nothing more.
- Your data stays separate. Each customer's data is kept apart from every other customer's, and within your account, a location user sees only their own location.
- Access is recorded. Every request an AI makes through PUZL is logged with who made it and when.
How your AI connection works
PUZL connects to the Claude, ChatGPT or Grok account your business already uses. Because this is the core of the product, it's worth explaining exactly what happens.
- You authorize the connection. Each team member connects their own AI account through a standard, secure sign-in flow (OAuth). PUZL never sees or stores your Claude, ChatGPT or Grok password.
- Access follows the person. When someone asks a question, PUZL checks their role and location before returning anything. A staff member's AI cannot see what the staff member can't see.
- Only what's needed is shared. PUZL sends your AI provider the specific information needed to answer a question, not your whole library.
- You can revoke it anytime. Disconnect an AI app on the Connect AI page in the PUZL portal and it loses access right away.
- No model training on your data. PUZL does not use your business data to train AI models. How your AI provider handles the information it receives is governed by your agreement with that provider. Business and team plans from major AI providers generally exclude customer data from training by default; check your plan's terms.
Encryption
- In transit: all connections to PUZL use TLS 1.2 or higher.
- At rest: the database, uploaded files and backups are encrypted using AES-256.
- Credentials: access tokens for your connected tools get a second layer of encryption inside PUZL. The key is held in AWS Systems Manager Parameter Store, encrypted by AWS Key Management Service (KMS), and never in our code.
Access controls in your account
- Roles: admins see the whole account; location users see only their own location. Financial data, such as QuickBooks, is visible to admins only.
- Sign-in: sign in with Google, a passkey or a one-time email link. When you sign in with Google, your Google account's 2-Step Verification protects your PUZL sign-in too.
- Connected apps: the Connect AI page shows each connected AI app, who connected it and when it was last used.
- Offboarding: removing a team member revokes their portal access and their AI connection at the same time.
Infrastructure
PUZL runs on Amazon Web Services (AWS) in the United States, in the us-east-2 (Ohio) and us-east-1 (Virginia) regions. AWS maintains physical security and environmental controls for its data centers, and holds its own independent certifications for them.
- Customer data is logically isolated by account in the application.
- Production systems are separated from development and testing environments. Real customer data is never copied into development or testing.
- Encrypted database backups run every 6 hours and are kept for 30 days. Encrypted snapshots of the database disk are taken daily and kept for 7 days.
- Automated alarms alert our team if a database backup is missed.
Our team and internal access
- PUZL is run by its founder. The founder and one other team member have operator access to customer data, to support you and to keep the service running.
- Both sign in with Google 2-Step Verification, and their actions in PUZL's admin tools are logged, including which pages are opened.
How we build software
- PUZL has an automated test suite of more than 12,000 tests.
- We test PUZL for security issues with AI-assisted reviews; we have not yet had an independent penetration test.
Vendors
We use outside providers to run PUZL, such as AWS for hosting and Stripe for payments, and engage them under written agreements appropriate to the data involved.
Integrations you choose to connect (for example, a CRM or POS system) and the AI provider you use are operated by those companies under their own terms. PUZL accesses them only with your authorization and only to provide the service.
Compliance
| Standard | Status |
|---|---|
| SOC 2 | PUZL is new. We follow SOC 2 security controls but have not yet had an audit. |
| California privacy law (CCPA/CPRA) | Supported; see California Privacy Rights in our Privacy Policy |
| Payment card data (PCI DSS) | Handled by our payment processor, Stripe; PUZL does not store card numbers |
PUZL is not designed to store protected health information under HIPAA or payment card numbers. Please don't upload them.
Incident response
If we confirm a security incident affecting your data, we will notify you without undue delay, and in any case within the time required by law and your agreement with us, with what we know, what we're doing about it and what you can do.
Common security questions
Does PUZL use my data to train AI?
No. PUZL never uses your business data to train AI models, and we never sell it.
Can PUZL staff see my data?
The founder and one other team member can, to support you and keep the service running. Both sign in with Google 2-Step Verification, and their actions in PUZL's admin tools are logged.
What happens to my data if I cancel?
If you were on a paid plan, we keep your account data for 13 months after the plan ends. After that, your account goes on our erase list, and an operator permanently erases it, with a 7-day grace period immediately before erasure. If your trial ends without becoming a paid plan, we keep your account data for 90 days, then it is permanently erased, with a 7-day grace period immediately before erasure. We keep a minimal record, such as the account ID and the audit entries for the erase, so we can show it was done. To delete your data sooner, email privacy@puzldata.com; we delete it within 30 days, by an operator erase. Database backups expire after 30 days.
Can I remove a tool or a shared folder?
Yes. Disconnect a tool or remove a shared folder in the portal and PUZL stops pulling new data from it. Files PUZL already copied stay in Documents; contact support if you want them deleted.
Is PUZL HIPAA compliant?
No. PUZL isn't designed for protected health information, so please don't upload patient records or other health data covered by HIPAA.
Report a vulnerability
If you believe you've found a security issue in PUZL, email support@puzldata.com with a description and steps to reproduce it. We'll acknowledge your report within 2 business days and keep you updated.
Please give us reasonable time to fix the issue before sharing it publicly, and don't access or change other customers' data, disrupt the service or use social engineering. We won't pursue legal action against good-faith research that follows these guidelines.
What you can do
- Turn on 2-Step Verification for the Google account you sign in with, or sign in with a passkey, and protect your Claude, ChatGPT or Grok account the same way.
- Give each person the narrowest role that lets them do their job.
- Remove people promptly when they leave.
- Review your connected AI apps on the Connect AI page from time to time.
- Keep sensitive personal data you don't need out of uploads.