Privacy Policy

Cookie settings

One choice covers analytics and ad cookies. We ask first in the EU/EEA, the UK, Switzerland, Quebec and Brazil. Elsewhere they are on by default, and you can turn them off here or with Cookie settings in the site footer. If your browser sends Global Privacy Control, we treat it as no.

1. Data controller

The data controller is RIPLI LTD, a company registered in England and Wales (Company No. 17120779), with its registered office at 128 City Road, London, EC1V 2NX.

Contact: admin@ripli.ai

2. Data we collect

• Account data: Name, email address, and authentication credentials when you create an account.
• Uploaded content: Product images, logos, packaging photos, and other media you upload for AI processing.
• Shopify app data: Shop domain, Shopify shop ID, granted app scopes, product and media IDs, selected product metadata, app installation state, Shopify billing state, and webhook delivery metadata needed to operate the embedded Shopify app.
• Usage data: Generation history, credit usage, feature interactions, and session analytics.
• Payment data: Processed by Stripe for direct Ripli billing and by Shopify Billing for Shopify-installed merchants. Ripli does not store your card number, CVV, or full card details on our servers.
• Communications: Emails and support messages you send to us.
• Business outreach data: A company name and domain, a published role-based business email address, the public source URL, relevant public product or website details, and our outreach, objection, and suppression records.
• Advertising measurement: Limited records of eligible public page visits and approved sign-up or subscription milestones. Where we ask first, only after you allow it.

3. Shopify embedded app

If you install Ripli from Shopify, Shopify provides app installation and session data so the app can open inside Shopify Admin, load selected products and media, publish generated media back to products, and bill subscriptions or credit top-ups through Shopify Billing.

Ripli currently requests the narrow Shopify scopes read_products, write_products, and write_files for product access, product media updates, and file uploads. Ripli does not request protected customer data scopes such as orders or customer records for the current app experience.

Shopify privacy webhooks are processed at /api/v1/shopify/app/webhooks, including customers/data_request, customers/redact, and shop/redact. Customer data request and redaction webhook payloads are scrubbed during processing. Shop redaction removes or redacts Shopify installation data, staff user records, channel mappings, publish job records, imported Shopify media references, and Shopify billing mirrors within 30 days unless a longer retention period is required for legal, fraud-prevention, accounting, or dispute purposes.

3a. Optional Instagram connection

When you choose to connect an Instagram professional account, Ripli receives the account identifiers, username and account type, an access credential, and the post information and performance metrics needed to show your results. This can include captions, publication times, links and preview references, and available reach, likes, comments, saves and shares. Authorized members of the Ripli workspace where you connect the account can view these results. Only authorized workspace managers can connect, refresh or disconnect the account.

Access credentials are encrypted. Post snapshots stop being shown after seven days and become eligible for removal. A healthy hourly cleanup normally removes them within the following hour. The cleanup reports failures and backlogs for investigation. Disconnecting removes the saved credential and post snapshot from the active service. Verified deletion or deauthorization requests from Meta remove the associated access credential, profile and post data from the active service. A minimal hashed security record prevents an earlier authorization from restoring a deleted connection. It becomes eligible for removal after ten minutes and is normally removed by the next healthy hourly cleanup. It contains no Instagram credential, profile or post content.

Daily disaster-recovery backups may contain earlier copies for up to seven additional days. These copies are kept apart from the active service and expire on the backup schedule. Before restoring service from a backup, we remove restored Instagram connection and post data and require a fresh connection.

This connection displays your own account's posts and available performance data. It does not publish posts, run ads, send messages or modify comments. This feature does not automatically send connected posts or metrics to generative AI services. Post previews may load from Meta's media services.

For customer support, we use technical diagnostics and synthetic examples. We do not transfer your connected Instagram credentials, profile, posts or performance data to personal AI support accounts. You can disconnect in Socials or contact admin@ripli.ai for a data request.

4. Lawful bases for processing

• Contract performance: Processing your data to provide the Ripli service, generate outputs, and manage your account.
• Legitimate interests: Analytics, fraud prevention, service improvement, platform security, and limited relevant business-to-business outreach to corporate subscribers. We apply a purpose, necessity, and balancing assessment before relying on this basis.
• Consent: Marketing to individual subscribers and optional communications where consent is required. You can withdraw consent at any time.

5. Business-to-business outreach

We may contact a company at a role-based business address published on its own website when the message is relevant to that company and the recipient is a corporate subscriber. Before sending, we record the public source, confirm the organisation is a separate legal entity, document why the contact is relevant, and apply a legitimate interests assessment. We do not use this route for sole traders or unincorporated partnerships unless consent or another valid permission applies.

The first message identifies Ripli, explains where the address was found, links to this policy, and provides an unsubscribe option. You may object to direct marketing at any time. We stop marketing to that address and retain only the minimum suppression record needed to honour the objection. We do not use provider open-tracking pixels in this outreach.

6. AI processing and your content

Ripli does not use your uploaded content to train AI models. Your images and media are processed solely to generate the outputs you request. Generated outputs are stored in your account and are not shared with other users or used for model training.

AI model providers process your content only to fulfil generation requests and do not retain your data for their own training purposes under our data processing agreements.

7. Third-party service providers and data recipients

• Stripe: Payment processing. See Stripe's privacy policy.
• Shopify: Embedded app installation, authentication, Admin API access, app billing, and mandatory privacy webhooks for Shopify-installed merchants.
• AI model providers: Image, video, and creative generation. Providers may include OpenAI, Anthropic, Google/Gemini/Veo, Black Forest Labs/fal.ai, xAI/Grok, Qwen, Venice, Sora, and similar providers depending on the selected workflow.
• Hosting and storage providers: Cloud infrastructure for serving the platform and storing uploaded or generated outputs.
• PostHog processes limited product-use events for Ripli in its European cloud. These events use internal user and organisation identifiers and approved product activity fields. They do not include prompts, generated content, names or email addresses. We use this information to understand and improve product reliability and use.
• Google Analytics 4: Measurement using registered page titles, routes, events, and campaign labels. Where we ask first, it runs only after you allow it; elsewhere it is on by default. See Google's privacy policy and business data responsibility information.
• Meta: Meta receives approved event data through the browser Pixel and, only after you allow it, the server Conversions API. Where we ask first, nothing is sent until you allow it; elsewhere the Pixel is on by default. Meta’s role changes with the purpose and stage of processing, as described in section 8.
• Ripli site analytics: Ripli counts page visits and sign-ups by page and country on its own servers. The counts store no IP address, name or email address. They follow the same cookie choice.

8. Optional Meta advertising measurement

Ripli uses one shared Meta Dataset and Pixel. Ripli’s purpose is to understand whether ads on Facebook and Instagram lead to the approved public activity listed below. Where we ask first (the EU/EEA, the UK, Switzerland, Quebec and Brazil), the browser Pixel collects eligible public activity only after you allow it. Elsewhere it is on by default unless you turn it off or your browser sends Global Privacy Control. The server Conversions API (CAPI) may report an approved milestone only if you have allowed it, Ripli has confirmed the milestone, and your choice is still Allow when it is sent.

When these tools are active, Meta may use the approved event data to match activity, provide measurement and analytics, target and deliver ads, improve the effectiveness of ad delivery, personalize features, content, ads and recommendations, and provide, improve and secure Meta products. Meta may combine or aggregate event data with other information as described in its Business Tools Terms and Privacy Policy. This disclosure does not authorize Ripli to upload Customer Lists, create Custom Audiences, select audiences, or use any event outside the categories below. Those activities remain outside this phase and would require separate approval, notice, consent and controls.

On Ripli-owned surfaces, the allowed categories are page visits, new waitlist sign-ups, completed account registration or access, and first paid subscription activation. Shopify controls delivery on its App Store listing, where the categories are listing views, install clicks, and completed app installations. Ripli controls delivery on ripli.ai, its public tools, and its public Studio entry and login pages. Shopify and Ripli delivery remain separate in reporting even though they use one shared Dataset and Pixel.

Where we ask first, Meta browser resources, cookies, similar browser storage, and events stay off until you allow them. You can change your choice at any time with Cookie settings in the site footer. Choosing No thanks stops later browser and server delivery and removes Ripli-owned Meta browser storage. The Conversions API is never used to bypass your choice. Separately, you can use Meta Ad Preferences, including Activity information from ad partners, to control how Meta uses activity received from businesses for ads. Meta controls those settings; Ripli cannot change them for you.

