Skip to content

Ridvay Privacy Policy

Last Updated: October 9, 2026

This Privacy Policy describes how ridvay.com, owned and operated by Ridvay SIA ("we," "us," or "our"), a limited liability company registered in Latvia, EU, collects, uses, discloses, and protects your information when you visit our website, https://www.ridvay.com (the "Site"), use our mobile application, or use our services (the "Services"). If you use Ridvay inside ChatGPT or Claude, Sections 12 and 13 explain what information is involved there.

Privacy at a Glance

This summary sets out the categories of personal data we collect, the purposes we use it for, the categories of recipients, how long we keep it, and the controls you have. This Privacy Policy is published by Ridvay SIA, a limited liability company registered in Latvia, EU, which owns and operates ridvay.com, the Ridvay mobile app and our other services, including Ridvay in ChatGPT and Ridvay in Claude. The numbered sections below give the full details.

Categories of Personal Data We Collect

  • Account and profile data: your name, email address, password and display name and, if you give it to us, your phone number.
  • Content: the designs, brand kits, prompts, chat messages, study material, pictures, files and documents you create or upload, and the images and videos generated for you.
  • Connected accounts: if you connect a Google, GitHub, Azure DevOps or social media account, the data a feature reads or creates there for you, such as emails, calendar events, Drive files, tasks or code.
  • Payment and subscription data: your plan, your purchase records and your credits. Card details are handled by Stripe, or by Apple or Google for purchases in the mobile app; we do not store them.
  • Usage, device and technical data: the pages and features you use (including page addresses, which can contain a prompt you typed on our homepage, and the text of the buttons and links you click), your IP address, device and browser type, device identifiers, cookies, crash reports from the mobile app and, if you enable location services, your location.
  • Your choices: your sharing settings, and whether and when you agreed to receive marketing emails.
  • Ridvay in ChatGPT: the designs and pictures ChatGPT sends to Ridvay, and our records of those actions.
  • Ridvay in Claude (the Ridvay connector for Claude at mcp.ridvay.com/claude/mcp): the designs Claude sends to Ridvay, the pictures it asks Ridvay to add from a web link, and our records of those actions.

Details: Section 1 and, for ChatGPT and Claude, Section 12 and Section 13.

Purposes of Use

We use personal data to provide the Services, including sending the content an AI feature needs to the AI provider that runs it; to process payments and manage subscriptions; to communicate with you about your account and the Services; to send marketing emails, only if you have agreed to receive them; to keep the Services secure and prevent fraud and abuse; to understand how the Services are used, improve them and develop new features; to measure whether our advertising leads to sign-ups and purchases; to run our affiliate program; to train, fine-tune and evaluate the AI models behind Ridvay's design features, using design prompts and the designs generated from them; and to meet our legal obligations, such as keeping accounting records. We never use designs created or changed through Ridvay in ChatGPT or through the Ridvay connector for Claude (mcp.ridvay.com/claude/mcp) to train, fine-tune or evaluate Ridvay's AI models. If you added Ridvay to Claude with the address mcp.ridvay.com/mcp instead, Section 2 applies to those designs. Section 2 describes each purpose and its legal basis.

Categories of Recipients

  • AI providers that run the AI features you use: OpenAI, Google, OpenRouter (and the company that runs the AI model chosen), Mistral AI, DeepInfra, fal.ai and Replicate (Section 3).
  • Hosting and infrastructure providers: Google Cloud, including Firebase, and Redis Cloud (Section 4).
  • Payment providers: Stripe and, for purchases in the mobile app, Apple's App Store or Google Play, together with RevenueCat.
  • Email delivery providers, such as Amazon SES.
  • Analytics, advertising and cookie-consent providers: Google (Google Analytics, including Firebase Analytics, and Google Ads) and TermsFeed (Section 3).
  • Mobile app service providers: Firebase Crashlytics for crash reports, and Expo for push notifications and app updates.
  • Services you connect: when you ask a feature to post or write to an account you connected, such as TikTok, GitHub or Azure DevOps, that service receives the content.
  • OpenAI, when you use Ridvay in ChatGPT: it receives what Ridvay returns to ChatGPT (Section 12).
  • Anthropic, when you use Ridvay in Claude: it receives what Ridvay returns to Claude and, for the Ridvay connector for Claude, runs Ridvay's design card in Claude (Section 13).
  • Other people: the people you share content with, and anyone who has a share link or views content you make public.
  • Others in limited cases: the affiliate partner who referred you, authorities when the law requires it, and a buyer or successor if Ridvay's business is transferred.

Data Retention

  • Your account and content (profile, designs, brand kits, chats, uploaded and generated files, API keys and settings): kept until you delete them or delete your account. When you delete a single design, its earlier versions, the values set on it, our usage-log records of each design generated for it (with the prompt it came from) and our activity records about it, including copies of the design as it was after each change, are not removed; they are deleted when you delete your account, or earlier if you ask us.
  • Exported files, thumbnails and share preview images: exported files stay available at their links until you ask us to delete them or delete your account. Thumbnails are private and replaced when a design changes; a share preview image is deleted when its design is made private or deleted. Deleting your account deletes all of them, except that a file made before 9 October 2026 that your account no longer links to can stay at its link until you ask us to delete it.
  • After you delete your account, the records we keep include: payment, credit, creator-payout and affiliate records, which we keep to meet our accounting and tax obligations (Stripe also keeps its own invoice and payment records); your email address on our do-not-email list, if you unsubscribed or an email to you bounced or was reported as spam, so that we do not email it again; your account ID for 7 days, so that sign-ins issued before the deletion stop working; messages you sent us through our contact form or to support, until you ask us to delete them; and, if you subscribed to our former newsletter, that subscription record.
  • Training copies: copies of design prompts and generated designs that we have taken to train, fine-tune or evaluate our AI models are not deleted when you delete a design or your account.
  • Backups and deleted files: deleted data can remain in our database backups for up to 30 days, and deleted files can be recovered for 7 days, before they are gone for good.
  • Server logs: deleted after 30 days, except Google Cloud audit logs of administrative changes, which can include the storage path of a file (and with it your account ID) and are kept for 400 days.
  • Analytics: analytics records we store with your account are deleted when you delete your account. Google keeps Google Analytics data for the retention period set in our Google Analytics account. The copy of Google Analytics data we export to our Google Cloud project currently has no automatic deletion date and is not deleted when you delete your account. Crash reports from the mobile app are kept by Firebase Crashlytics (Google) for the period Google sets and are not deleted when you delete your account.
  • AI providers: how long each provider keeps the data it receives is governed by its own terms, summarised in Section 3.
  • Ridvay in ChatGPT: the period for each kind of record is listed in Section 12.
  • Ridvay in Claude (the Ridvay connector for Claude at mcp.ridvay.com/claude/mcp): the period for each kind of record is listed in Section 13.

Your Controls

  • Your rights: you can ask us for access to your personal data, to correct, delete or restrict it, or for a copy of it in a portable format, and you can withdraw any consent you have given at any time (Section 5). To make a request, email legal@ridvay.com.
  • Delete your account yourself at ridvay.com/user/delete. If you pay through the App Store or Google Play, turn off the subscription's auto-renewal first.
  • Marketing emails: turn them on or off in your account settings, or use the unsubscribe link in any marketing email.
  • Cookies: accept or decline analytics and advertising cookies in the cookie banner shown on your first visit. To change your choice later, delete our cookies in your browser and reload the page; Section 6 explains what each choice does.
  • Sharing and connected apps: stop sharing content at any time, and revoke the API keys of connected apps, including ChatGPT and Claude, at ridvay.com/user/api-keys (Section 12 and Section 13).

Contact

Ridvay SIA, Latvia, EU. Email legal@ridvay.com with any question about this policy or your personal data.

