Privacy Policy

1. Introduction

Cloudlabels ("we," "our," or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our service at app.cloudlabels.io and our website at cloudlabels.io.

By using our service, you agree to the collection and use of information in accordance with this policy.

2. Information We Collect

2.1 Information You Provide

• Account information (name, email address, password)
• Organization information (company name, team members)
• Payment information (Stripe for standalone accounts; Shopify Billing API for App Store installs)
• Content you create (labels, items, print profiles)
• Shopify store data when you install the Cloudlabels Shopify app (shop domain, OAuth token, product, variant, inventory, and barcode fields)
• Support communications

2.2 Automatically Collected Information

• Usage data (features used, time spent)
• Device information (browser type, operating system)
• IP address and location data
• Cookies and similar tracking technologies

3. How We Use Your Information

• To provide and maintain our service
• To process payments and manage subscriptions
• To notify you about changes to our service
• To provide customer support
• To gather analysis and improve our service
• To monitor usage and detect technical issues
• To send marketing communications (with your consent)

4. Data Sharing and Disclosure

We do not sell your personal data. We may share your information only in the following circumstances:

• Service Providers: With third-party services that help us operate (Stripe for standalone payments, Shopify Billing for App Store installs, Supabase for hosting, Railway and Vercel for hosting, Resend for transactional email delivery)
• Legal Requirements: When required by law or to protect our rights
• Business Transfers: In connection with a merger, acquisition, or sale of assets
• With Your Consent: When you explicitly authorize us to share information

5. Data Security

We implement industry-standard security measures to protect your data:

• Encryption in transit (SSL/TLS) and at rest
• Most data access runs with the signed-in user's own permissions and row-level security (RLS). Some operations (barcode allocation, PDF and image storage, activity logging) use a server account that filters by organization in code
• Regular security audits and updates
• Access controls and authentication
• Secure cloud infrastructure (Supabase, Vercel)

However, no method of transmission over the Internet is 100% secure. While we strive to protect your data, we cannot guarantee absolute security.

6. Shopify App Store installs

If you install Cloudlabels from the Shopify App Store, Shopify sends us your shop domain and an OAuth access token. We store the token encrypted and use it to sync product, variant, inventory, and barcode data so you can design and print labels. We do not sell this data.

App Store subscriptions are billed through the Shopify Billing API. We request the read_customers scope only so Shopify can deliver the mandatory GDPR webhooks (customers/data_request, customers/redact, shop/redact). Cloudlabels does not show customer profiles in the merchant UI.

After you uninstall, Shopify sends shop/redact. We then delete that shop's Cloudlabels data within 48 hours. Standalone web accounts that you created outside Shopify follow the retention rule in section 8.

7. Using Cloudlabels Through AI Assistants (MCP)

You can connect Cloudlabels to an AI assistant, such as ChatGPT, Codex, Claude, or Cursor, through our Model Context Protocol (MCP) server at api.cloudlabels.io. The assistant can then call Cloudlabels tools on your behalf, within the permissions you approve. This section explains what data is shared when you do that.

7.1 How You Connect

• OAuth: You sign in to Cloudlabels and approve the connection in your browser. The approval screen shows the permissions the assistant asks for.
• API key: You create a key in Cloudlabels settings and give it to the assistant yourself.

Cloudlabels never asks the assistant for your Cloudlabels password, and tool responses do not include passwords, API keys, or access tokens.

7.2 Data Accessed and Returned Through MCP

Depending on the tools the assistant uses and the permissions you approved, Cloudlabels may receive requests for, and return, the following data from your own organization:

• Workspace information: organization name and your name, so the assistant knows which account it is connected to
• Items and sheets: item names, SKUs, barcodes, prices, notes, photos, and other fields you have stored
• Labels and print settings: print profiles, label templates, label designs, and uploaded label assets
• Customers: customer names, account codes and status. Customer and supplier contact details (email, phone, address) are not returned to AI connections in tool responses
• Orders: sales orders, purchase orders, returns, and suppliers, including order lines, quantities, and related records
• Inventory: stock movements and stock levels
• PDFs: generated label and shipping-mark PDFs, returned as download links on a cloudlabels.io domain. Those links expire after 48 hours. Stored PDFs are deleted after about 48 hours (cleanup runs every 6 hours). Each plan also has a cap; when it is reached, the oldest stored PDFs are deleted first. Shipping-mark PDFs may show the customer's delivery address printed on the label
• Item photos and label images: served from a public storage location. Those links do not expire
• Email: if the assistant uses the send_pdf_email tool, Cloudlabels emails a PDF you created. By default it goes to your own Cloudlabels email address. Sending to other recipients is only available to some organizations. Sending to an address outside your organization requires a second, explicit confirmation step before anything is sent. The tool response may include the recipient address (your own email)

The assistant also sends Cloudlabels the tool arguments needed to perform each request, such as search terms, item fields, or recipient addresses. We only use the data your assistant sends to perform the requested action.

7.3 Purpose

We process this data only to perform the actions you request through the assistant, such as listing, creating, updating, printing, or emailing labels and related records, and to secure the service, prevent abuse, and provide support.

7.4 Recipients

• Your AI assistant provider: When you connect an assistant, the tool arguments and results for your requests are sent to the provider you chose, for example OpenAI (ChatGPT, Codex), Anthropic (Claude), or Anysphere (Cursor). That provider processes the data under its own terms and privacy policy, which Cloudlabels does not control. Please review the provider's policy before you connect.
• Email delivery: Emails sent with send_pdf_email are delivered through Resend, our email service provider.
• Recipients you choose: If you send a PDF to other people, those recipients receive the email and the attached PDF.
• Hosting providers: Our hosting providers listed in section 4.
• Image hosts: If you give us an image_url, our server fetches that image from the host you specified.

We do not sell data accessed through MCP.

7.5 Data Retention

• Your Cloudlabels data: Items, labels, customers, orders, and other records are kept until you delete them or delete your account, as described in section 8.
• OAuth connections and API keys: Access tokens expire after 12 hours. Refresh tokens expire after 30 days; each refresh issues a new refresh token. Connections unused for 90 days stop working. Manual API keys expire after at most 365 days, and after 90 days without use. We store access tokens, refresh tokens, and API keys only as hashes, not in plain text.
• Activity log: For security and support, we record one log entry per tool call. It contains your organization, user, connection, the tool name, whether the call succeeded, a short error message if it failed, and a shortened copy of the tool arguments with secrets removed. MCP activity log rows are kept until the organization account is deleted. Deleting an API key or removing a user does not delete existing rows. There is no automatic purge of this log.
• Your AI assistant provider: Data held by the provider is retained according to that provider's policy.

7.6 Your Choices

• Permissions: New connections can read items and print profiles by default. One checkbox additionally allows creating and updating items and printing. Deletion is only granted if the assistant requests it and you allow writing. Customer and supplier contact details are never returned to AI connections in tool responses.
• Revoke access: You can revoke a single connection, or use Revoke all to revoke all of your connections, in Cloudlabels settings. Organization owners and admins can revoke connections for the whole organization. A revoked connection stops working immediately.
• Disconnect in the assistant: Removing Cloudlabels inside the assistant app does not revoke access in Cloudlabels. Use Revoke in Cloudlabels settings to cut off the connection.
• Delete data or your account: You can delete records in the app, or delete your account as described in section 8. You can also contact privacy@cloudlabels.io.

7.7 Organization Isolation

Each connection is tied to one Cloudlabels organization. The key owner must still belong to that organization. Tools only read and write data in that organization. The assistant cannot choose another organization, and Cloudlabels ignores any organization identifier sent in a tool request. Most data access runs with the connected user's own permissions and row-level security; some operations (barcode allocation, PDF and image storage, activity logging) use a server account that filters by organization in code.

Using Cloudlabels through an AI assistant does not change your rights described in sections 9 and 10.

8. Data Retention

We retain your personal data only for as long as necessary to fulfill the purposes outlined in this Privacy Policy, unless a longer retention period is required by law. When you delete your account, we will delete or anonymize your data within 30 days, except where we are required to retain it for legal purposes.

9. Your Rights

Depending on your location, you may have the following rights regarding your personal data:

• Access: Request a copy of your personal data
• Rectification: Request correction of inaccurate data
• Erasure: Request deletion of your data
• Restrict Processing: Request limitation of data processing
• Data Portability: Request transfer of your data
• Object: Object to processing of your data
• Withdraw Consent: Withdraw consent at any time

To exercise these rights, please contact us at privacy@cloudlabels.io.

11. Cookies and Tracking Technologies

We use cookies and similar technologies to:

• Remember your preferences
• Analyze usage patterns
• Improve our service
• Provide personalized content

You can control cookies through your browser settings. However, disabling cookies may affect the functionality of our service.

Types of cookies we use:

• Essential: Required for the service to function
• Analytics: Help us understand how users interact with our service
• Functional: Remember your preferences and settings

12. Children's Privacy

Our service is not intended for children under 16 years of age. We do not knowingly collect personal information from children. If you believe we have collected information from a child, please contact us immediately.

13. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last updated" date. You are advised to review this Privacy Policy periodically for any changes.

14. Contact Us

If you have any questions about this Privacy Policy or wish to exercise your rights, please contact us: