Privacy Policy
This Privacy Policy explains how Curobi (the “Curobi” app, “we”, “us”), operated by Vibhora, collects, uses, stores, discloses, and protects information in connection with the Curobi subscription application for Shopify (the “App”) and our websites, curobi.com and docs.curobi.com (the “Sites”). It covers the merchants who install the App, their customers whose data the App processes, and visitors to the Sites.
Curobi runs on Shopify’s native subscription and billing rails. Recurring charges are processed by Shopify, so the App never handles, sees, or stores customer payment-card data.
1. Our role: data processor
When you install Curobi, you (the merchant) remain the data controllerof your store’s and your customers’ personal data. Curobi acts as adata processor, processing that data only on your instructions and only to provide the App’s functionality. We do not sell personal data, and we do not use it for advertising, profiling, or any purpose beyond operating the App.
Information you give us directly, such as a form on our website, an email, or a support chat, is ours to look after. Sections 2, 7 and 11 explain what we collect that way and how we use it.
2. Information the App accesses and stores
Curobi is built to process the minimum data necessary. It accesses the following through Shopify’s APIs. Data marked transient is read in-request to create or manage a subscription and is never written to our database.
| Data | Accessed | Stored by Curobi |
|---|---|---|
| Customer ID (Shopify GID) | Yes | Yes — identifier only |
| Customer name | Yes (transient) | No |
| Shipping / delivery address | Yes (transient) | No |
| Payment-method ID (vaulted token reference) | Yes (transient) | No |
| Subscription contract data | Yes | Mirror — IDs and status only |
| Customer email | Yes (transient) | No |
| Customer phone | No | No |
| Payment-card / bank details | No | No |
For merchants, Curobi also stores your store domain, the offline access token issued by Shopify, and the granted API scopes so the App can operate against your store. To power its merchant dashboards, Curobi stores non-identifying operational records such as subscription status, billing dates, and aggregate analytics.
Key point: Curobi persists only Shopify identifiers (GIDs) and subscription status. Customer name, email, address, and payment details are read only in-request, to build a subscription contract or send a message, and are never stored at rest. There is no raw customer personally identifiable information (PII) in our database.
Support chat. The App’s own pages, including its admin inside Shopify, show a tawk.to chat widget. It does not load on your storefront, in customer accounts, or at checkout. Messages, attachments, and contact details someone chooses to send through the chat, plus the technical information tawk.to collects to run it (such as IP address, browser type, approximate location, and the App page the chat was opened from), are processed by tawk.to and are not copied to the App’s database. We do not send Shopify customer, subscription, or store data to tawk.to.
3. Shopify API scopes we request
The App asks for these scopes when it is installed, each for the feature listed:
- Plans, boxes and bundles:
write_products,write_publications,write_purchase_options— create subscription plans and the products behind boxes and bundles, and make them available on your storefront. - Subscription contracts:
read_own_subscription_contracts,write_own_subscription_contracts— create and manage the subscription contracts the App owns. - Orders:
read_orders,write_order_edits— read the order a subscription started from, and apply a customer’s box selections to an order. - Inventory:
write_inventory,read_locations— keep stock counts right when box selections change an order, and forecast stock for upcoming renewals. - Discounts:
read_discounts,write_discounts— the discounts behind save offers, win-back codes, and Mix & Match bundles. - Checkout validation:
read_validations,write_validations— the checkout rule that applies your plan’s active-subscription limit. - Customers and payment methods:
read_customers,write_customers,read_customer_payment_methods,write_customer_payment_methods— find the customer and shipping address for a subscription, attach their vaulted payment-method reference (never card data) to a contract, and ask Shopify to send the customer a secure link to update their card. - Storefront widget:
read_themes— set up and check the subscription widget in your theme. - Customer portal:
customer_read_customers,customer_write_customers,customer_read_orders,customer_read_own_subscription_contracts,customer_write_own_subscription_contracts— let a signed-in customer see and manage their own subscriptions in their Shopify customer account. These reach only that customer’s own records.
Two optional scopes, read_online_store_navigation andwrite_online_store_navigation, are asked for only if a merchant clicksUpdate my menu on the App’s Portal branding page, to point the customer account menu’s Manage subscriptions link at the branded portal. They are never requested at install.
Under Shopify’s Protected Customer Data requirements, the App requests access only to the Name, Email and Address protected fields — never phone. A customer’s email address is read from Shopify only at the moment it is needed, to send a subscription email or an event to an integration the merchant connected (see section 6), and is never stored.
4. How we use information
- Create and manage subscription contracts, plans, bundles, and boxes.
- Render the merchant admin dashboard and the customer self-service portal.
- Recover failed recurring payments (retries and payment-update prompts).
- Send transactional and subscription-lifecycle emails on the merchant’s behalf.
- Send subscription events to services the merchant chooses to connect, and answer lookups from them (see section 6).
- Produce aggregate analytics (e.g. MRR, churn, renewal forecasts) for the merchant.
- Answer support questions sent through the App’s chat widget or by email.
- Maintain the security, integrity, and reliability of the App.
5. Sub-processors
We use a small number of trusted service providers to run the App. Each processes data only as needed to provide its service to us and is bound by appropriate data-protection terms.
| Sub-processor | Purpose | Region |
|---|---|---|
| Shopify Inc. | Core platform, native subscription billing, and system of record. Recurring charges are processed by Shopify — Curobi never handles or stores card data. | USA / Canada |
| Neon (Postgres database) | Stores the app's operational data (Shopify identifiers and subscription status). Encrypts data and backups at rest. | USA |
| Vercel | Application hosting and serverless compute. All traffic is served over HTTPS. | USA |
| Resend | Delivery of transactional and subscription-lifecycle emails (e.g. renewal reminders, payment-update prompts) on the merchant's behalf. | USA |
| Inngest | Background job processing, such as scheduled renewals, payment retries and email sends. | USA |
| tawk.to | Support chat on the App's pages, including chat content a visitor chooses to submit and the session data the chat needs to work. | USA |
6. Integrations the merchant connects
A merchant can choose to connect the App to other services they use. Nothing is shared with an integration until the merchant sets it up, and disconnecting it stops any further sharing.
- Shopify Flow: subscription events, such as a subscription starting or a payment failing, are sent to the merchant’s own Flow workflows. The customer is referenced by their Shopify ID only; their contact details stay inside Shopify.
- Email-marketing services, such as Klaviyo: when the merchant connects their account, the App sends subscription events and subscription status for a customer together with that customer’s email address, so the service can match them to the profile the merchant already holds there. The email address is read from Shopify when each event is sent and is not stored by the App. The App never sends phone numbers, postal addresses or payment details, and never subscribes a customer to a marketing list or changes their consent settings.
- Helpdesks, such as Gorgias: when the merchant sets this up with a Curobi API key, the helpdesk sends the App the email address on a support ticket, and the App uses it to look up that customer’s subscriptions in Shopify. The App returns subscription details (status, products, billing frequency, dates, amounts and order number) and no names, email addresses, postal addresses or payment details. The email address it receives is not stored.
Once received, the connected service processes this data as the merchant’s own provider, under the merchant’s agreement with it and its own privacy policy. These services are not our sub-processors.
7. Data retention and deletion
We retain data only as long as needed to provide the App, and we honor Shopify’s mandatory data-privacy webhooks:
- Customer data request (
customers/data_request) — we assemble every record we hold for that customer and provide it to the merchant so they can respond within the required window. We hold no raw customer PII of our own to export. - Customer redaction (
customers/redact) — we delete the subscription records referencing that customer for the store. - Shop redaction (
shop/redact) — after a merchant uninstalls the App (approximately 48 hours later), we delete all of that store’s subscription, offer, and session records.
Deletions requested through these webhooks are completed within 30 days. Inside the App, we retain no customer personal data beyond the identifiers needed for an active subscription.
- Support chat — chat transcripts are not stored in the App’s database. Conversations stay in tawk.to under its own retention terms; contact us for help with access or deletion.
- Website enquiries — what you send through a form on curobi.com is kept so we can follow up with you. Email us and we will delete it.
8. Security
- Encryption in transit: all connections to Shopify and to our database use TLS; the App is served exclusively over HTTPS.
- Encryption at rest: our database provider encrypts stored data and backups at rest.
- Data minimization: no raw customer PII is stored at rest — only Shopify identifiers and subscription status.
- Access control: production credentials are tightly restricted, protected by strong, unique passwords and two-factor authentication.
- Environment separation: development and production use separate deployments, databases, and credentials.
- Access logging: we emit PII-free, structured logs each time customer data is accessed, recording who/what/when — never the data values themselves.
- Incident response: we maintain a documented security-incident and breach-notification procedure. On a confirmed personal-data breach we notify affected merchants without undue delay so they can meet their own obligations (including the GDPR 72-hour window) and notify Shopify through its Trust/Partner channels.
9. International data transfers
Our sub-processors are located in the United States and Canada. The website tools described in section 11 are run by Google, Meta, Microsoft and Vercel, which process data in the United States and other countries. Where personal data is transferred internationally, it is protected by appropriate safeguards offered by those providers (such as Standard Contractual Clauses or the EU-U.S. Data Privacy Framework) and, for App data, by the data-protection terms in the Shopify Partner Program Agreement and API Terms, which govern our processor relationship.
10. Your rights (merchants, customers, and visitors)
Depending on your location, you may have rights under laws such as the GDPR and the CCPA to access, correct, delete, or restrict the use of your personal data, and to object to or port it.
- Customers of a store: because we process your data on behalf of the merchant (the controller), please direct data-subject requests to the store you subscribed with. The merchant can trigger data-request and deletion through Shopify, and we will act on it.
- Merchants: you can uninstall the App at any time, which triggers deletion of your store’s data as described in Section 7, or contact us directly using the details below.
- Website visitors and anyone who contacts us: email us to see, correct, or delete what you sent us through a form, by email, or in the support chat. Section 11 explains how to turn off website cookies.
We do not engage in automated decision-making or profiling about customers.
11. Our websites, forms, and cookies
This section covers curobi.com, docs.curobi.com, and the cookies the App itself sets. None of it involves the data the App processes for a merchant’s customers.
Forms on curobi.com
Our forms (the contact form and, while it is open, the founding-merchant offer) ask for your name and email address, and optionally your store URL, business name, store category, and a message. We also record your browser’s user-agent string and the page you came from. Submissions are stored in our database (Neon) and emailed to our team through Resend. We use them to reply to you and to talk with you about Curobi, and we do not sell them.
Booking a call takes you to Cal.com, which handles the booking under its own privacy policy.
Cookies and tags on curobi.com
The live site uses these tools:
- Google Analytics and Google Tag Manager (Google) — count visits and show which pages and actions lead to installs.
- Google Ads (Google) and the Meta Pixel (Meta) — measure how our ads perform and build advertising audiences from visits to the site.
- Microsoft Clarity (Microsoft) — records how visitors scroll, click, and move through a page, so we can see where a page is confusing.
The events we send these tools describe what you did, such as viewing the pricing page or clicking Install. They do not include anything you type into a form. Each provider sets its own cookies and handles the data under its own privacy policy.
docs.curobi.com
The documentation site uses Vercel Web Analytics, which counts page views and referrers without cookies, and the Meta Pixel, to measure our ads. If your browser’s time zone is in the EU, EEA, UK, or Switzerland, the site asks first and loads the pixel only if you allow it. Anyone can change their choice from “Cookie settings” in the documentation site’s footer.
Inside the App
The App uses session cookies required for sign-in and security. Its tawk.to support chat widget also sets a twk_uuid_* cookie, which lasts six months and holds a random ID that recognizes a returning chat visitor so their conversation stays available, plus session cookies (such as TawkConnectionTime andtwk_idm_key) that manage the chat connection. The App sets no advertising cookies, and the website tools above do not run inside it.
Your choices
You can block or delete cookies in your browser settings. Google’sMy Ad Center and Meta’s ad preferences control ad personalization, and Google offers abrowser add-on to opt out of Google Analytics.
12. Children’s privacy
The App is a business tool for Shopify merchants and is not directed to children. We do not knowingly collect personal data from children.
13. Changes to this policy
We may update this Privacy Policy from time to time. When we make material changes, we will revise the effective date above and, where appropriate, notify merchants. Your continued use of the App after an update constitutes acceptance of the revised policy.
14. Contact us
For any question about this policy or to exercise a data-protection right, contact us at:
- Email: hello@curobi.com
Curobi is operated by Vibhora. Curobi is not affiliated with or endorsed by Shopify Inc.