1. Information We Collect

We collect information that you provide directly to us and information that we automatically collect when you use the Site and Services.

Information You Provide:

  • Account Information: When you create an account with Ridvay, we collect personal information such as your name, email address, and password.
  • Profile Information: You must provide a display name for your profile. This display name will be publicly visible when you create and share prompts in our Prompt Library. We require a display name (not your email address) to protect your privacy and maintain a professional community environment.
  • Contact Information: We collect contact information, such as your phone number, when you choose to provide it.
  • Payment Information: If you purchase any Services, we collect payment information, such as your credit card details, through Stripe, a secure third-party payment processor. We do not store your payment information.
  • Content You Submit: We collect content that you submit to the Site and Services, including:
    • Chat conversations and messages with AI assistants
    • Prompts you create for the Prompt Library
    • Files, images, videos, and documents you upload
    • Projects and discussions you create
    • Search queries and interactions
  • Mobile App Study Content: If you use our mobile application's study features, we collect:
    • Tutor conversations and messages you exchange with AI tutors
    • Essays, notes, flashcards, and quiz answers you create or submit
    • Photos and images you upload for problem solving
    • Course topics, study plans, and learning progress data
    • Voice conversations conducted through the live voice tutoring feature
    This content is sent to our servers and routed to third-party AI providers to generate personalised tutoring, flashcards, quizzes, essay feedback, and problem solutions. See Section 3 for details on which providers receive this data and how it is protected.
  • Photos and Images (Mobile App): If you use our mobile application, you may choose to:
    • Take photos using your device camera to share with the AI assistant for analysis
    • Select images from your photo library to share with the AI assistant
    • Save AI-generated images to your device photo library
    Important: We do NOT collect, extract, analyze, store, or process any face data, facial recognition data, facial biometric information, or facial features from photos you upload. Photos are used solely for general AI visual analysis (e.g., describing image content, reading text from documents, identifying objects or scenes). No facial recognition, facial detection, facial feature mapping, or biometric data extraction occurs. We treat faces in photos the same as any other visual element (like objects, buildings, or landscapes) for descriptive purposes only.
  • Sharing Preferences: When you share chat conversations, prompts, or projects, we collect information about your sharing settings, including whether content is public or shared with specific users via email invitations.
  • AI Image Generator: When you use the AI Image Generator (the “Image Studio” on web and mobile), the text prompts you write and any images you provide for editing are sent to our third-party image AI providers (such as Fal AI and Replicate) to produce or modify images. The images you generate are stored in your account so they appear in your gallery and history, and you can download or delete them. Generating or editing an image consumes creative credits from your account.

Automatically Collected Information:

  • Usage Data: We collect data about how you interact with the Site and Services, such as the pages you visit, the features you use, chat sessions, AI models selected, and the time spent on the Site.
  • Device Information: We collect information about your device, such as your IP address, operating system, browser type, and unique device identifiers.
  • Location Information: We may collect your location information if you enable location services on your device.
  • Analytics Data: We use analytics tools to understand how users interact with our Services and improve user experience.

2. How We Use Your Information

We use your information for the following purposes:

  • To Provide and Improve Our Services: We use your information to provide you with the Services, including AI chat functionality, prompt library, file processing, and other features. We also use your data to personalize your experience and develop new features.
  • To Process AI Interactions: When you use an AI feature, the content it needs — your prompts, chat messages, study content, designs, and the pictures and files you upload for it — is processed by third-party AI providers to produce what you asked for. Which provider depends on the feature and on the AI model you choose or that is chosen for you; they include OpenAI, Google, OpenRouter (which passes requests on to the company that runs the chosen model, such as Anthropic), Mistral AI, DeepInfra, fal.ai and Replicate. Section 3 lists each provider, what it receives and what its published terms say about keeping data and using it to train AI models. We do not sell your content to AI providers or share it with them for their marketing.
  • To Enable Sharing and Collaboration: When you share chat conversations, prompts, or projects, we use your sharing preferences to control access and enable collaboration with invited users.
  • To Communicate with You: We use your information to communicate with you about your account, the Services, important updates, and respond to your inquiries.
  • To Process Payments: We use your payment information, collected through Stripe, to process payments for Services you purchase and manage subscriptions.
  • To Protect Our Services and Users: We use your information to detect and prevent fraud, unauthorized access, abuse, and other harmful activities.
  • To Analyze and Improve Our Services: We use analytics data to understand how users interact with the Site and Services and to improve our offerings. For this we use Google Analytics (including Firebase Analytics), which receives your Ridvay account ID when you are signed in, in the mobile app your email address, and some text you type or name, such as a prompt you typed on our homepage. To measure whether our advertising leads to sign-ups and purchases, we use Google Ads. These tools use cookies or similar identifiers; Section 3 (“Analytics, Advertising and App Services”) describes what Google receives and Section 6 explains your cookie choices.
  • Improving Our AI Models: We may use the design prompts you write and the designs generated from them to train, fine-tune and evaluate the AI models behind Ridvay's design features. We never do this with designs created or changed through Ridvay in ChatGPT or through the Ridvay connector for Claude (mcp.ridvay.com/claude/mcp) (see Sections 12 and 13). Designs made through Ridvay's general MCP server (mcp.ridvay.com/mcp), including from Claude, are not part of this exception.
  • To Improve Our Integrations and Developer Tools: Content and usage data from Ridvay integrations and developer tools (such as the Ridvay MCP — including prompts and generated designs) may be used to improve Ridvay's products, services, and AI features. This does not apply to designs created or changed through Ridvay in ChatGPT or through the Ridvay connector for Claude (mcp.ridvay.com/claude/mcp): we never use them to train, fine-tune or evaluate Ridvay's AI models (see Sections 12 and 13). It does apply to Ridvay's general MCP server at mcp.ridvay.com/mcp, including when Claude connects to it.
  • To Conduct Marketing and Advertising: We send you marketing emails, such as product news, tips and offers, only if you have agreed to receive them: by ticking the optional box when you sign up on ridvay.com, or by turning on marketing emails in your account settings. The box is never ticked for you. We keep a record of your choice and when you made it. You can withdraw your consent at any time in your account settings or with the unsubscribe link in any marketing email. Emails about your account and the Services, such as sign-in, security, billing and service notices, are not marketing and are sent regardless.
  • To Manage Affiliate Program: If you participate in our affiliate program, we use your information to track referrals and process commission payments.

3. Sharing Your Information

