Sub-Processors & Data Processing
Last Updated: November 4, 2026
Version: 1.4
Service: Burnish Pro
This document lists all third-party services that process your personal data and designs on our behalf.
Core Infrastructure
Supabase (PostgreSQL Database)
- Location: United States (AWS US-East-1)
- Purpose: Store account data, designs, runs, 3D queue status; handle sign-in and send the email that confirms your address at signup
- Data Shared: Email, name, all design parameters, generated images, usage logs
- DPA: Supabase Data Processing Agreement
- Encryption: AES-256 at rest, TLS 1.2+ in transit
- Retention: Until account deletion + 30-day recovery window; backups retained 30 days
Stripe (Payment Processing)
- Location: United States
- Purpose: Process payments and manage billing
- Data Shared: Email, name, payment method (tokenized)
- DPA: Stripe Data Processing Agreement
- Retention: Per Stripe's 7-year transaction retention policy
- PCI Compliance: Stripe is PCI-DSS Level 1 certified
- Note: Credit card details never stored by Burnish Pro
Vercel (Hosting)
- Location: United States (server functions run in Vercel's US East region; requests may pass through Vercel's global edge network)
- Purpose: Host the web app and run its server functions
- Data Shared: Every request to the Service, including IP addresses and the content you submit; server logs
- DPA: Vercel Data Processing Addendum
AI & Image Generation
Google Gemini 3.1 Flash Image & 3 Pro Image
- Location: United States (Google Cloud)
- Purpose: Generate jewelry designs from prompts and images
- Data Shared: Jewelry design prompts, parameters, and the images a request starts from: designs (for variants and Studio Refine), sketches (Studio Sketch and Design Station), and photos uploaded to Studio From Photo
- DPA: Google Cloud DPA
- Retention: Prompts/images deleted after generation completes (not stored by Google)
- Model Training: Your designs are NOT used to train models
- Safety: Implements SafetyAttributes filtering for inappropriate content
OpenAI GPT-Image-2 & Moderation API
- Location: United States
- Purpose: Generate premium quality designs; check designs for policy violations
- Data Shared: Design prompts and generation parameters; photos uploaded to Studio From Photo and the message a client adds to a share-link price request (moderation only)
- DPA: OpenAI Data Processing Agreement
- Retention: Prompts deleted after 30 days per OpenAI policy (not retained by default)
- Model Training: Your designs are NOT used for model improvement (unless you explicitly opt-in)
- Moderation: Prompts checked for policy violations before generation, and the message a client adds to a share-link price request checked before it is stored
3D Model Generation
Meshy API
- Location: United States
- Purpose: Convert jewelry images into 3D mesh models (GLB, OBJ, FBX, USDZ)
- Data Shared: Design images, model format preferences, generation parameters
- Terms: Meshy Terms of Service
- DPA Status: No separate DPA available from Meshy. Data shared is limited to design images for 3D conversion. We rely on their Terms of Service and standard security practices as contractual safeguards.
- Retention: Models stored for 30 days; available for download indefinitely
- Quality Levels: Standard (single image) and Premium (multi-angle)
- Formats Supported: GLB (recommended), OBJ, FBX, USDZ
Infrastructure Services
Upstash (Redis)
- Location: United States
- Purpose: API rate limiting and CSRF token storage
- Data Shared: Request metadata, IP addresses, rate limit counters
- DPA: Upstash Data Processing Agreement
- Retention: Rate limit data expires automatically (short-lived TTLs)
- Note: No designs are stored in Redis. A photo sent from your phone to Studio passes through Redis and is deleted when your desktop collects it, or expires within minutes
Inngest (Background Processing)
- Location: United States
- Purpose: Orchestrate background jobs (batch generation, queue processing)
- Data Shared: Job IDs, generation parameters, status callbacks
- DPA: Inngest Privacy Policy
- Retention: Job metadata retained for 7 days for debugging
- Note: Inngest does not store generated images or design content
Analytics
Google Analytics (Website Analytics)
- Location: United States
- Purpose: Count visits to our public pages (home, pricing, blog, product and legal pages, sign-in and sign-up, and the first page after sign-up). It does not run in the signed-in app.
- Data Shared: Page viewed (only campaign tags are kept from a page's address), referring website, approximate location derived from IP address, browser and device type. Advertising features and Google signals are off. No Google Analytics cookies are set for visitors in the EEA, UK or Switzerland.
- DPA: Google Ads Data Processing Terms
- Opt-out: Google Analytics opt-out add-on, or block it in your browser
- Retention: Configured in Google Analytics, never more than 14 months
Communications
Resend (Transactional Email)
- Location: United States
- Purpose: Send transactional email: Design Station lead notices to a store's owners and admins (or the address the store chose for that station), share-link price request notices to a store's owners and admins, a store's quote to its client (sent under the store's name, replies going to the store), new-account alerts to our team, and account approval notices to an organization's owner
- Data Shared: Recipient email addresses. A lead notice carries the walk-in customer's name, email, phone and notes, the number of designs they saved, and the station and store names. A price request notice carries the client's name, email or phone and message, the design's title and the share link's title. A quote carries the client's email address, the store's name and logo, the design image, and the amount and note the store typed. A new-account alert carries the new user's email address and sign-up time. An approval notice carries the owner's email address, name and organization name
- DPA: Resend Data Processing Addendum
Slack (Internal Alerts)
- Location: United States
- Purpose: Deliver alerts to our team through an incoming webhook: new signups, failed first runs during onboarding, image provider outages, and billing or integration problems that need manual attention
- Data Shared: A new-account alert carries the new user's email address and sign-up time. An onboarding failure alert carries the user's email address, the failure type, the jewelry category and the organization ID. All other alerts carry internal record IDs (such as organization, run, Stripe and Shopify IDs) and error codes only
- DPA: Slack Data Processing Addendum
Customer-Directed Integrations
Shopify (Only If You Connect It)
- Status: Not a sub-processor we select. You choose to connect your own Shopify store, and Shopify handles that data under your own agreement with Shopify
- What We Send: When you publish a drop, we create draft products and a collection in your store: product title, description (including the design prompt, style, metal and stones), price, SKU, weight, tags, vendor name and the design image, plus the drop's title and marketing copy for the collection
- What We Store: Your store's domain, the permissions granted, and the access token, encrypted at rest (AES-256-GCM)
- Permissions: The connection asks Shopify for permission to write products and collections and to read orders. Order access is reserved for a planned sales sync; the Service does not read your orders today
- Disconnect: An organization admin can disconnect the store in Settings, which erases the access token we store. This does not revoke the authorization at Shopify: to do that, uninstall the app from your Shopify admin. Products already created in your store stay there
- Privacy: Shopify Privacy Policy
Summary Table
| Service | Type | Location | Encryption | DPA | Optional |
|---|---|---|---|---|---|
| Supabase | Database | US | Yes (AES-256) | Yes | No |
| Vercel | Hosting | US | Yes (TLS) | Yes | No |
| Stripe | Payments | US | Yes (TLS) | Yes | No |
| Google Gemini | AI Generation | US | Yes (TLS) | Yes | No |
| OpenAI | AI Generation | US | Yes (TLS) | Yes | No |
| Meshy API | 3D Generation | US | Yes (TLS) | TOS only | No |
| Upstash | Rate Limiting | US | Yes (TLS) | Yes | No |
| Inngest | Job Processing | US | Yes (TLS) | Yes | No |
| Resend | US | Yes (TLS) | Yes | No | |
| Slack | Internal Alerts | US | Yes (TLS) | Yes | No |
| Google Analytics | Website analytics | US | Yes (TLS) | Yes | Yes |
Shopify is not in this table: it is a customer-directed integration you connect yourself (see above).
Your Rights
You have the right to:
- Access: Know which processors handle your data
- Withdrawal: Stop using the Service and request data deletion
- Objection: Opt-out of optional processors (Google Analytics)
- Portability: Request your data in a standard format
For questions about sub-processors, contact:
Email: Ryan@RyanB.NYC
Changes to Sub-processors
If we add a new processor, we will:
1. Notify you 30 days in advance
2. Provide details about the processor and data shared
3. Allow you to object or request data deletion
How to object:
Email Ryan@RyanB.NYC with your objection within 30 days.