PromptUI is operated by Vrising Properties Ltd (trading as PromptUI), a company registered in England and Wales under company number 15713546, with its registered office at 3 Hemingway Loke, Milton Keynes, Buckinghamshire, MK4 4QG, United Kingdom. For privacy and data requests, use the contact channel listed on this site.
This Privacy Policy applies to PromptUI and PromptUI Growth Agent. PromptUI Growth Agent is the social publishing and GTM workspace inside PromptUI.
TL;DR — Plain English Summary
✅ We collect your email, prompts, generated code, and any local-business enquiry details you choose to submit.
✅ We never sell your data to third parties.
✅ Payments go through Stripe — we never see your card details.
✅ Projects are private by default. You control what you share.
✅ We use analytics, advertising, and referral technologies. In the EU/UK/Switzerland you choose via the cookie banner — reject and only essential technologies load.
✅ When you use Growth, Ads or Operate, we read and store only what each feature needs, and we post, reply or run an ad only after you approve it (see §1a).
✅ For your customers' messages, lead-form answers and ad-click data, your business decides how they are used and we process them for you.
✅ You can request deletion of your data at any time.
1. Information We Collect
Account Information
When you sign up via Clerk authentication, we collect your email address, name, and profile information provided by your authentication provider (Google, GitHub, or email).
Usage Data
Prompts and instructions you provide to the AI builder
Brand profiles, campaign briefs, and publishing settings you save in PromptUI Growth Agent
Generated code and project files created by the Service
Session metadata (timestamps, status, model used)
Credit balance and transaction history
Local-Business Enquiries
If you request a Digital Opportunity Review or enquire about our local-business services, we collect the business and contact details you submit, your sector, website, business challenge, preferred contact method, consent choices, and limited referral or campaign attribution attached to the visit.
Connected Services
If you connect GitHub or a supported social account, we process the account and installation identifiers, selected-repository or connected-account metadata, and the content needed to perform the import, export, synchronization, or publishing action you request. GitHub repository contents are accessed only for repositories you authorize.
When you connect Meta or Shopify, we process the provider account, Page, ad-account, dataset, store and granted-scope identifiers needed to show and use only the assets you authorize. Access tokens are encrypted at rest. For approved Meta campaign workflows we also retain provider object IDs, review status and readback evidence. For Shopify commerce attribution we retain compact order identifiers and financial/lifecycle facts for order, refund and cancellation receipts without storing raw webhook payloads, direct customer identity fields, customer profiles or a copy of your product catalog.
Meta ads you run
When you tap Run on an ad in PromptUI, after setting its total budget and end date, PromptUI:
uploads the ad's image to the Meta ad account you chose and creates the campaign, ad set, creative and ad there, with the campaign, ad set and ad paused and your total budget and end date on the ad set. If you ran the ad before, PromptUI uses the ones it already created;
reads them back and checks they match what you approved. If they do not, nothing is switched on. If they do, PromptUI switches them on and reads their status back again; if Meta does not confirm they match, PromptUI tries to pause them again and reads their status back. If Meta does not confirm that pause either, the ad may still be running: PromptUI tells you so and asks you to press Pause again or check Meta Ads Manager.
When you tap Pause, PromptUI asks Meta to pause them and reads their status back. PromptUI shows the ad as paused only when Meta confirms it; if Meta does not, the ad may still be running and PromptUI tells you to press Pause again or check Meta Ads Manager. PromptUI also reads each ad's status, spend, clicks and reach to show you its results; reading never switches anything on. Meta stops the ad on its own when it reaches your total budget or end date, unless you change them in Meta Ads Manager, where you can also pause it or switch it on yourself. Meta bills you directly. We keep the ad's copy, image, targeting, Page and Instagram account, the IDs of the objects PromptUI created, your total budget and end date, what Meta reported back, any error, and who tapped Run or Pause and when. Run and Pause are also recorded as product events in PostHog (see §3).
YouTube channels you connect
PromptUI uses YouTube API Services. If you choose Connect YouTube, you sign in with Google and grant PromptUI permission to upload videos (youtube.upload) and to view your channel (youtube.readonly). PromptUI uses them only to show which channel is connected (its name and ID), to upload the videos you approve with the title, description and privacy setting you chose, and to read your recent uploads and their view, like and comment counts so you can see how they perform. By using PromptUI's YouTube features you agree to be bound by the YouTube Terms of Service. Google's handling of your data is described in the Google Privacy Policy.
We store the encrypted tokens, your channel ID and name, and the IDs of videos PromptUI uploaded. Disconnecting YouTube in PromptUI deletes the stored tokens and channel details; you can also revoke access at any time in your Google Account's security settings. The Google API Services User Data Policy and Limited Use commitment in Google API Services: Limited Use apply to YouTube data too.
Google Ads accounts you connect
If you choose Connect Google Ads, you sign in with Google and grant PromptUI the Google Ads scope (https://www.googleapis.com/auth/adwords). PromptUI uses it only to:
discover the Google Ads accounts you can access and connect those whose details can be read, including each account's name, ID, currency, time zone and status. You select an account later during campaign setup;
after you review and approve a Search campaign in PromptUI, create its budget, campaign, location and language targeting, ad group, keywords and ad in that account, with the campaign, ad group, keywords and ad set to PAUSED. The budget is the total budget you set, and the campaign ends on the end date you set;
when you tap Run ad (on some screens, Switch on) in PromptUI, check again that the paused campaign still matches what you approved, including your total budget and end date. If it does not, nothing is switched on. If it does, switch its ads, keywords, ad group and campaign on (ENABLED) and read it back; if Google does not confirm it matches, PromptUI tries to pause it again and reads it back. If Google does not confirm that pause either, the campaign may still be running: PromptUI tells you so and asks you to press Pause again or check Google Ads. PromptUI switches a campaign on only when you tap this button;
when you tap Pause in PromptUI, ask Google to set the campaign, ad group and ad back to PAUSED and read their status back. PromptUI shows it as paused only when Google confirms it; if Google does not, the campaign may still be running and PromptUI tells you to press Pause again or check Google Ads. The campaign also stops on its own when it reaches your total budget or end date, unless you change them in Google Ads, where you can also pause it or switch it on yourself. Google bills you directly for its spend;
read those campaigns back (their settings, status, spend, impressions, clicks and conversions) to confirm they match what you approved and to show you their results.
We store the encrypted access and refresh tokens, the accounts successfully connected and their basic details, and the IDs and readback of campaigns PromptUI created, and who tapped Run or Pause and when. We do not use Google Ads data to train AI models, for advertising, or for any purpose other than showing and managing the campaigns you ask for. We do not sell it or share it with anyone, except the service providers listed in §3 that host and run PromptUI for you, and as required by law.
The Google API Services User Data Policy and Limited Use commitment in Google API Services: Limited Use apply to Google Ads data.
Payment Information
Payment processing is handled entirely by Stripe. We do not store credit card numbers or payment details on our servers. We receive transaction confirmations and subscription status from Stripe.
1a. Growth, Ads and Operate: what each connection uses
This section explains, platform by platform, what PromptUI reads and stores when you connect a channel for Growth (posting and results), Ads, or Operate (your customer inbox and enquiries), why, how long we keep it, and how to disconnect or ask us to delete it. Some of these features are being switched on business by business. A paragraph that begins "When you turn on" describes a feature that may not be available on your account yet; it applies from the moment that feature is turned on for your workspace. We ask each platform only for the permissions the features you use need, and the platform shows you what you are granting before you agree.
For your own PromptUI account, Vrising Properties Ltd (trading as PromptUI) is the controller of your personal data. When PromptUI handles personal data about your customers or website visitors for your business (the comments and messages in your inbox, lead-form answers and ad-click identifiers), your business is the controller and PromptUI processes that data on your behalf, as described in Customer messages and comments.
Facebook Pages and Instagram accounts
When you connect a Facebook Page and its Instagram professional account for posting, we store their IDs and the Page name or Instagram username, an encrypted access token, and the IDs of the posts PromptUI publishes. We use them to publish the posts you approve and to show their likes, comments and shares. Ads are covered in Meta ads you run.
When you turn on Results insights for Facebook and Instagram, we also read reach, views, saves, shares and impressions for the posts PromptUI published and for your Page, once a day, and store the daily totals in your workspace.
When you turn on the inbox for Facebook and Instagram, you sign in to Meta again on a separate login that asks for the inbox permissions: pages_show_list, pages_read_engagement, pages_manage_metadata, pages_read_user_content, pages_manage_engagement, pages_messaging, instagram_basic, instagram_manage_comments, instagram_manage_messages and business_management (so that Pages owned by a business account can be listed). They let us list your Pages, read Page and Instagram comments and messages, reply, hide or like comments, and subscribe your Page to our webhooks. What we collect is described in Customer messages and comments.
When you turn on Meta lead forms, you sign in to Meta on another separate login for lead ads. See Meta lead forms.
Disconnecting: remove the Page or account in Growth → Channels. Turning off the inbox (which applies to your whole workspace) unsubscribes your Page from our webhooks and deletes the inbox token. You can also remove PromptUI in Facebook (Settings → Business integrations) or in Instagram's settings. To ask us to delete the data we hold, see Connected-service access and data deletion.
LinkedIn
When you connect LinkedIn, you sign in with LinkedIn and choose a LinkedIn Page you administer. We use LinkedIn's permissions to list the Pages you administer (rw_organization_admin) and to publish the posts you approve to that Page as the organisation (w_organization_social). Depending on how your connection was made, it may also include permission to read your basic profile (r_basicprofile) and to post to your own LinkedIn profile (w_member_social); PromptUI posts to your profile only if you choose it as the destination. We store the encrypted token, your LinkedIn member ID and name, the ID and name of each Page you administer, and the IDs of the posts PromptUI published.
When you turn on LinkedIn results, we read aggregate statistics (impressions, clicks, reactions, comments and shares) for your Page and the posts PromptUI published, once a day. We do not read data about individual members for this.
When you turn on LinkedIn Page comments in the inbox, we ask for the comment permissions (r_organization_social_feed, w_organization_social_feed). We read the comments members leave on posts PromptUI published as your Page, at most every 30 minutes, and post the reply you confirm as your Page. The commenter is shown as "LinkedIn member": we do not fetch their profile, and we keep their LinkedIn ID only to link the conversation. We keep the text of a member's comment for no more than 48 hours after we last read it from LinkedIn. After that we remove the text and keep only IDs and times; your enquiry record keeps a note in place of the text.
We use LinkedIn data only to provide these features to you for your own Page. We do not sell it, use it for advertising, build profiles of LinkedIn members, or combine it with other customers' data.
Disconnecting: Growth → Channels → Disconnect deletes the stored LinkedIn credentials. Turning off the inbox (which applies to every inbox channel in your workspace) deletes the LinkedIn comments token stored in PromptUI. You can also remove PromptUI from your LinkedIn account's data privacy settings (permitted services).
YouTube comments
When you turn on YouTube comments in the inbox, Google asks you for one extra permission (https://www.googleapis.com/auth/youtube.force-ssl), added to the YouTube access you already gave. We use it to read comment threads on your channel's videos (threads with no activity for 30 days are skipped) and to post the reply you write or edit, as your channel, only after you press Send and confirm. We store the comment text, the commenter's display name and channel ID, and the time. We refresh stored YouTube comment text from YouTube or delete it within 30 days, as YouTube's developer policies require; text that is no longer on YouTube is deleted. We do not moderate, like, rate or delete anything on YouTube. Adding comments does not replace your upload permission. Turning off the inbox (which applies to every inbox channel in your workspace) deletes the YouTube comments token stored in PromptUI, unless another of your workspaces still uses it for its own inbox. When you turn off the inbox, or Google tells us the access was revoked, we also delete the YouTube comments we stored for that workspace and replace the comment text copied into its enquiries with a note. To remove Google's grant entirely, revoke PromptUI in your Google Account. The rest of YouTube channels you connect and Google API Services: Limited Use apply.
Google Business Profile
When you turn on Google Business Profile, you sign in with Google on a separate connection used only for Business Profile and grant https://www.googleapis.com/auth/business.manage. PromptUI uses it to:
list the Business Profile accounts and locations you manage, so you can pick one;
publish the posts you approve to that location (updates, offers and events, with an optional button and photo);
show your reviews and post the reply you write or edit, only after you press Send and confirm;
when Results is on for it, read your profile's views on Search and Maps, website clicks, calls, direction requests and bookings.
We do not create, verify or edit your business information. We store the encrypted token for the location you pick (tokens for locations you did not pick are deleted), the location's ID and name, the posts PromptUI published and daily performance totals. Reviews are read from Google when you open them and are not stored; when you reply, we record who replied, which review, and a fingerprint (hash) of the reply text. To draft a reply, the review text and your Brand Kit are sent to our AI providers (see AI processing). A workspace owner or admin can disconnect in Growth → Channels, and you can revoke access at myaccount.google.com/permissions. Google API Services: Limited Use applies.
Threads
When you turn on Threads, you connect your Threads profile through Meta's Threads login and grant threads_basic, threads_content_publish and threads_manage_insights. We use them to show which profile is connected (its ID and username), to publish the posts you approve (text, an image, a video or a carousel), and to read views, likes, replies, reposts and quotes for the posts PromptUI published, and your follower count, once a day. We store the encrypted token, the profile ID and username, and those daily totals. We do not read or send replies on Threads. You can disconnect in Growth → Channels or remove PromptUI in your Threads settings. When you remove PromptUI in Threads, Meta tells our uninstall callback and we delete your Threads connection and stored token. When you ask Meta to delete your data, Meta calls our deletion callback; we delete those and your Threads results, and give you a confirmation code and a status page (see data deletion).
TikTok
When you connect TikTok, you sign in with TikTok and grant user.info.basic, video.upload and video.publish. We use them to post the videos you approve to your own TikTok account through TikTok's Content Posting API. We store an encrypted token, your TikTok account ID (not your name), and the IDs and publishing status of the posts PromptUI sent.
Once TikTok's post screen is released, every TikTok post will go through it. Each time it opens, we ask TikTok for your current creator settings (your nickname and avatar, shown on the screen and not stored, the audiences you can choose, whether comments, Duet and Stitch are allowed, and the longest video you can post). You choose who can see the video and its interaction settings yourself; nothing is preselected, and nothing is sent to TikTok until you press Post and agree to TikTok's Music Usage Confirmation (and, for branded content, its Branded Content Policy). A scheduled TikTok post waits for you to open the screen and press Post. Your last audience choice may be remembered in your own browser, as a hint only.
TikTok's Terms of Service and Privacy Policy apply to your TikTok account. We use TikTok data only to post for you and show you its status; we do not sell it or use it for advertising. You can disconnect in Growth → Channels, which deletes the stored TikTok credentials, or remove PromptUI in the TikTok app's security settings (manage app permissions).
X
When you connect X, you grant tweet.read, tweet.write, media.write, users.read and offline.access. We use them to show which account is connected, to publish the posts and threads you approve (with their images), and to read engagement counts for the posts PromptUI published, within a monthly read limit for each workspace. We store the encrypted tokens, your X user ID and username, and the IDs of the posts PromptUI published.
When you turn on X mentions in the inbox, we read posts that mention your account (the author's X ID, name and username, the text and the time), using part of the same monthly read limit. Replying to mentions from PromptUI is not available yet.
When X post credits are turned on, posting to X uses PromptUI credits. The cost is shown on the post before you approve it; see the Terms of Service.
Disconnecting: Growth → Channels → Disconnect deletes the stored X credentials. You can also revoke PromptUI in your X account's connected apps settings.
Customer messages and comments (Operate inbox)
When you turn on the inbox in Customers, PromptUI collects the comments and messages your customers send your business on the channels you turn on: Facebook Page comments, Messenger, Instagram comments and Direct messages, LinkedIn Page comments, YouTube comments and X mentions. Only accounts your workspace already posts to can be added.
What we store: the sender's platform ID and display name or username (LinkedIn commenters are shown only as "LinkedIn member"), the message or comment text, its time and a link to the post; your replies and drafts, who confirmed each reply and when; and any hide or like you apply. Meta channels reach us through Meta's webhooks and a regular check; the other channels by a regular check.
Why: to show you every conversation in one place; to help you write a reply; to send the reply you confirm; to save a conversation that is an enquiry once as a customer enquiry; and to tell you when someone is waiting (by email, in your morning report and, if you turned on alerts, by Telegram, Slack, Discord or Microsoft Teams). An alert about a new message includes the sender's name and up to 200 characters of their message, so the alert channel you chose receives that snippet.
Sending: PromptUI sends a reply only after you press Send and confirm it, only to the person in that conversation, and does not start conversations or send bulk or promotional messages. Messenger and Instagram replies are sent only within 24 hours of the customer's last message.
AI drafts: if you press "Draft a reply", the conversation and your Brand Kit are sent to our AI providers to write a draft for you to edit (see AI processing).
How long we keep it:
Message content (the text of messages, comments and replies, the sender's display name, and the conversation preview) is deleted 12 months after the conversation's last activity. Shorter limits apply where a platform sets them: LinkedIn comment text, at most 48 hours after we last read it; YouTube comment text, refreshed from YouTube or deleted within 30 days. Where a platform limit applies, the commenter's display name copied into the conversation and its enquiry is cleared on the same schedule, unless you changed it yourself.
Records we keep after the content is deleted: conversation and message identifiers, times, direction, delivery status, and the record of each reply you approved (who approved it, when and where it went, and a fingerprint of its text, not the text). These stay in your workspace while it exists.
Enquiries made from conversations follow the 24-month enquiry period in §6. Where a platform limit applies, the message text copied into the enquiry is replaced with a note when the limit is reached.
Turning the inbox off (it is turned on and off for your whole workspace) stops new collection and deletes the inbox tokens, except a token another of your workspaces still uses for its own inbox. For YouTube it also deletes the stored YouTube comments (see YouTube comments). Other stored content follows the limits above; to have it deleted sooner, ask us (see data deletion).
Our role: your business is the controller of this data, and PromptUI processes it on your behalf and on your instructions to provide the inbox. Only members of your workspace can see it. We do not sell it, use it for our own marketing, or combine it with other customers' data.
If you messaged a business that uses PromptUI: please contact that business first about your data. You can also email hello@promptui.co, and we will pass your request to the business and help it respond.
Meta lead forms
When you turn on Meta lead forms and run a lead ad, PromptUI creates an instant form on your Facebook Page that asks for name, email, phone and one question you choose, and shows your privacy policy link and thank-you message. When someone submits the form, Meta notifies us (and, as a back-up, we regularly check for new leads) and we fetch that lead. We store only the answers the form asked for, with the ad and form it came from and the time, as one enquiry in your workspace; any other fields Meta returns are dropped. We email you about it and may send a Telegram alert that contains no personal data. Lead data is shown only to your workspace and is not copied elsewhere or used for anyone else. It is kept with your other enquiries for up to 24 months, or, if the enquiry has moved to an active service status (won, delivery, launched or support), for as long as that service is active, unless it is deleted sooner. Your business is the controller of lead data, and PromptUI processes it on your behalf. People who fill in your form should contact you, as your form's privacy notice says; they can also email us and we will pass the request on. Meta's Lead Ads Terms also apply to your Page.
Ad measurement on websites built with PromptUI
When a business turns on "Measure my ads" for a website it built with PromptUI, the business is the controller of the measurement data and PromptUI processes it on the business's behalf, under ad-measurement terms the business accepts when it turns the feature on. If you visit one of these websites:
You see a short banner only if you arrived from an ad or a link that tracks ad clicks. It offers Accept and Reject as equal choices, with nothing preselected. Everyone else sees no banner.
Before you choose, nothing is stored on your device. Your choice and when you made it are remembered in a cookie (pui_am) for up to 180 days, for the business that asked. You may be asked again after 180 days, if the terms change, or if the site is now run by a different business, when you arrive from an ad again.
If you accept, the ad-click identifiers in the link you arrived from (such as fbclid, gclid, gbraid or wbraid) are kept in your browser and sent with an enquiry you choose to make. They are never sent more than 90 days after the click. The copy in your browser is removed the next time you open the site after that (a browser cannot delete it while the site is closed); the copy held with an enquiry is deleted 90 days after the click.
If you reject, your choice is saved in the cookie, the click identifiers stored in this browser are deleted, and none are sent with an enquiry. Click identifiers already held with an enquiry you sent earlier are deleted if you send another enquiry with the same email or phone (even if that enquiry repeats one you just sent), 90 days after the click, when the business stops measuring its site or moves it to another business (identifiers you agreed to for the business now running the site are kept), or when you ask the business to delete them. The business's enquiry form works the same whatever you choose, and sending an enquiry is not consent to ad measurement.
In the current version, PromptUI does not send this data to Meta or Google. The banner names them because the business uses their ads; we will update this policy before any measurement data is sent to them.
Every page of the site has an "Ad measurement settings" link where you can change or withdraw your choice. You have the right to access, correct or delete your data, to object, and to complain to the Information Commissioner's Office (ICO) or your local data-protection authority. The site's "How this works" page names the business; contact it first, or email us and we will pass your request on. If the business turns measurement off for its site, the identifiers held for that site are deleted.
AI processing and AI providers
PromptUI uses AI models to build apps and to write and check posts, ads, captions, video scripts and reply drafts. To do this we send the content the task needs (your prompts, Brand Kit, drafts and, when you ask for a reply draft, the customer message, comment or review you are answering) to AI model providers, mostly through OpenRouter and, for some back-up models, directly. Depending on the task, the models can include Anthropic (Claude), OpenAI, Google (Gemini) and DeepSeek. Older direct connections to Groq and DeepInfra exist in our code and may be used if we switch them on. We choose and change models, and their back-ups, for quality and reliability. Through OpenRouter, a request may be served by the model's developer or by another hosting provider that OpenRouter routes to. These providers process the data under their own terms and privacy policies.
Text and images: Growth, Ads and Operate requests that write or check text or describe images are configured not to go to hosting providers based in China; DeepSeek models are served for them by hosts outside China. Audio is transcribed by default with a model that is not hosted in China.
Storage and training: Growth, Ads and Operate requests through OpenRouter are configured to ask the provider not to store the data or use it for training, where that type of request supports it. We are extending the same setting to every app-builder request. For data that comes from Google (for example YouTube comments), we can also ask for providers that keep no copy of the request.
Video: video clips are made with Google Veo or HeyGen. We do not send your prompts or media to video models hosted in China: ByteDance's Seedance video models, which are served only in China, are switched off for customer content and will stay off unless a UK transfer mechanism is in place.
We send only what the task needs, and we do not sell it. AI output can be wrong, which is why posts, ads and replies wait for your approval.
Google API Services: Limited Use
PromptUI's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. This covers Google Ads (adwords), YouTube (youtube.upload, youtube.readonly and, when you turn on YouTube comments, youtube.force-ssl) and, when you turn on Google Business Profile, business.manage. In particular, we:
use Google user data only to provide or improve the user-facing features described in this policy that you choose to use;
transfer it to others only as needed to provide those features (for example, sending a review or comment to an AI provider to draft the reply you asked for, or to the hosting providers in §3), to comply with applicable law, for security, or as part of a merger, acquisition or sale of assets only after obtaining your explicit prior consent;
do not use or transfer it to serve advertising, including retargeting, personalised or interest-based ads, and do not sell it;
do not allow people to read it unless you give us permission for specific data, it is needed for security (such as investigating abuse), it is needed to comply with law, or it is aggregated and anonymised for internal operations;
do not use it to develop, improve or train generalised AI or machine-learning models.
2. How We Use Your Information
Service Delivery: Your prompts and relevant project context are sent through OpenRouter or to selected AI model providers to generate and refine code and content. These providers may process that data under their own privacy policies.
Build and Verification: Generated project files and the related build output are processed in isolated E2B environments, while Trigger.dev runs background jobs needed for builder and media workflows.
GitHub Integration: If you connect GitHub, we use the access you grant to list selected repositories and perform the import, export, or synchronization action you request.
Social and Campaign Workflows: If you use PromptUI Growth Agent, we process your connected-account metadata, draft content, publishing preferences and explicit campaign approvals. Meta and Google Ads campaign objects are created in PAUSED state and are read back for verification. PromptUI switches a campaign on only when you tap Run in PromptUI, after you set its total budget and end date, and pauses it when you tap Pause.
Commerce Attribution: If you connect Shopify, verified order, refund and cancellation events are used to report commercial outcomes and match them to a PromptUI campaign only when an exact attribution marker is present.
Account Management: To manage your account, credits, and session history.
Service Improvement: Aggregated, anonymized usage data may be used to improve the Service.
Local-Business Services: To respond to service enquiries, conduct a requested review, manage follow-up, prepare proposals, and keep an auditable opportunity record.
Communication: To send service, account, purchase, and consented marketing emails through Resend. Optional local-business marketing follow-up is processed only when separately selected.
2a. Our Lawful Bases
Under UK and EU data-protection law, we rely on these lawful bases:
Contract: to provide the Service you signed up for, including building, publishing, ads, the inbox, results, billing and account management.
Legitimate interests: to keep the Service secure, prevent fraud and abuse, monitor errors and reliability, and understand how the Service is used (server-side), where those interests are not overridden by your rights.
Consent: for non-essential analytics, advertising and referral technologies on promptui.co where the cookie banner applies, for marketing emails you opt into, and for ad measurement on websites built with PromptUI (collected by the business through its banner).
Legal obligation: to keep payment, tax and other records the law requires.
Your customers' data: for inbox messages, lead-form answers and ad-measurement data, the business using PromptUI is the controller and chooses its own lawful basis; Vrising Properties Ltd (trading as PromptUI) processes that data as its processor under our Data Processing Addendum, which forms part of the Terms.
3. Data Sharing
We share your data with the following third-party service providers, each operating under their own privacy policies:
OpenRouter and AI model providers (which can include Anthropic, OpenAI, Google, hosts outside China for DeepSeek models, Groq and DeepInfra, and, for video requests, Google and HeyGen): Receive prompts, Brand Kit details, drafts and, when you ask for a reply draft, the message or review being answered, to generate AI responses (see AI processing)
GitHub: Provides authentication and, when you connect it, repository import, export, and synchronization for the repositories you authorize
Clerk: Handles authentication and user identity
Stripe: Processes payments and manages billing
Vercel: Hosts the application and may process request logs
Supabase: Hosts the database containing your projects and account data
E2B: Provides isolated build, preview, and verification environments that process generated project files, configuration, and build or runtime output
Trigger.dev: Runs background jobs and processes the job payloads, status, and logs needed for builder and media workflows
Resend: Delivers service, account, purchase, and consented marketing emails using recipient addresses and message content or delivery metadata
PostHog: Product analytics — records manual product events and, for signed-in users, account identifiers and basic profile details so we can understand reliability and product use
Sentry: Browser and server error monitoring. Consented browser monitoring can include sampled performance traces and masked session replay; prompt text, code, and media are masked or excluded from replay.
Meta: If you connect Meta, we use its APIs to read the business assets you select and support approved social publishing and the ads you create, run and pause in PromptUI (see Meta ads you run). Separately, Meta Pixel may receive advertising-measurement signals for PromptUI's own marketing, subject to your consent (see §9).
Shopify: If you connect a store, we use Shopify's Admin API and signed webhooks to maintain the connection and receive the limited commerce events described above.
Google: If you connect YouTube or Google Ads, we use those APIs only as described in YouTube channels you connect and Google Ads accounts you connect. Separately, the Google Ads tag may receive advertising-measurement signals for PromptUI's own marketing, subject to your consent (see §9).
ElevenLabs: Generates voiceovers for videos you create, from the script text
Amazon Web Services (Remotion): Renders videos from your scripts, images and media
Upstash: Hosts short-lived data used to run the Service, such as rate-limit counters and a prompt you hand over to the builder from another page
Jina AI: Reads public web pages, such as your business website, when you ask PromptUI to fetch your brand or research a page
Pexels: Receives search terms to find stock images and videos for your content
Arcjet: Protects the Service from bots and abuse, processing request details such as IP address and user agent
LinkedIn, X, TikTok and Threads (Meta): If you connect them, we use their APIs only as described in §1a. Google Business Profile, when you turn it on, is described there too.
Telegram, Slack, Discord and Microsoft Teams: If you turn on alerts on one of them, it delivers the alerts PromptUI sends you. Inbox alerts include the sender's name and up to 200 characters of their message; alerts about new lead-form enquiries contain no personal data.
Tolt: Affiliate/referral tracking — attributes a subscription to the partner who referred you, so they can be credited
Connected social, media, and research providers: Process only the account data, content, assets, or queries needed when you connect or request their optional features
We do not sell your personal information to third parties.
4. Data Storage & Security
Your data is stored in a PostgreSQL database hosted on Supabase with encryption at rest.
GitHub and supported social-account credentials are encrypted before storage, and connected access can be revoked through the relevant provider.
All communication is encrypted in transit via HTTPS/TLS.
API keys and secrets are stored as environment variables, never in source code.
We implement reasonable security measures but cannot guarantee absolute security.
5. Your Projects
Projects you create are private by default and accessible only to you.
Completed projects can be shared via public links. Only projects with a "done" status are accessible to others via share links.
You can export your projects to GitHub at any time, giving you full ownership and portability.
6. Data Retention
We retain your account and project data for as long as your account is active. Unsuccessful local-business enquiries are retained for up to 24 months so we can manage follow-up, suppression, and service records, unless you ask us to delete them sooner or law requires a different period. Customer, contract, and financial records may be retained for the period required by law or the relevant agreement. Some connected-service data has shorter periods, set out in §1a: inbox message content is deleted 12 months after a conversation's last activity (the identifiers, times and reply-approval records stay while your workspace exists), LinkedIn comment text is kept for at most 48 hours after we last read it, YouTube comment text is refreshed or deleted within 30 days (and deleted when you turn off the inbox or revoke Google's access), LinkedIn Page analytics are deleted after 12 months, ad-click identifiers are deleted 90 days after the click, and the ad-measurement choice cookie lasts 180 days. Enquiries created from inbox conversations and lead forms follow the 24-month enquiry period. If you request account deletion, we will remove your personal data within 30 days, except where retention is required by law or for legitimate business purposes (e.g., payment records).
7. International Data Transfers
PromptUI is based in the United Kingdom. Our main database is hosted in Ireland (EU) and our error monitoring in Germany (EU). Server functions for Growth, customers, Missions and video rendering run in Dublin, Ireland (EU); our other server functions, our product analytics and our video rendering (Amazon Web Services) run in the United States, and other providers listed above may process data in the United States or other countries where they operate. Growth, Ads and Operate AI requests that write or check text or describe images are configured not to go to hosting providers based in China. We do not send customer prompts or media to video models hosted in China (see AI processing). Where a transfer of personal data out of the UK needs a transfer mechanism, we use UK adequacy regulations where they apply (for example for the EEA) and otherwise look to the mechanism in the provider's own data processing terms, such as the UK International Data Transfer Addendum to the EU Standard Contractual Clauses. For some providers we have not yet confirmed which mechanism applies; our sub-processor list shows where each provider processes data and what we have confirmed. You can ask us at hello@promptui.co which terms apply to a particular provider.
8. Your Rights
Depending on your jurisdiction, you may have the right to:
Access the personal data we hold about you
Request correction of inaccurate data
Request deletion of your data
Export your data in a portable format
Object to or restrict certain processing of your data
Withdraw consent at any time, where we rely on consent
Complain to the UK Information Commissioner's Office (ico.org.uk) or your local data-protection authority
You can disconnect a Meta or Shopify provider asset from the Growth Agent connection controls. This removes or deactivates that business workspace's binding and stops its automation. PromptUI will not disconnect a Meta ad account while an ad PromptUI created on it may still be running; pause it first. After a disconnect, any ads left at Meta are managed in Meta Ads Manager. PromptUI may retain the encrypted human-owner credential so another active workspace binding can keep working and so the owner can reconnect safely; an account deletion request, provider uninstall/redaction event, or the credential's final deletion lifecycle removes it as applicable.
For Shopify, PromptUI requests removal of the webhook subscriptions it created before showing the store as disconnected.
PromptUI also honors Shopify's verified customer-data request, customer-redaction and shop-redaction webhooks. Customer requests return only matching order-level facts to the verified merchant contact; customer redaction removes matching commerce receipts and outcomes, while shop redaction removes all connector-owned commerce data, bindings and credentials for that store.
You can disconnect Google Ads from the Growth Agent connection controls. PromptUI first asks Google to revoke its access; only when Google confirms does it delete the stored Google tokens and account binding. If Google does not confirm, nothing is deleted and you are told so, so you can retry or revoke it yourself.
You can also revoke PromptUI directly from Meta, Shopify or your Google Account (for YouTube and Google Ads) (myaccount.google.com/permissions). Provider-held information remains subject to that provider's own retention rules.
You can disconnect LinkedIn, X, TikTok and, when you turn them on, Threads and Google Business Profile in Growth → Channels; this deletes the stored credentials for that connection. Turning off the inbox (for the whole workspace) stops new collection and deletes the inbox tokens, except a token another of your workspaces still uses for its own inbox; for YouTube it also deletes the stored YouTube comments. Stored inbox message content is deleted on the schedule in §1a (12 months after a conversation's last activity, sooner for LinkedIn and YouTube), while identifiers and reply-approval records stay while your workspace exists. Lead-form and inbox enquiries follow the 24-month enquiry period in §6, and results stay in your workspace (LinkedIn Page analytics for 12 months). You can ask us to delete any of it sooner.
Facebook and Instagram: remove PromptUI in Facebook (Settings → Business integrations) or Instagram's settings, then email us as below to have the data we hold deleted. This section is PromptUI's data deletion instructions for Meta.
Threads (when you turn it on): Meta can send us your request automatically. Our uninstall callback is https://www.promptui.co/api/gtm/connect/threads/uninstall and our data deletion callback is https://www.promptui.co/api/gtm/connect/threads/delete. A deletion request removes your Threads connection, stored token and Threads results, and returns a confirmation code you can check at https://www.promptui.co/threads/data-deletion.
Customers and website visitors of a business that uses PromptUI (people who messaged it, filled in its lead form or visited its website): please contact that business first. You can also email us, and we will pass your request to the business and help it respond.
To request deletion of your PromptUI account and connected-service data, email hello@promptui.co from your PromptUI account email. We will verify the request and remove personal data within 30 days, except records we must retain for legal, payment, fraud-prevention, or security purposes.
9. Cookies, Analytics & Advertising
We use these cookies and similar technologies:
Essential — required for the Service to work: authentication and session management (via Clerk), and your cookie-consent choice. These always load.
Referral attribution (Tolt) — if you arrive through an affiliate/referral link, this records which partner referred you so they can be credited when you subscribe. It follows the same regional consent choice as analytics and advertising technologies.
Analytics & advertising — non-essential:
PostHog — product analytics using manual events; signed-in events can be associated with your PromptUI account
Sentry — browser error and performance monitoring with masked session replay sampling
Meta Pixel and Google Ads tag — to measure and optimize our advertising (including conversions and remarketing audiences)
Your choice. If you visit from the EU, UK, or Switzerland, PostHog, Sentry browser monitoring, Meta, Google advertising tags, and Tolt do not load until you accept them in the cookie banner shown on your first visit. Choose Reject and only essential technologies are used. Outside these regions, these technologies load by default, but an explicit rejection is respected. You can change your choice at any time using Cookie settings.
Server-side operational events and error logs may still be processed without browser analytics cookies when needed to deliver, secure, troubleshoot, and measure the reliability of the Service. These can include account, session, build, request, and error metadata.
Websites that businesses build with PromptUI and that use "Measure my ads" set their own pui_am choice cookie, as described in Ad measurement on websites built with PromptUI. That banner is separate from the cookie banner on promptui.co.
Each provider processes data under its own privacy policy. We never sell your personal information.
10. Children's Privacy
The Service is not intended for users under 13 years of age. We do not knowingly collect personal information from children under 13.
11. Changes to This Policy
We may update this Privacy Policy from time to time. We will notify you of significant changes by updating the "Last updated" date at the top of this page.
12. Contact Us
For privacy-related questions or to exercise your data rights, email hello@promptui.co. PromptUI handles privacy requests for PromptUI and PromptUI Growth Agent.
The controller of your personal data is Vrising Properties Ltd (trading as PromptUI), a company registered in England and Wales under company number 15713546, with its registered office at 3 Hemingway Loke, Milton Keynes, Buckinghamshire, MK4 4QG, United Kingdom.