Privacy First Approach: We do not sell or rent your personal information. We share it only in the circumstances described below.

  • Public Content: When you create public prompts in our Prompt Library or mark chat conversations as public, your display name and the content you create will be visible to all users of the platform. Please do not use your email address as your display name to protect your privacy.
  • Shared Conversations and Projects: When you share chat conversations, projects, or discussions with specific users:
    • You can invite users via email to view or collaborate on your content
    • Invited users with "view" permission can read shared content
    • Invited users with "collaborate" permission can add messages and make changes
    • You can revoke access at any time through sharing settings
    • Shared content remains private to invited users unless marked as public
  • AI Service Providers: Ridvay's AI features — creating and editing designs, chat, study tools, and image and video generation — are run by the third-party AI providers listed below. When you use one of these features, we send the provider that runs it the content the feature needs, so that it can process it for us.
    • What Data Is Sent: Depending on the feature:
      • your prompts, chat messages and instructions;
      • for designs: the content of the design you are creating or editing (its text, its layout and descriptions of its pictures) and the pictures you upload or add to it, including a picture you ask us to turn into an editable design;
      • for chat and study features: your conversation, your study material and the files and pictures you attach;
      • for the chat's Google tools, if you connect a Google account: the emails, calendar events, Drive files and tasks the chat reads or creates for you;
      • for code security scans: the code in the repositories you connect;
      • for image and video features: your prompt and the pictures you generate from or edit;
      • for any other AI feature: the content you give it, such as your brand details.
      Your account information (name, email, password) is never sent to AI providers. Anything you put into a prompt, a design or an upload yourself, such as a name, a phone number or a photo of a person, is sent as part of that content.
    • AI providers we use:
      • OpenAI — GPT models in chat, and a backup model when a design cannot be created with our main model. OpenAI says that data sent to its API is not used to train its models unless the customer opts in, and that it keeps abuse-monitoring logs for up to 30 days. developers.openai.com/api/docs/guides/your-data
      • Google (Gemini API) — Gemini models for designs, chat, web search and research answers, and the security scans of code in repositories you connect. We pay for our use of the Gemini API; for paid use, Google's Gemini API terms say Google does not use prompts, files or responses to improve its products. ai.google.dev/gemini-api/terms
      • Google Cloud — Cloud Vision reads the text in a picture you turn into an editable design; Text-to-Speech reads flashcards aloud; Vertex AI turns the study material and documents you add to a notebook or knowledge base, and the questions you ask about them, into embeddings (a numeric index) so that the relevant passages can be found; and the Custom Search API runs the web searches the chat makes on our website, receiving the search words. Google says it does not use content sent to Cloud Vision to train or improve its Vision features (docs.cloud.google.com/vision/docs/data-usage) and does not log the text or audio of Text-to-Speech requests (docs.cloud.google.com/text-to-speech/docs/data-logging), and Google Cloud's terms say Google won't use data sent to Vertex AI to train or fine-tune any AI models without our permission or instruction (docs.cloud.google.com/gemini-enterprise-agent-platform/resources/zero-data-retention).
      • OpenRouter — passes requests on to the company that runs the AI model in use: for most models in chat, and for some of the AI that creates and edits designs. That company is the one that made the model (for example Anthropic, Google, OpenAI, xAI, DeepSeek, Alibaba (Qwen) or Meta) or another company that hosts it. OpenRouter's privacy policy says it does not use inputs or outputs to train models. The company that runs the model handles the request under its own terms; these differ, and some companies may keep the data or use it to improve their models. openrouter.ai/privacy
      • Mistral AI — Mistral models in chat, under Mistral's API terms. legal.mistral.ai/terms
      • DeepInfra — runs some open models in chat, such as Qwen, DeepSeek, Llama, Kimi and gpt-oss models. DeepInfra says it does not store the inputs or outputs of requests and does not use them to train models. docs.deepinfra.com/account/data-privacy
      • fal.ai — generates the pictures in designs and in the Image Studio, and edits pictures: removing backgrounds, erasing objects, extending, upscaling and splitting a picture into layers. fal processes this content under its API terms. fal.ai/privacy
      • Replicate — some image models in the Image Studio and our video generation models. Replicate says the inputs, outputs and logs of API predictions are deleted after one hour by default. replicate.com/docs/topics/predictions/data-retention
      • Pexels — not an AI provider: when a design needs a photo, we may search Pexels' free photo library instead of generating one. Pexels receives only a few search words describing the photo (for example “pyramids at sunset”), never your account details or your pictures.
    • Mobile App: AI features in our mobile app work the same way as on the website: using one sends the content it needs to the providers listed above. Where the app shows its AI Data Usage screen, that screen is a short summary; this section is the full description.
    • Important: We do not sell your data to AI providers or share it with them for their marketing. How long a provider keeps the data, and whether it may use it to train AI models, is governed by that provider's terms, summarised above. How Ridvay itself may use content to improve its own products and AI features is described in Section 2; designs created or changed through Ridvay in ChatGPT or through the Ridvay connector for Claude (mcp.ridvay.com/claude/mcp) are never used to train, fine-tune or evaluate Ridvay's AI models (see Sections 12 and 13).
  • Essential Service Providers: We share limited information with trusted service providers who perform services on our behalf and are contractually obligated to protect your data:
    • Stripe for secure payment processing (we do not store your payment information)
    • Google Cloud Platform for hosting and infrastructure
    • Redis Cloud (Redis Ltd.), hosted on Google Cloud in the United States, for usage, credit and analytics counters and to recognise repeated pictures
    • Email service providers for transactional emails (account verification, password reset, etc.)
    • Amazon Web Services (Amazon SES) for sending email
  • Analytics, Advertising and App Services: We also share limited information with these companies:
    • Google (Google Analytics, including Firebase Analytics, and Google Ads) receives information about how you use the Site and the app: the pages and features you use, including the address of each page you open, which can contain the text of a prompt you typed on our homepage; events such as signing up, opening or generating a design, and purchasing; the text of the buttons and links you click, which can include names you gave your own content, such as a project name; error messages from the Site; in the mobile app, your Prompt Library searches and the names of courses you create; your device and browser details; your IP address; and, when you are signed in, your Ridvay account ID and, in the mobile app, your email address. We use it to understand how the Services are used and to measure whether our advertising leads to sign-ups and purchases. On our website, unless you decline in our cookie banner, or you are in the European Economic Area, the United Kingdom or Switzerland and have not accepted, Google may also use this information under its own terms, including to personalise ads. A copy of our Google Analytics data is exported to our Google Cloud project.
    • TermsFeed provides our cookie banner. Its script is loaded from termsfeed.com, which therefore receives your IP address and browser details; your cookie choices are stored in a cookie on your device.
    • Apple, Google and RevenueCat: purchases in the Ridvay mobile app are made through Apple's App Store or Google Play, which handle your payment, and are recorded through RevenueCat, which receives your Ridvay account ID and your purchase and subscription details so that we know which plan you have.
    • Mobile app services: Firebase Crashlytics (Google) receives crash reports from the app together with your Ridvay account ID; when you allow notifications, the app registers your device with Expo's push-notification service, which receives your device's push token; and the app downloads its updates from Expo's servers.
    See Section 6 for your cookie choices.
  • Services You Connect: When you ask a feature to post or write to an account you connected, such as TikTok, GitHub or Azure DevOps, that service receives the content you asked it to post or write.
  • Affiliate Partners: If you were referred to Ridvay through an affiliate link, we share limited information (referral success, commission amounts) with the referring affiliate partner.
  • Legal Requirements: We may disclose your information if required by law or regulation, or to comply with a legal process, court order, or government request.
  • Protection of Rights: We may disclose your information to protect the rights, property, or safety of Ridvay, our users, or others, including to detect and prevent fraud or security issues.
  • Business Transfers: If Ridvay is involved in a merger, acquisition, or sale of assets, your information may be transferred as part of that transaction. We will notify you before your information is transferred and becomes subject to a different privacy policy.

4. Data Security and Storage Location

We take reasonable measures to protect your information from unauthorized access, use, or disclosure. Stripe handles all payment processing with its own robust security measures. However, no website or online service is completely secure. Therefore, we cannot guarantee the absolute security of your information.

Data Storage and International Transfers

Physical Data Location: Your data is primarily stored and processed in the following locations:

  • Primary Infrastructure: Our services are hosted on Google Cloud Platform in the United States. This includes:
    • User account information and authentication data
    • User profile data and subscription information
    • Chat conversations and interaction history
    • Generated images and media files
    • Application analytics and usage data
  • Where Your Data Is Stored and Processed: The files you upload or create, such as pictures, generated images and exported designs, are stored in Google Cloud Storage in South Carolina (us-east1). Your designs, chats and account records are kept in Google Cloud Firestore databases in South Carolina (us-east1) and in a US multi-region that replicates between Iowa (us-central1) and Northern Virginia (us-east4). Our application servers, including the service that draws exported files, thumbnails and share images and measures a design's text, run on Google Cloud Run and Cloud Functions in Iowa (us-central1); temporary rendering data there is deleted after one day. A few background tasks for chat memory run in South Carolina (us-east1). Sign-in is handled by Google Firebase Authentication, which processes data only in the United States.
  • Other Service Providers: We also use Redis Cloud (Redis Ltd.), hosted on Google Cloud in Iowa (us-central1), for usage, credit and analytics counters and for the fingerprints that recognise repeated pictures, and Amazon Web Services (Amazon SES, Northern Virginia, us-east-1) to send email.
  • Content Delivery: Our website, shared designs and the images in them are delivered through Google's global network, so copies may be cached briefly at locations near you.
  • AI Processing: When you use AI features, your data is processed by the AI providers named in Section 3, which may operate in the United States and other regions. How long each provider keeps it is governed by that provider's terms, summarised in Section 3.