For an approved page visit, Meta may receive the query-free public page address and its page category. After consent, Ripli may also use limited browser-generated Meta identifiers when they are available so Meta can connect an approved milestone to the same visit and avoid duplicate counting. Ripli’s server delivery does not include your email address, IP address, browser or device details, raw page query or referrer, workspace or shop name, prompts, uploaded or generated media, generation activity, downloads, login activity, or activity inside the authenticated Studio workspace.

For the matching, measurement and analytics services that Ripli requests, Ripli is the controller and Meta acts as Ripli’s processor. For collection and transmission through Meta Business Tools for certain advertising-related uses, Ripli and Meta act as joint controllers where applicable. After Meta receives event data and processes it for its own purposes under its terms, Meta acts as an independent controller. For UK personal data, the relevant Meta company is Meta Platforms, Inc.; for EEA personal data, it is Meta Platforms Ireland Limited. Meta’s Privacy Policy identifies the responsible Meta company for other locations. Read Meta’s Business Tools Terms. Meta’s current Business Tools Terms say it may retain event data for up to two years.

9. International data transfers

Your data may be processed outside the United Kingdom by AI model providers and cloud infrastructure services. Where transfers occur, appropriate safeguards are in place, including standard contractual clauses or adequacy decisions recognised by the UK Government.

10. Data retention

• Account data: Retained while your account is active and for a reasonable period after closure for legal and operational purposes.
• Uploaded content: Retained while your account is active. Deleted upon account closure unless required for legal compliance.
• Generated outputs: Retained while your account is active. Available for download during your subscription period.
• Shopify app data: Retained while the app is installed and redacted or deleted after Shopify privacy webhooks, uninstall, or written deletion request, subject to the 30-day Shopify privacy webhook window and legal/accounting retention needs.
• Payment records: Retained as required by UK tax and accounting regulations (typically 6 years).
• Business outreach data: Reviewed routinely and deleted or anonymised when it is no longer relevant. If you object or unsubscribe, we retain a minimal suppression record so we do not contact you again.
• Google Analytics 4: Event-level data is retained for 2 months and user-level data for up to 14 months, with user retention reset on new activity. See Google's data-retention documentation.
• Ripli site analytics: Daily counts are kept for the current month and the 12 months before it. Older records from a previous analytics tool are deleted after no more than 90 days.

11. Your rights

Under UK GDPR, you have the right to:

• Access: Request a copy of the personal data we hold about you.
• Rectification: Request correction of inaccurate personal data.
• Erasure: Request deletion of your personal data ("right to be forgotten").
• Portability: Request your data in a structured, commonly used, machine-readable format.
• Objection: Object to processing based on legitimate interests. Your right to object to direct marketing is absolute, and we will stop that processing.
• Restriction: Request restricted processing in certain circumstances.

To exercise any of these rights, contact us at admin@ripli.ai. We will respond within one month.

You also have the right to lodge a complaint with the Information Commissioner's Office (ICO) at ico.org.uk.

12. Cookies

Ripli uses essential cookies required for the platform to function (authentication, session management). One choice covers analytics and ad cookies: Google Analytics 4, the Meta Pixel, the OpenAI ads tag and Ripli site analytics. In the EU/EEA, the UK, Switzerland, Quebec and Brazil we ask first, and they load only after you allow them. Elsewhere they are on by default. If your browser sends Global Privacy Control, we treat it as no. You can turn them off at any time with Cookie settings in the site footer; this stops collection and removes Ripli-owned analytics cookies and storage. Analytics receives canonical page labels and validated campaign labels (utm_source, utm_medium, utm_campaign) only. We do not collect a raw URL, a raw referrer, utm_term, or utm_content: analytics receives at most the referring site's domain, never a full referrer URL. Where we ask first, Meta's browser Pixel and related cookies or similar storage load only after you allow them, as described above.

13. Changes to this policy

We may update this privacy policy from time to time. Material changes will be communicated via email or a notice on the platform. The "Last updated" date at the top of this page indicates when the policy was last revised.

Contact

For any questions about this privacy policy or your data, contact:
RIPLI LTD
128 City Road, London, EC1V 2NX
admin@ripli.ai