Privacy policy

Raw Guild Studios LLC is the controller for merchant account details, billing records, support chats, bug reports, early-access requests and security logs.

Merchants control their catalog and buyer data. Buyer contact details in order requests, CRM notes and catalog content belong to the merchant who owns the catalog. We process that data on the merchant's behalf only to run the service, under the merchant's instructions and our Terms. Buyers should contact the merchant first about their data.

• Account details: your email address, password (stored only in hashed form), sign-in records, declared business country and confirmation that you are an authorized business representative. We use the declaration to check eligibility for US-only subscriptions; it is not location tracking.
• Catalog content: product data, prices, photos, logos, brand settings and version history you create, plus pricing profiles, share-link settings and team invitations (including teammates' email addresses).
• Order requests: when a buyer submits a request, the buyer's company name, contact name, email, notes, requested products and quantities. These go to the merchant who owns the catalog and any teammate the merchant allows to see requests.
• Merchant notes: private request status, internal notes and company notes merchants add.
• Support: messages you send in the website chat, bug reports (what you write, the page address and browser type, and your email only if you give it), and emails you send us.
• Guest demo: when you start the free demo, our server stores a random demo code (as a one-way hash), a keyed one-way hash of your network address (the full IPv4 address, or the first 64 bits of an IPv6 address), the layout you chose, when it started and whether its one PDF download was used. This is used only to allow one demo per network and to prevent abuse. The hash is derived from your IP address, so we treat it as personal information, not anonymous data. Your sample edits stay in your browser and are not sent to us. People who share a network (for example an office or school) may find the demo already used; email hello@cloudcatalogue.co for help.
• Support chat limits: to keep the AI assistant available and its costs controlled, each AI answer is counted against a limit. For visitors who are not signed in to a paid account, we store a keyed one-way hash of your network address (the full IPv4 address, or the first 64 bits of an IPv6 address) with hourly and daily counts. For signed-in paid accounts, we count by account instead. These counts are derived from your IP address or account, so we treat them as personal information, not anonymous data. They are used only for rate limiting, are separate from the guest demo record, and are deleted automatically after one day without use. People who share a network share its limit.
• Technical data: IP address, browser type and request logs created when you use the site, used for security, abuse prevention and troubleshooting.
• Early-access requests: email, business type, plan interest, comments and your marketing-consent choice.

• To provide the service: save catalogs and versions, generate PDFs, show catalogs to people with your link, deliver order requests and notifications, and support teammates you invite.
• To send service emails you need or choose, such as sign-in and password emails and, if you turn it on, new-request emails.
• To answer support requests and fix bugs.
• To keep the service secure, including rate limits and abuse detection.
• To send product news only if you've opted in. Every marketing email will include our identity and an unsubscribe link. Account, security, billing and order-request emails are service messages, not marketing.

Where laws such as the GDPR apply, we rely on: performing our contract with you (account, catalogs, billing, support); our legitimate interests (security, abuse prevention, fixing bugs, improving the service); your consent (product news, optional emails); and legal obligations (tax and accounting records, lawful requests).

The website chat first answers from built-in help topics, which run in your browser and send nothing to us. Only when you choose "Ask the AI assistant" is your question, with the last few messages of that chat, sent to third-party AI model providers through our hosting platform's AI service to generate a reply. Those AI chats are saved so our team can review conversations and improve support. Don't share passwords or sensitive personal information in the chat.

We don't sell personal information or share it for advertising. We share it only:

• With people you choose: anyone with your share link (catalog content), and teammates you invite (the catalog, and requests only if you allow it).
• With service providers that run the service for us, under their own security commitments: our application hosting, database, file storage and email-delivery platform (Lovable and the cloud infrastructure it uses), AI model providers for the support chat, Cloudflare for domain and email routing, and our email providers for support correspondence.
• With Paddle.com, our reseller and Merchant of Record, for subscription sales, payments, tax compliance and invoicing. We keep only subscription status, plan, billing customer and subscription IDs, your checkout consent record and billing events — never card details.
• When required by law, or to protect users, the public or the service.
• As part of a business transfer, with notice to you.

Photos and logos you upload are stored privately in your account. They are shown only to you, teammates you invite to the catalog that uses them, and people who open an active share link for that catalog, through short-lived signed links.

We use your browser's storage to keep you signed in, to hold unsaved edits until our servers confirm them, to keep guest-demo sample edits and the demo code on your device, and to remember a buyer's last request on the same device. We don't use advertising cookies or third-party ad trackers. Our hosting provider may keep standard server logs. Details are in our Cookie policy.

We keep data only as long as needed. Our schedule:

• Active account and catalog data: while your service is active.
• After paid access ends (expired, cancelled or suspended): merchant content, including catalogs, photos and order requests, is kept view-only for 90 days and then becomes due for deletion. We email you before that date.
• Billing and tax records: generally 7 years, unless the law requires otherwise.
• Checkout agreement records: at least 3 years, or 1 year after your subscription ends, whichever is longer.
• Support chats and bug reports: 24 months after the issue is closed.
• Security logs: generally 90 days.
• Support chat rate-limit counts: deleted automatically about one day after last use.
• Guest demo records: deleted automatically 30 days after the demo starts (a daily cleanup job). After that, the same network can start a demo again.
• Backups: we aim to remove deleted data from backups within 30–60 days, depending on our infrastructure providers.
• Legal holds: if we must keep data for a legal claim, investigation or legal requirement, the hold takes priority over this schedule.

Apart from guest demo records, deletions are currently carried out by our team after checking for legal holds, not automatically. We'll only tell you data has been deleted once that has actually been done.

You can view your stored data while retained. Editing and commercial catalog downloads require an active plan; personal-data export and deletion requests remain available after paid access ends. You can ask us to access, correct, export or delete your personal information, or to stop marketing, by emailing hello@cloudcatalogue.co. Depending on where you live, you may have additional rights under local law — for example in the EU/UK the right to access, correct, erase, restrict or object to processing, data portability, to withdraw consent, and to complain to your data protection authority. We'll respond as the law requires (within one month where the GDPR applies). Signed-in merchants can download their data and request deletion from the Account page.

Buyers: the merchant who owns the catalog controls your order request. Contact them first; we'll help where we can.

We use encrypted connections, hashed passwords, per-account access controls in our database, private file storage, expiring and revocable share links and invite links, and rate limits. No system is perfectly secure; tell us at hello@cloudcatalogue.co if you find a problem.

Cloud Catalogue is currently offered to US businesses. We're based in New York, United States, and our service providers may process data in the United States and other countries. By using the service, your information may be transferred to and processed in those countries. US-only subscriptions do not eliminate international privacy obligations, including where a US merchant submits overseas buyer information. We do not claim GDPR compliance or an approved EU/UK transfer framework. Applicable transfer safeguards, processor contracts and any representative requirements must be assessed; contact us before submitting data that requires an international processing agreement.

Cloud Catalogue is a business tool for people 18 and over. It isn't directed to children, and we don't knowingly collect children's information.

We'll update this policy as the service changes and note the date above; we'll tell account holders about material changes. Questions: hello@cloudcatalogue.co.