International Data Transfers and GDPR Compliance

For Users in the European Economic Area (EEA), United Kingdom, and Switzerland:

  • Data Transfer Mechanism: When you use our Services from the EEA, UK, or Switzerland, your personal data will be transferred to and processed in the United States. We rely on appropriate safeguards for these international data transfers, including:
    • Google Cloud Platform's compliance with the EU-U.S. Data Privacy Framework and standard contractual clauses
    • Contractual commitments with our service providers to protect your data in accordance with GDPR standards
  • Adequacy of Protection: Our infrastructure provider (Google Cloud Platform) implements technical and organizational measures to ensure an adequate level of protection for your personal data equivalent to that provided within the EEA, including:
    • Encryption of data in transit and at rest
    • Access controls and authentication mechanisms
    • Data breach notification procedures
    • Compliance with GDPR data protection principles
  • Your Rights: As an EEA, UK, or Swiss resident, you retain all rights under GDPR and applicable data protection laws, including the rights described in Section 5 of this Privacy Policy.

For more information about our infrastructure provider's data protection measures:

5. Your Rights

You have certain rights regarding your information, including the right to:

  • Access: You can request access to the personal information we hold about you.
  • Correction: You can request that we correct any inaccurate or incomplete information we hold about you.
  • Deletion: You can delete your account yourself at any time. If you pay for Ridvay through the App Store or Google Play, turn off the subscription's auto-renewal first, because we cannot cancel it for you. Deleting your account permanently deletes your designs, chats, uploaded and generated files, API keys and settings from our live systems straight away. Some records are kept after that; the summary at the top of this policy lists the main ones under “Data Retention”. You can also ask us to delete your personal information. Delete your account
  • Restriction: You can request that we restrict the processing of your personal information.
  • Portability: You can request that we provide you with a copy of your personal information in a portable format.
  • Opt-out of Marketing: You can opt out of receiving marketing communications from us at any time.

6. Cookies and Tracking Technologies

We use cookies and similar technologies, such as your browser's local storage, on the Site. Some are strictly necessary, for example to keep you signed in and to remember your cookie choices. Others are used for analytics and advertising by Google Analytics and Google Ads; Section 3 (“Analytics, Advertising and App Services”) explains what Google receives.

Our website also contains code for the Meta Pixel, Meta's advertising measurement tool, but our site's security settings currently stop it from loading, so it does not run and sends nothing to Meta.

When you first visit, our cookie banner, provided by TermsFeed, lets you accept or decline analytics and advertising cookies, or choose by category. If you are in the European Economic Area, the United Kingdom or Switzerland, Google Analytics and Google Ads do not use cookies until you accept them, although Google can still receive cookieless measurement signals. Elsewhere, these tools are on by default. If you decline in the banner, Google Analytics and Google Ads stop using cookies from the next time you open or reload the Site.

The banner is shown on your first visit. To change your choice later, delete our cookies, including the one that stores your choice, in your browser settings and reload the Site; the banner then asks again. You can also block cookies in your browser settings.

7. AI-Generated Content and Limitation of Liability

IMPORTANT DISCLAIMER: Our Services utilize artificial intelligence to generate responses, images, and other content. You acknowledge and agree to the following:

  • No Warranty of Accuracy: AI-generated content may contain errors, inaccuracies, hallucinations, or misleading information. We make no representations or warranties regarding the accuracy, reliability, completeness, or currentness of any AI-generated content. You should independently verify all AI-generated information before relying on it.
  • Not Professional Advice: AI-generated content does NOT constitute professional advice of any kind, including but not limited to:
    • Medical, health, or wellness advice
    • Legal advice or legal opinions
    • Financial, investment, or tax advice
    • Professional consulting or expert recommendations
    Always consult qualified professionals for important decisions affecting your health, legal rights, finances, or other critical matters.
  • User Responsibility for Decisions: You are solely responsible for any decisions, actions, or outcomes resulting from your use of AI-generated content. We are NOT liable for:
    • Decisions made based on AI-generated responses or recommendations
    • Financial losses resulting from AI-generated advice or information
    • Health consequences from following AI-generated health or wellness information
    • Legal consequences from relying on AI-generated legal information
    • Any damages, losses, or injuries resulting from your use of the Services
  • Content Moderation: While we implement safety measures and content filtering, AI may occasionally generate inappropriate, offensive, or harmful content. We are not responsible for such content, and users should report any problematic outputs.
  • Third-Party AI Models: We use various third-party AI models and providers. We are not responsible for the performance, accuracy, biases, or limitations of these third-party models.

Template Submission & Content Guidelines

When you create and submit templates to our platform (including image generation templates, prompts, and other creative content), please be aware of the following important guidelines and limitations:

  • AI-Generated Content Ownership: You do not own or have copyright over content generated by others using your prompts or templates. AI-generated images, text, and other outputs created by users of your templates are not subject to traditional copyright protection in most jurisdictions. When you publish a template, you are sharing the prompt/instructions, not claiming ownership of what others create with it.
  • Public Availability: When you submit a public template, your prompt will be publicly available for others to use. Please do not include any personal, sensitive, or proprietary information in your prompts.
  • Copyright Restrictions: Copyrighted content cannot be published as prompts or templates. Do not submit content that infringes on the intellectual property rights of others, including copyrighted images, text, or other protected materials.
  • Parental Supervision Required: This application requires parental supervision for minors. Parents and guardians are responsible for monitoring their children's use of the Services.
  • Content Moderation: We reserve the right to review, modify, or remove any submitted templates or content that violates our Terms of Service, this Privacy Policy, or applicable laws.

Creative Credits & Template Usage:

  • How Credits Work: When you use a template to generate images or other content, you consume creative credits from your account. Credits are deducted regardless of whether you are satisfied with the generated output, as computational resources are used for each generation request.
  • Template Variability: AI generation is inherently variable and probabilistic. Using the same template multiple times may produce different results. Example images shown in templates are representative samples and do not guarantee identical or similar outputs.
  • No Guaranteed Results: Templates are provided "as-is" without any guarantee that generated content will match your expectations, the template description, or the example images. AI models may interpret prompts differently, and results can vary based on numerous factors including model version, settings, and random variation.
  • Template Quality Concerns: If you believe a template does not produce results consistent with its description or example images:
    • You can report the template through our platform, and we will review it for accuracy and compliance with our guidelines
    • We may update, modify, or remove templates that are misleading or do not function as described
    • However, we cannot provide refunds or credit reimbursements for templates that produce unsatisfactory results, as credits are consumed during the generation process
    • We encourage users to start with small tests before committing significant credits to any template
  • User Responsibility: Users are responsible for reviewing templates and understanding that AI generation is not deterministic. We recommend testing templates with minimal credits before large-scale usage.
  • Template Creator Accountability: Template creators should provide accurate descriptions and representative example images. Deliberately misleading templates may result in removal and potential account restrictions.

8. Children's Privacy

The Site and Services are not intended for children under the age of 13. We do not knowingly collect personal information from children under 13. As noted above, parental supervision is required for minors using our Services.

9. 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 the Site.

10. Contact Us

If you have any questions about this Privacy Policy, please contact Ridvay SIA at legal@ridvay.com.

11. Stripe's Privacy Policy

You can find more information about Stripe's privacy practices at: https://stripe.com/privacy.

12. Ridvay in ChatGPT

Ridvay can be used inside ChatGPT, a service operated by OpenAI. This section explains what happens to your information when you connect your Ridvay account to ChatGPT and use Ridvay there. The rest of this Privacy Policy also applies; where this section is more specific, it governs your use of Ridvay in ChatGPT.

How the Connection Works

  • Signing In: You connect Ridvay by signing in to your Ridvay account on ridvay.com and approving access for ChatGPT. ChatGPT does not see your Ridvay password, and Ridvay does not receive your ChatGPT password.
  • Access Key: When you approve, we create an API key for your Ridvay account and give it to ChatGPT, which sends it with every request it makes to Ridvay for you. With this key, ChatGPT can list, read and change all the designs in your Ridvay account — including designs you made on ridvay.com or in the Ridvay app — create new ones, read your brand kits, add pictures, export files and share designs. The key is named after the app that connected, followed by “(OAuth)” — for example “ChatGPT (OAuth)”. It does not expire: it works until you revoke it. We store the key, its name, your account ID, the time it was created, the ID of the app it was created for, and a label that switches Ridvay's AI features off for this key.
  • Sign-in Records: While you approve the connection, we keep a short record of the request: which app asked, the address to send you back to, a security check value, the access requested and, once you approve, your account ID and a one-way hash of the single-use code. These records expire within about 20 minutes and are then deleted automatically.
  • No Ridvay AI: In ChatGPT, ChatGPT itself composes and edits your designs. Ridvay stores them, shows them in the Ridvay editor, draws image files and creates share links. Ridvay does not run any AI models of its own for requests from ChatGPT, and does not send your designs or pictures to any AI provider: our servers switch Ridvay's AI features off for the ChatGPT connection.
  • The Editor in ChatGPT: When ChatGPT shows you a design, the Ridvay editor opens inside ChatGPT. It is loaded from ridvay.com, runs on your device, and saves your changes directly to your Ridvay account. It signs in to your account with a sign-in token that lasts about one hour and is renewed through ChatGPT while the editor is open. In ChatGPT, the editor has no Ridvay AI features and cannot upload files from your device, export or share.

Information We Collect and Why

  • Designs: The designs ChatGPT creates or changes for you, and the changes you make by hand in the editor: the title, pages, text, layout, colours, fonts, links to pictures and logos, any variables and their values, and the web addresses of any live data sources the design reads values from. Anything you ask ChatGPT to put into a design — for example names, phone numbers, addresses or photos of people — becomes part of that design. Each design has an ID, a version number and the time of its last change; designs created through ChatGPT are labelled as such.
  • Pictures: When you ask ChatGPT to add a picture from your conversation (one you uploaded or one ChatGPT created), ChatGPT gives Ridvay a temporary link to the file and the file's ID (and sometimes the file's name and type, which we do not store), and our server downloads the file once from that link. We only accept links to files stored by ChatGPT, up to 15 MB, in PNG, JPEG, WebP or GIF format. We then re-encode the picture: this removes embedded information such as camera details and GPS location, keeps only the first frame of an animation, and shrinks pictures larger than 2,048 pixels on their longest side. Only the re-encoded copy is stored, in your account's storage; the ChatGPT link is not saved. You can add up to 5 new pictures a day this way. Adding the same picture again within 30 days reuses the stored copy and does not count against that limit; to recognise repeats, we keep a fingerprint (a SHA-256 hash) of each picture's contents together with the stored picture's link and size.
  • Exports: When you ask for a PNG or JPEG file, we record an export job (its ID, your account ID, the design, the format, size and page requested, its status, the times it was created and updated, and the file's link or an error message), and our rendering service draws the file. A daily export limit applies.
  • Sharing: When you ask ChatGPT to share a design, we mark it as shared and create its share links and, while you are within the daily export limit, a preview image used when the link is shown in other apps (it counts as one export). We count how many times a shared design is viewed each day and keep the referring page and browser type of the latest view. When you ask ChatGPT to change a design's values (for example a price on a menu), we save the new values.
  • Brand Kits: If your Ridvay account has brand kits, ChatGPT can read them so it can design in your brand's style. Brand kits are created and changed on ridvay.com; ChatGPT cannot change them.
  • Usage Counts: We count the pictures you store and the exports you make through ChatGPT, per day and per month, to apply the daily limits.
  • Version History: Each design keeps earlier versions, so a change made by you or by ChatGPT can be undone on ridvay.com.
  • Activity Records: Each time a design is created, changed or shared through ChatGPT — including every save the editor makes while you edit inside ChatGPT — we keep an internal record of the action: the time, the design's title and version, a short description of what changed, a label showing where it came from and, for creations and changes, a copy of the design as it was afterwards. For each design created through ChatGPT we also keep an entry in our internal usage log with a copy of the design, its title and its thumbnail.
  • Technical Information: Requests from ChatGPT reach Ridvay from OpenAI's servers, not from your device. The editor, however, runs on your device and connects directly to ridvay.com and our servers, which therefore receive your device's IP address and browser details, as with any visit to our website. Your device loads a design's pictures from where they are stored — usually Google Cloud — or, if a design uses a picture from another website, from that website. The editor uses your ChatGPT language setting to show its interface in your language. Our servers keep technical logs of requests for security and troubleshooting.
  • What We Do Not Receive: Ridvay does not receive your ChatGPT conversation as a whole. It receives only what ChatGPT sends when it uses Ridvay: for example the content of a design, a picture's file link, or a word to search your designs for. ChatGPT may attach general information to these requests, such as your language, your app or browser type, an approximate location and an anonymous ID; Ridvay does not use or store it.
  • Why We Use It: We use this information to provide Ridvay in ChatGPT: to save your designs to your account and show them to you and to ChatGPT, to keep ChatGPT and the editor in step when both change a design, to store your pictures, make exports and create share links, to apply the daily limits, to keep the service secure and prevent abuse, and to give you support. Authorised Ridvay staff can view designs and these records to give support, investigate problems and check the quality of the service.
  • Not Used to Train AI: We never use designs created or changed through Ridvay in ChatGPT to train, fine-tune or evaluate Ridvay's AI models — neither their content nor the records and usage-log entries we keep about them. Once a design has been created or changed through ChatGPT, it stays excluded, even if you later edit it on ridvay.com or in the Ridvay app. This covers Ridvay connected to ChatGPT as described in this section. If you instead add Ridvay to ChatGPT yourself with a Ridvay API key you created (for example as a custom connector), Section 2 (“To Improve Our Integrations and Developer Tools”) applies, as it does to our other developer tools.

What Ridvay Sends to ChatGPT

When ChatGPT uses Ridvay, Ridvay sends back the information needed for your request, and ChatGPT — and therefore OpenAI — receives it. Depending on the request, this can include:

  • Designs: the design ID (design_id), title, version number (version), time of the last change (updated_at), whether the design is shared (is_public), number of pages (page_count) and which page is shown (page_index), a link to a thumbnail image that stops working after one to two hours (thumbnail_url), how many designs matched a search (total), a short description of a change (summary), and the full content of a design (design): its text, layout, colours, fonts, picture and logo links, variables, the web addresses of any live data sources it reads values from, and any notes saved with it, such as the request a design was originally generated from on ridvay.com. This applies to any design in your account, including designs you made outside ChatGPT.
  • Brand Kits: the brand kit ID (brand_id), name, whether it is your default (is_default), colours (colors), heading and body fonts (heading_font, body_font), logo links (logo_urls), brand voice (voice), tagline (tagline) and business name (business_name).
  • Pictures: the link to the stored picture (src), its width and height, whether it had already been stored (deduped), and where it was placed: the design ID, version, page and element ID (element_id, which is derived from a one-way hash of ChatGPT's file ID). Links to files stored by Ridvay — pictures, brand kit logos, exported files, thumbnails and share preview images — can contain your Ridvay account ID.
  • Exports: the export job ID (job_id), its status, the file format, and the link to the finished file (url).
  • Sharing: whether the design is shared (is_public, shared) and its share links (links): the view page (view_url), a link that opens an editable copy (edit_url), an always-current image of the design (live_image_url) and a full-screen display page (screen_url).
  • Design Values: the values set on a design (values) and the names of the variables the design has (declared).
  • The Editor in ChatGPT: to open the editor, Ridvay provides a sign-in token for your Ridvay account and the time it expires (expires_at). The token contains your account ID and the details of your Ridvay sign-in profile: your email address and, if your account has them, your name, profile picture link, phone number and the IDs of the accounts you sign in with (for example Google). The token also states whether your email address is verified, the time it was issued, when it expires and the time of this sign-in, a label marking it as an editor sign-in for ChatGPT and, if your account has them, the labels stored with your sign-in profile: your Ridvay subscription level (for a plan bought on ridvay.com through Stripe), your in-app purchase entitlements (for purchases made in the Ridvay app and recorded through RevenueCat) and, for Ridvay staff, an administrator flag. ChatGPT passes the token on to the editor; it is not shown to the AI model. Ridvay also sends the editor the latest version of the open design (its ID, version, time of the last change, whether it changed, which version ChatGPT last saved, and its full content). When you edit a design by hand, the editor adds a short summary of your changes (up to 1,500 characters), with the design ID and version, to ChatGPT's context so that ChatGPT knows about them; otherwise it notes only which design is open.
  • Messages: confirmations and error messages, which can include how many of your daily pictures or exports you have used and when the limit resets.

Who Receives Your Information

  • OpenAI: Everything Ridvay sends to ChatGPT, as listed above, is received by OpenAI and handled under OpenAI's own privacy policy (openai.com/policies/privacy-policy). Your conversations with ChatGPT are governed by OpenAI's terms and privacy policy, not by this one.
  • Google: Ridvay is hosted on Google Cloud in the United States, which stores your designs, pictures and exported files and runs our servers (see Section 4 for the exact locations). The editor's sign-in token is issued through Google's Firebase Authentication. The editor loads typefaces from Google Fonts, so Google receives your device's IP address and the names of the fonts a design uses when the editor opens.
  • Our Rendering Service: Ridvay's own rendering service draws exported files, thumbnails and share preview images, and measures the text of a design when it is saved; it receives the design's content to do so. It runs on Google Cloud Run and Cloud Functions in Iowa (us-central1), and the temporary data it keeps while drawing a file is deleted after one day.
  • Redis Cloud: The daily and monthly counts of the pictures you store and the exports you make, and the fingerprints that recognise repeated pictures, are kept in Redis Cloud, a database service run by Redis Ltd. on Google Cloud in Iowa (us-central1).
  • Anyone With a Link: Share links are not protected by a sign-in. Anyone who has a share link can view the design, see its always-current image, show it full screen and save an editable copy of it to their own Ridvay account. A shared design's page is a public web page, so if its link is posted publicly, search engines may find and list it. The links to stored pictures, exported files and share preview images are long and hard to guess, but they are not protected by a sign-in either: anyone who has such a link can open the file. A thumbnail link works the same way, but only for one to two hours (up to seven days in an email from us); after that it stops working.
  • No Sale: We do not sell this information. Apart from returning results to ChatGPT, Ridvay does not send it to any AI provider. The disclosures in Section 3 for legal requirements, protection of rights and business transfers also apply.

How Long We Keep It

  • Designs and Brand Kits: kept in your account until you delete them (you delete brand kits in the Brand Kit panel of the Ridvay editor on ridvay.com).
  • Version History: up to 60 versions per design; older versions are removed as new ones are saved. Version history and the values set on a design are not removed automatically when you delete the design — ask us and we will delete them. Deleting your Ridvay account deletes all of them.
  • Activity Records: activity records, usage-log entries and the daily view counts of shared designs are kept until you ask us to delete them or you delete your Ridvay account; they are not removed when you delete a single design.
  • Stored Pictures and Files: stored pictures and exported files stay available at their links until you ask us to delete them or you delete your Ridvay account; deleting a design or a brand kit does not delete them. A design's thumbnail is replaced, and the old one deleted, each time the design changes, and is deleted when you delete the design. Its share preview image is kept while the design is shared and deleted when you make the design private, delete it, or share it again. Deleting your Ridvay account deletes the pictures, exported files, thumbnails and share preview images filed under your account, and the images drawn for your shared designs' always-current image links. Files made before 9 October 2026 were not filed under your account: we delete those your designs and export records still link to, but an older exported file, or a thumbnail or share preview image that had already been replaced before that date, can stay at its link — send us the link and we will delete it. After we delete a file, Google Cloud keeps a recoverable copy for 7 more days.
  • Picture Fingerprints: 30 days after the picture is stored, then deleted automatically.
  • Export Job Records: expire 7 days after the export was requested and are then deleted automatically. The exported file itself stays available at its link, as described above.
  • Usage Counts: deleted automatically at the end of the day or month they count (UTC).
  • Sign-in Records: expire within about 20 minutes and are then deleted automatically.
  • Access Key: kept until you revoke it.
  • Editor Sign-in Tokens: not stored by Ridvay; each one stops working after about one hour.
  • Connector Notes: to tell ChatGPT's changes apart from yours, the service that connects Ridvay to ChatGPT notes which design versions ChatGPT saved (the design ID, version numbers and the time of the last save only). These notes are held only in the service's memory and never written to disk; they are no longer used after six hours, are dropped when newer notes need the room, and are lost whenever the service restarts.
  • Technical Logs: kept for 30 days, then deleted automatically.

Your Choices and Controls

  • Disconnecting: You can disconnect Ridvay in ChatGPT's settings at any time. To make sure the connection is closed on our side too, revoke its key at ridvay.com/user/api-keys (the key whose name ends in “(OAuth)”, for example “ChatGPT (OAuth)”). Revoking it stops ChatGPT's access to your account straight away; an editor that is already open can keep working for up to an hour.
  • Deleting Designs: Ridvay's tools in ChatGPT cannot delete designs. You can delete them at ridvay.com/studio/my-designs.
  • Stopping Sharing: Ask ChatGPT to make a design private, or change it in Ridvay. Its share links then stop working, although copies cached along the way can take a short time to expire, and search engines can take longer to drop a page they already listed. Copies that other people already saved, and files they downloaded, are not affected.
  • Choosing What You Share: Ridvay receives only what ChatGPT sends when it uses Ridvay, such as the content it puts into your designs and the pictures it adds. Leave out of your requests anything you do not want stored in your Ridvay account, and check a design in the editor before you share it.
  • Your Rights: You have the rights described in Section 5, including access, correction, deletion and a copy of your data. You can delete your Ridvay account yourself at ridvay.com/user/delete; that deletes your designs, version history, design values, activity records and stored pictures with it. To have single items or exported files deleted, email legal@ridvay.com.
  • Your ChatGPT Data: What ChatGPT keeps from your conversations is controlled in ChatGPT and described in OpenAI's privacy policy.

13. Ridvay in Claude

Ridvay can be used inside Claude, an AI assistant operated by Anthropic, through the Ridvay connector for Claude at https://mcp.ridvay.com/claude/mcp (“Ridvay in Claude”). This section explains what happens to your information when you connect your Ridvay account to Claude through that connector and use Ridvay there. The rest of this Privacy Policy also applies; where this section is more specific, it governs your use of Ridvay in Claude. It does not cover Ridvay's general MCP server at https://mcp.ridvay.com/mcp, which Claude apps such as claude.ai, Claude Desktop and Claude Code can also connect to and which includes Ridvay's AI features; if you added Ridvay to Claude with that address, Section 2 describes how we use data from it.

How the Connection Works

  • Signing In: You connect Ridvay by signing in to your Ridvay account on ridvay.com and approving access for Claude. Claude does not see your Ridvay password, and Ridvay does not receive your Claude password.
  • Access Key: When you approve, we create an API key for your Ridvay account and give it to Claude, which sends it with every request it makes to Ridvay for you. With this key, Claude can list, read and change all the designs in your Ridvay account — including designs you made on ridvay.com or in the Ridvay app — create new ones, read your brand kits, add pictures, export files and share designs. It cannot delete designs or your Ridvay account. The key is named “Claude (OAuth)”. It does not expire: it works until it is revoked, and each time you connect again, a new key is created. We store the key, its name, your account ID, the time it was created, the ID of the app it was created for, and labels that switch Ridvay's AI features off for this key and mark it as the Claude connection.
  • Sign-in Records: While you approve the connection, we keep a short record of the request: which app asked, the address to send you back to, a security check value, the access requested, the Ridvay address the access is for and, once you approve, your account ID and a one-way hash of the single-use code. These records expire within about 20 minutes and are then deleted automatically.
  • No Ridvay AI: In Claude, Claude itself composes and edits your designs. Ridvay stores them, draws image files and preview images, and creates share links. Ridvay does not run any AI models of its own for requests from Claude through this connector: our servers switch Ridvay's AI features off for this connection.
  • The Design Card: When Claude creates, changes or shows a design, Claude can display a Ridvay design card in your conversation: the design's title, version, number of pages and a preview image, with an “Open in Ridvay” button. The card is a small web page from Ridvay that Claude runs on a separate web address Anthropic provides for it (under claudemcpcontent.com). It gets its information from Ridvay through Claude and does not connect to Ridvay's servers itself. To show the preview, your device loads the design's thumbnail image directly from Google Cloud Storage, through a link that stops working after one to two hours (the card asks for a new one when it is shown again). While a new thumbnail is being made after a change, the card asks Ridvay for it again for up to about five minutes. “Open in Ridvay” opens ridvay.com in your browser, which shows the design only when you are signed in to the same Ridvay account there; Claude may ask you to confirm before it opens the link. The card cannot change, export or share a design.

Information We Collect and Why

  • Designs: The designs Claude creates or changes for you: the title, pages, text, layout, colours, fonts, links to pictures and logos, any variables and their values, the web addresses of any live data sources the design reads values from, and any notes Claude saves with a design. Anything you ask Claude to put into a design — for example names, phone numbers, addresses or photos of people — becomes part of that design. Each design has an ID, a version number and the time of its last change; designs created through Claude are labelled as such.
  • Pictures: When you give Claude a public https link to a picture and ask it to add the picture, Claude passes the link to Ridvay, and our server downloads the picture once from that address. We only accept https links to files up to 15 MB in PNG, JPEG, WebP or GIF format. Pictures you upload into a Claude conversation cannot be passed to Ridvay. We then re-encode the picture: this removes embedded information such as camera details and GPS location, keeps only the first frame of an animation, and shrinks pictures larger than 2,048 pixels on their longest side. Only the re-encoded copy is stored, in your account's storage; we do not keep the link it was downloaded from. You can add up to 5 new pictures a day this way, counted together with pictures added through Ridvay in ChatGPT. Adding the same picture again within 30 days reuses the stored copy and does not count against that limit; to recognise repeats, we keep a fingerprint (a SHA-256 hash) of each picture's contents together with the stored picture's link and size.
  • Exports: When you ask for a PNG or JPEG file, we record an export job (its ID, your account ID, the design, the format, size, quality and page requested, its status, the times it was created and updated, and the file's link or an error message), and our rendering service draws the file. A daily export limit applies, counted together with exports made through Ridvay in ChatGPT.
  • Sharing: When you ask Claude to share a design, we mark it as shared and create its share links and, while you are within the daily export limit, a preview image used when the link is shown in other apps (it counts as one export). We count how many times a shared design is viewed each day and keep the referring page and browser type of the latest view. When you ask Claude to change a design's values (for example today's special on a menu), we save the new values.
  • Brand Kits: If your Ridvay account has brand kits, Claude can read them so it can design in your brand's style. Brand kits are created and changed on ridvay.com; Claude cannot change them.
  • Thumbnails: As for every Ridvay design, our rendering service makes a small image of a design's first page after it changes. It is shown on the design card and in your list of designs on ridvay.com. Thumbnails are stored privately: Ridvay hands out only links to them that stop working after one to two hours. A new thumbnail is made after each change and the previous one is deleted.
  • Usage Counts: We count the pictures you store and the exports you make through Claude and ChatGPT, per day and per month, to apply the daily limits.
  • Version History: Each design keeps earlier versions, so you can return to an earlier state of a design on ridvay.com.
  • Activity Records: Each time a design is created, changed or shared through Claude, we keep an internal record of the action: the time, the design's title and version, a short description of what changed, a label showing it came from Claude and, for creations and changes, a copy of the design as it was afterwards. For each design created through Claude we also keep an entry in our internal usage log with a copy of the design, its title, a label showing it came from Claude and any notes saved with it.
  • Technical Information: Requests from Claude reach Ridvay from Anthropic's servers, not from your device. When you sign in to connect Ridvay, or open a design with “Open in Ridvay”, your browser visits ridvay.com, which receives your device's IP address and browser details, as with any visit to our website. Our servers keep technical logs of requests for security and troubleshooting.
  • What We Do Not Receive: Ridvay does not receive your Claude conversation as a whole, and it cannot read your Claude chat history, memory or the files you upload to Claude. It receives only what Claude sends when it uses Ridvay: for example the content of a design, a link to a picture, or a word to search your designs for. Ridvay's tools use only these details and do not store anything else Claude attaches to a request.
  • Why We Use It: We use this information to provide Ridvay in Claude: to save your designs to your account and show them to you and to Claude, to store your pictures, make previews and exports and create share links, to apply the daily limits, to keep the service secure and prevent abuse, and to give you support. Authorised Ridvay staff can view designs and these records to give support, investigate problems and check the quality of the service.
  • Not Used to Train AI: We never use designs created or changed through Ridvay in Claude to train, fine-tune or evaluate Ridvay's AI models — neither their content nor the records and usage-log entries we keep about them. Once a design has been created, changed or shared through Claude, it stays excluded, even if you later edit it on ridvay.com or in the Ridvay app, and so do copies made from it in Ridvay. This covers Ridvay connected to Claude as described in this section. If you instead connect Claude to Ridvay's general MCP server at https://mcp.ridvay.com/mcp, or add Ridvay to Claude with a Ridvay API key you created, Section 2 (“To Improve Our Integrations and Developer Tools”) applies, as it does to our other developer tools.

What Ridvay Sends to Claude

When Claude uses Ridvay, Ridvay sends back the information needed for your request, and Claude — and therefore Anthropic — receives it. Depending on the request, this can include:

  • Designs: the design ID (design_id), title, version number (version), time of the last change (updated_at), whether the design is shared (is_public), number of pages (page_count) and which page is shown (page_index), a link to a thumbnail image (thumbnail_url), how many designs matched a search (total), a short description of a change (summary), a link that opens the design on ridvay.com, and the full content of a design (design): its text, layout, colours, fonts, picture and logo links, variables, the web addresses of any live data sources it reads values from, and any notes saved with it, such as the request a design was originally generated from on ridvay.com. This applies to any design in your account, including designs you made outside Claude.
  • Brand Kits: the brand kit ID (brand_id), name, whether it is your default (is_default), colours (colors), heading and body fonts (heading_font, body_font), logo links (logo_urls), brand voice (voice), tagline (tagline) and business name (business_name).
  • Pictures: the link to the stored picture (src), its width and height, whether it had already been stored (deduped), and where it was placed: the design ID, version, page and element ID (element_id, which is derived from a one-way hash of the picture's contents). Links to files stored by Ridvay — pictures, brand kit logos, exported files, thumbnails and share preview images — can contain your Ridvay account ID.
  • Exports: the export job ID (job_id), its status, the file format, and the link to the finished file (url).
  • Sharing: whether the design is shared (is_public, shared) and its share links (links): the view page (view_url), a link that opens an editable copy (edit_url), an always-current image of the design (live_image_url) and a full-screen display page (screen_url).
  • Design Values: the values set on a design (values) and the names of the variables the design has (declared).
  • The Design Card: for the design card: the design ID, title, version, time of the last change, number of pages and the size of each page (pages), a link to its thumbnail that stops working after one to two hours (preview_url), whether that thumbnail shows the latest change (preview_current) and whether a newer one is on its way (preview_pending), together with which design a result is about, whether it changed the design, and the time it was sent. The card requests this through Claude, which receives it like any other result.
  • Messages: confirmations and error messages, which can include how many of your daily pictures or exports you have used and when the limit resets.

Who Receives Your Information

  • Anthropic: Everything Ridvay sends to Claude, as listed above, is received by Anthropic, which also runs the design card. Anthropic handles it under its own terms and privacy policy (anthropic.com/legal/privacy) or, if you use Claude through an organisation's business account, under Anthropic's agreement with that organisation. Your conversations with Claude are governed by those terms, not by this Privacy Policy.
  • Google: Ridvay is hosted on Google Cloud in the United States, which stores your designs, pictures, thumbnails and exported files and runs our servers (see Section 4 for the exact locations). Signing in to ridvay.com to connect Claude uses Google's Firebase Authentication. When the design card shows a preview, your device loads it from Google Cloud Storage, so Google receives your device's IP address.
  • Our Rendering Service: Ridvay's own rendering service draws exported files, thumbnails and share preview images, and measures the text of a design when it is saved; it receives the design's content to do so. It runs on Google Cloud Run and Cloud Functions in Iowa (us-central1), and the temporary data it keeps while drawing a file is deleted after one day.
  • Redis Cloud: The daily and monthly counts of the pictures you store and the exports you make, and the fingerprints that recognise repeated pictures, are kept in Redis Cloud, a database service run by Redis Ltd. on Google Cloud in Iowa (us-central1).
  • Websites You Link Pictures From: When Claude adds a picture from a link, the website that hosts the picture receives one request for it from Ridvay's servers, not from your device. If a design uses a picture straight from another website's link instead, that website can receive requests for it from our rendering service and, when you open the design on ridvay.com, from your browser.
  • Anyone With a Link: Share links are not protected by a sign-in. Anyone who has a share link can view the design, see its always-current image, show it full screen and save an editable copy of it to their own Ridvay account. A shared design's page is a public web page, so if its link is posted publicly, search engines may find and list it. The links to stored pictures, exported files and share preview images are long and hard to guess, but they are not protected by a sign-in either: anyone who has such a link can open the file. A thumbnail link works the same way, but only for one to two hours (up to seven days in an email from us); after that it stops working.
  • No Sale: We do not sell this information. Through this connector, Ridvay does not send this information to any AI provider other than returning results to Claude. If you later use Ridvay's AI features on a design on ridvay.com, Section 3 applies. The disclosures in Section 3 for legal requirements, protection of rights and business transfers also apply.

How Long We Keep It

  • Designs and Brand Kits: kept in your account until you delete them (you delete brand kits in the Brand Kit panel of the Ridvay editor on ridvay.com).
  • Version History: up to 60 versions per design; older versions are removed as new ones are saved. Version history and the values set on a design are not removed automatically when you delete the design — ask us and we will delete them. Deleting your Ridvay account deletes all of them.
  • Activity Records: activity records, usage-log entries and the daily view counts of shared designs are kept until you ask us to delete them or you delete your Ridvay account; they are not removed when you delete a single design.
  • Stored Pictures and Files: stored pictures and exported files stay available at their links until you ask us to delete them or you delete your Ridvay account; deleting a design or a brand kit does not delete them. A design's thumbnail is replaced, and the old one deleted, each time the design changes, and is deleted when you delete the design. Its share preview image is kept while the design is shared and deleted when you make the design private, delete it, or share it again. Deleting your Ridvay account deletes the pictures, exported files, thumbnails and share preview images filed under your account, and the images drawn for your shared designs' always-current image links. Files made before 9 October 2026 were not filed under your account: we delete those your designs and export records still link to, but an older exported file, or a thumbnail or share preview image that had already been replaced before that date, can stay at its link — send us the link and we will delete it. After we delete a file, Google Cloud keeps a recoverable copy for 7 more days.
  • Picture Fingerprints: 30 days after the picture is stored, then deleted automatically.
  • Export Job Records: expire 7 days after the export was requested and are then deleted automatically. The exported file itself stays available at its link, as described above.
  • Usage Counts: deleted automatically at the end of the day or month they count (UTC).
  • Sign-in Records: expire within about 20 minutes and are then deleted automatically.
  • Access Key: kept until you revoke it or delete your Ridvay account. If Claude asks Ridvay to revoke a key, we delete it then. Keys from earlier connections are kept until they are revoked too.
  • Connector Caches: the service that connects Ridvay to Claude briefly remembers whether a key is valid (for up to 60 seconds) and your list of designs for the design card (for a few seconds). These are labelled with a one-way hash of the key, never with the key itself, are held only in the service's memory and never written to disk, and are lost whenever the service restarts.
  • Technical Logs: kept for 30 days, then deleted automatically.

Your Choices and Controls

  • Approving Actions: Claude can ask for your approval before it uses Ridvay's tools, and you can turn the connector off for a conversation. These choices are made in Claude.
  • Disconnecting: You can disconnect or remove the Ridvay connector in Claude's settings at any time. To make sure the connection is closed on our side too, revoke its key at ridvay.com/user/api-keys (the keys named “Claude (OAuth)”; there can be one for each time you connected). Revoking a key stops Claude's access to your account straight away.
  • Deleting Designs: Ridvay's tools in Claude cannot delete designs. You can delete them at ridvay.com/studio/my-designs.
  • Undoing Changes: You can restore an earlier version of a design in the Ridvay editor on ridvay.com. Changes made within 10 minutes of each other are kept as one version.
  • Stopping Sharing: Ask Claude to make a design private, or change it in Ridvay. Its share links then stop working, although copies cached along the way can take a short time to expire, and search engines can take longer to drop a page they already listed. Copies that other people already saved, and files they downloaded, are not affected.
  • Choosing What You Share: Ridvay receives only what Claude sends when it uses Ridvay, such as the content it puts into your designs and the picture links it passes on. Leave out of your requests anything you do not want stored in your Ridvay account, and check a design before you share it.
  • Your Rights: You have the rights described in Section 5, including access, correction, deletion and a copy of your data. You can delete your Ridvay account yourself at ridvay.com/user/delete; that deletes your designs, version history, design values, activity records, stored pictures, exported files, thumbnails, share preview images and API keys with it (for files made before 9 October 2026, see the retention list above). To have single items or exported files deleted, email legal@ridvay.com.
  • Your Claude Data: What Claude keeps from your conversations, including the results Ridvay returns, is controlled in Claude and described in Anthropic's privacy policy or, for business accounts, in Anthropic's agreement with your organisation.