App Store
App Privacy "nutrition label" and purpose strings for an app that uses AI and Supabase
App Store Connect will not let you submit until the App Privacy questions are answered, and those answers have to match what your app really sends off the phone - including what sits in your Supabase tables and what goes to an AI provider. On top of that, every camera, photo or microphone prompt needs a clear purpose string, and personal data may only go to third-party AI after the user is told and agrees. Guideline text below is quoted from the version last updated on 2026-10-16.
What you are seeing
This page is for an iOS app built with an AI tool - often a web app wrapped with Capacitor, or an Expo app - that uses Supabase for sign-in and data and calls an AI model. One or more of these brought you here:
- App Store Connect does not let you submit the version because App Privacy is not filled in. Apple says this information "is required to submit new apps and app updates to the App Store" (App privacy details).
- You opened App Privacy, saw a long list of data types (Email Address, User ID, Other User Content, Photos or Videos...) and do not know which ones apply to your app.
- A rejection in App Store Connect cites Guideline 5.1.1 (Data Collection and Storage) or 5.1.2 (Data Use and Sharing). Read the full message on the App Review page - the wording varies, and it usually names the screen or the data the reviewer noticed.
- The reviewer flagged a permission prompt ("would like to access your camera") whose explanation is missing, generic, or does not say what the photo is used for.
- The app crashes the moment someone taps "Take photo" or "Record". Apple documents that a missing purpose string makes access to the resource fail and "might cause your app to crash" (Requesting access to protected resources).
- After uploading a build you received an email about an invalid privacy manifest or missing required reasons for APIs your app or its plugins use.
How to check it yourself
Start with what Apple asks for. The App Privacy answers cover data that leaves the device and is kept. Apple's definition:
“"Collect" refers to transmitting data off the device in a way that allows you and/or your third-party partners to access it for a period longer than what is necessary to service the transmitted request in real time.”
For a Supabase app this settles most questions: anything your app saves in a Supabase table or Storage bucket stays there, so it counts as collected. Apple also says data sent to a server and "immediately discarded after servicing the request" does not need to be disclosed, and that data processed only on the device is not collected. And because a Capacitor app is a web view, this line matters too: "Data collected via web traffic must be declared, unless you are enabling the user to navigate the open web."
For AI, Guideline 5.1.2(i) adds a separate rule on top of the label:
“You must clearly disclose where personal data will be shared with third parties, including with third-party AI, and obtain explicit permission before doing so.”
Now build an inventory of your own app. Run the SQL in your project's SQL Editor in the Supabase dashboard; every query below only reads. Keep a note open and write down each kind of data you find - you will turn that note into the App Privacy answers in the fix.
1. What your tables store
select c.table_name, c.column_name, c.data_type
from information_schema.columns c
join information_schema.tables t
on t.table_schema = c.table_schema
and t.table_name = c.table_name
and t.table_type = 'BASE TABLE'
where c.table_schema = 'public'
order by c.table_name, c.ordinal_position;On a big schema, narrow it to columns whose names suggest personal data or user content, then check the rest by hand:
select c.table_name, c.column_name, c.data_type
from information_schema.columns c
where c.table_schema = 'public'
and c.column_name ~* '(name|email|phone|address|birth|avatar|photo|image|audio|voice|location|lat|lng|message|prompt|response|content|note|health|weight)'
order by c.table_name, c.column_name;~* is a case-insensitive regular expression match. Adjust the word list to your app. Chat history, prompts and AI answers saved per user are user content, even when nobody thinks of them as "personal data".2. What sits in Storage
select
b.id as bucket,
b.public,
count(o.id) as files,
string_agg(distinct lower(substring(o.name from '[.]([A-Za-z0-9]+)$')), ', ') as file_extensions
from storage.buckets b
left join storage.objects o on o.bucket_id = b.id
group by b.id, b.public
order by b.id;jpg, heic or png uploaded by users means Photos or Videos; m4a, wav or webm means Audio Data. Only read the storage schema with SQL - Supabase says to change files through the Storage API.3. What Supabase Auth keeps about each user
-- How people sign in (email, apple, google, phone...)
select provider, count(*) as identities
from auth.identities
group by provider
order by provider;
-- Extra profile fields stored at sign-up (e.g. full_name, avatar_url)
select key, count(*) as users
from auth.users,
jsonb_object_keys(coalesce(raw_user_meta_data, '{}'::jsonb)) as key
group by key
order by users desc;
-- Whether sessions record an IP address
select count(*) filter (where ip is not null) as sessions_with_ip,
count(*) as sessions
from auth.sessions;email provider means you collect Email Address; phone means Phone Number; a full_name key means Name. Supabase's audit log docs point to the ip column of auth.sessions for a session's IP address.Apple's guidance on IP addresses: if you collect and store them, declare the data types that match how you use them (for example coarse location or diagnostics); if an IP address is only sent with a request and not kept, it does not need to be disclosed. Supabase can also write Auth audit logs into the auth.audit_log_entries table - this is optional and can be switched off under Authentication > Audit Logs (Auth audit logs). If you are unsure how to classify what Supabase stores for you, describe it in your privacy policy and ask App Review rather than leave it out.
4. Where data goes outside Supabase
Search the code for AI providers and for analytics or crash reporting tools. Run this from the project root (for an app built with an AI tool, the repository it synced to GitHub):
grep -rniE "openai|anthropic|gemini|generativelanguage|@google/genai|LOVABLE_API_KEY|elevenlabs|replicate|posthog|mixpanel|amplitude|sentry|firebase|gtag|google-analytics" \
--exclude-dir=node_modules --exclude-dir=.git --exclude=package-lock.json .- AI calls inside
supabase/functions/run on Supabase's servers, so the provider receives the data from there - it still leaves the user's phone and still needs the 5.1.2(i) disclosure and consent. - If the app uses Lovable AI, Lovable's AI docs (checked 2026-11-21) say that with the AI app context setting on, Lovable keeps the full request and response of each AI call for 90 days, and that the setting is on by default on Free and Pro plans. Check the setting in your project; while it is on, prompts and answers are kept by a third party beyond the request.
- For any other provider, read its own data-use and retention terms. Whether it keeps prompts decides how you describe it in the privacy policy; the 5.1.2(i) consent is needed either way.
- Analytics and crash tools in the web code of a Capacitor app count as data collected through web traffic (see Apple's rule quoted above).
5. Every permission prompt and its purpose string
A purpose string is the sentence iOS shows under "would like to access your camera". Each one lives in the app's Info.plist under a key such as NSCameraUsageDescription (NSCameraUsageDescription). List them on a Mac:
# Capacitor: the native project lives in ios/App
plutil -p ios/App/App/Info.plist | grep -i UsageDescription
# Plugins that can ask for device access
grep -E '"@capacitor|"@capacitor-community|"expo-(camera|image-picker|media-library|av|audio|location|contacts|calendar)' package.json
# Expo: messages are set in the app config
grep -rn -E "UsageDescription|Permission\"" app.json app.config.* 2>/dev/nullios/App/App/Info.plist as the file to inspect (iOS configuration). For each plugin that touches the camera, photos, microphone or location, there must be a matching key with a real sentence.Then read every string the way a reviewer would. Apple's checklist for a valid purpose string (Requesting access to protected resources):
- It is not blank and not just spaces.
- It is shorter than 4,000 bytes - typically one complete sentence.
- It is "accurate, meaningful, and specific" about why the app needs access.
- The same applies to every translated version of the string.
Apple also notes that libraries can reference protected APIs even if your app never calls them, that App Review still requires a purpose string for those, and that you are responsible for all access to protected resources, including access by external SDKs.
6. The privacy manifests in your build
find . -name "PrivacyInfo.xcprivacy" -not -path "*/node_modules/*" -not -path "*/Pods/*"Why it happens
The App Privacy answers are not generated from your code. Someone has to fill them in by hand in App Store Connect, and Apple says they must include the practices of "third-party partners whose code you integrate into your app" (Manage app privacy). An AI tool that builds the app never sees this form, so it never prepares the answers.
An app that uses Supabase and AI collects more than its owner usually expects:
- Sign-in creates an account record with an ID and usually an email address, and every row the user creates is tied to that ID through
user_id- so the data is linked to the user. - AI features need the user's text, photos or voice, and apps commonly save the conversation in a table to show history. Each of those is a data type on the label, and each one sent to an AI provider falls under 5.1.2(i).
- Web-to-app wrappers and generated Expo apps get permission prompts from plugins. Config plugins come with default messages, and Expo's own docs say these "will most likely need to be tailored to your specific use case" (Expo permissions).
- Guideline 5.1.1(ii) asks for more than a prompt: "Ensure your purpose strings clearly and completely describe your use of the data." A string that says "This app needs camera access" does not say what happens to the photo - for an AI app, that it is sent to a model.
How to fix it
Step 1: turn your inventory into App Privacy answers
Map each finding from the checks to Apple's data types (App privacy details). For a typical Supabase app with AI features:
- Email sign-in: Contact Info > Email Address. A
full_namefield or a name column: Contact Info > Name. Phone sign-in: Contact Info > Phone Number. - The Supabase user ID stored next to the user's rows: Identifiers > User ID ("assigned user ID ... or other user- or account-level ID").
- Chat messages, prompts, notes, AI answers saved for the user: User Content > Other User Content.
- Photos uploaded to Storage or sent to the AI: User Content > Photos or Videos. Voice recordings: User Content > Audio Data.
- Analytics or crash tools: Usage Data > Product Interaction, Diagnostics > Crash Data - only if they are actually in the app.
- For each type, choose the purpose. Data needed to run the feature is App Functionality ("authenticate the user, enable features..."). Add Analytics or other purposes only if you really use the data that way.
- Linked to the user: data stored with a
user_idis linked. Apple treats "Personal Information" and "Personal Data" under privacy laws as linked. - Tracking: answer yes only if data is linked with third-party data for targeted advertising or advertising measurement, or shared with a data broker - that is Apple's definition of tracking. Supabase storage and an AI request are not tracking by that definition.
- In App Store Connect open Apps, select the app, and click App Privacy in the sidebar (Manage app privacy). You need the Account Holder, Admin or App Manager role.
- Click Get Started, answer whether you or your third-party partners collect data, select the data types from your list, and click Save.
- For each data type, set the purposes, whether it is linked to the user, and whether it is used for tracking.
- Click Publish (top right). Updated answers appear on the product page after you publish; a changed privacy policy URL is released with your next app version.
Step 2: rewrite the purpose strings
One clear sentence per key: what the app does with the access, and - for an AI feature - that the content is sent to the AI service. Do not claim anything the app does not do. In a Capacitor app, edit ios/App/App/Info.plist (or the Info tab in Xcode). Capacitor's Camera plugin, for example, needs all three keys below (Camera plugin):
<key>NSCameraUsageDescription</key>
<string>Take a photo of a receipt so the app can read the amounts. The photo is sent to our AI service for processing.</string>
<key>NSPhotoLibraryUsageDescription</key>
<string>Choose a receipt photo from your library so the app can read the amounts with our AI service.</string>
<key>NSPhotoLibraryAddUsageDescription</key>
<string>Save the edited receipt image to your photo library.</string>
<key>NSMicrophoneUsageDescription</key>
<string>Record a voice note that is turned into text by our AI service and saved to your account.</string>In an Expo app, set the same keys under ios.infoPlist in the app config, or through the option a library's config plugin offers (Expo permissions). Expo notes that Info.plist changes cannot be delivered over the air - they ship only with a new native build.
{
"expo": {
"ios": {
"infoPlist": {
"NSCameraUsageDescription": "Take a photo of a receipt so the app can read the amounts. The photo is sent to our AI service for processing.",
"NSMicrophoneUsageDescription": "Record a voice note that is turned into text by our AI service and saved to your account."
}
}
}
}app.json. If the app supports several languages, translate the purpose strings too - Apple's checklist applies to localized strings as well.Where the app only needs one picture the user chooses, Guideline 5.1.1(iii) suggests using "the out-of-process picker or a share sheet rather than requesting full access to protected resources like Photos" (5.1.1). Asking for less is also less to explain.
Step 3: disclose the AI provider and ask before the first request
Before the first AI request, show a screen that names the provider, says exactly what is sent (text, photos, voice) and offers "Allow" and "Not now". Guideline 5.1.1(ii) also requires "an easily accessible and understandable way to withdraw consent", so put a switch in Settings. Record the choice in Supabase, so the server can enforce it and a withdrawal works on every device:
create table public.ai_consents (
user_id uuid primary key references auth.users (id) on delete cascade,
provider text not null,
granted_at timestamptz not null default now(),
withdrawn_at timestamptz
);
alter table public.ai_consents enable row level security;
create policy "Users read own AI consent"
on public.ai_consents for select to authenticated
using ((select auth.uid()) = user_id);
create policy "Users record own AI consent"
on public.ai_consents for insert to authenticated
with check ((select auth.uid()) = user_id);
create policy "Users change own AI consent"
on public.ai_consents for update to authenticated
using ((select auth.uid()) = user_id)
with check ((select auth.uid()) = user_id);
grant select, insert, update on table public.ai_consents to authenticated;
grant select on table public.ai_consents to service_role;grant lines are needed because new tables are no longer exposed to the app automatically (Supabase changelog). on delete cascade removes the row when the account is deleted.// In the app: "Allow" on the consent screen
async function grantAiConsent(userId: string): Promise<boolean> {
const { error } = await supabase.from("ai_consents").upsert({
user_id: userId,
provider: "OpenAI", // the provider you actually use
granted_at: new Date().toISOString(),
withdrawn_at: null,
});
if (error) {
showError("We could not save your choice. Please try again.");
return false;
}
return true;
}
// In the app: the switch in Settings, turned off
async function withdrawAiConsent(userId: string): Promise<boolean> {
const { error } = await supabase
.from("ai_consents")
.update({ withdrawn_at: new Date().toISOString() })
.eq("user_id", userId);
if (error) {
showError("We could not save your choice. Please try again.");
return false;
}
return true;
}showError stands for however your app shows messages. Use the signed-in user's id from supabase.auth.getUser().Then make the Edge Function that calls the AI refuse to send anything without consent. Add this near the top of the handler, after the signed-in user is known (Securing Edge Functions):
// Inside withSupabase({ auth: "user" }, async (req, ctx) => { ... })
const userId = ctx.userClaims?.id;
if (!userId) {
return Response.json({ error: "Not signed in" }, { status: 401 });
}
const { data: consent, error: consentError } = await ctx.supabaseAdmin
.from("ai_consents")
.select("withdrawn_at")
.eq("user_id", userId)
.maybeSingle();
if (consentError) {
console.error("ai: consent lookup failed", { userId, message: consentError.message });
return Response.json({ error: "Try again later" }, { status: 500 });
}
if (!consent || consent.withdrawn_at !== null) {
return Response.json({ error: "AI consent required" }, { status: 403 });
}
// ...only now send the user's content to the AI providerAI consent required back, show the consent screen again. Our guide on moving API keys into Edge Functions has the full function this check goes into.Step 4: make the privacy policy say the same thing
A privacy policy URL is required for every app, in App Store Connect and inside the app (Manage app privacy, 5.1.1(i)). Guideline 5.1.1(i) says it must clearly and explicitly:
- Identify what data the app collects, how, and all uses of it - the same list as your App Privacy answers.
- Confirm that third parties that get user data provide the same or equal protection. Name them: Supabase as the database and sign-in provider, the AI provider, any analytics tool.
- Explain data retention and deletion, and how a user can revoke consent or request deletion. Say how long AI conversations are kept and how the user withdraws AI consent (the switch from step 3).
If the app has accounts, it must also let people delete them inside the app - see our guide on Guideline 5.1.1(v) account deletion.
Step 5: add or fix the privacy manifest
The privacy manifest, PrivacyInfo.xcprivacy, records the data your app collects and the "required reasons" APIs it uses (Privacy manifest files). App Store Connect rejects uploads with invalid privacy manifests and emails you the path of the invalid file (Adding a privacy manifest).
- Capacitor: in Xcode choose File > New File, select App Privacy File under Resource, check your app target and click Create. Capacitor says plugins such as
@capacitor/preferencesand@capacitor/filesystemmay need entries, and its example declares the UserDefaults API with reasonCA92.1(Capacitor privacy manifest). - Expo: add the entries under
expo.ios.privacyManifestsin the app config (Expo privacy manifests). Expo notes that Apple does not parse every privacy file from static CocoaPods dependencies, so you may need to repeat required reasons in your app's own config. - Only use reason codes that describe what your app actually does - pick them from Apple's list, not from an example.
{
"expo": {
"ios": {
"privacyManifests": {
"NSPrivacyAccessedAPITypes": [
{
"NSPrivacyAccessedAPIType": "NSPrivacyAccessedAPICategoryUserDefaults",
"NSPrivacyAccessedAPITypeReasons": ["CA92.1"]
}
]
}
}
}
}PrivacyInfo.xcprivacy in a Capacitor project.Step 6: check the result before you submit
- In Xcode, archive the app (Product > Archive), Control-click the archive in the Organizer and choose Generate Privacy Report. Apple says the report is organized like the privacy labels and is meant to be used when you fill in App Store Connect (Describing data use). Compare it with your answers from step 1.
- Install the build through TestFlight on a device that never had the app. Trigger each permission prompt and read every message as a stranger would.
- Start the AI feature without consent: the consent screen must appear, and "Not now" must not send anything. Withdraw consent in Settings and confirm the AI feature stops.
- Open the privacy policy from inside the app and check it lists the same data, the AI provider and how to withdraw consent.
- When you resubmit, use App Review Information > Notes to say where the AI consent screen and the Settings switch are, and which AI provider receives what.
When to get help
- The app handles health, financial or children's data, where the label, the consent and the privacy policy carry legal weight beyond App Review.
- You cannot tell what an SDK, a plugin or your AI provider does with the data, and the answers depend on it.
- The AI feature is the core of the app and you need a consent flow that keeps the app usable for people who say no.
- The rejection keeps coming back under 5.1.1 or 5.1.2 and you do not know which part the reviewer still objects to.
- A launch date depends on this submission and you cannot afford another review cycle.
Sources
Primary documentation this guide was checked against. Platforms change - if something here no longer matches, the source wins.
- App Store Review Guidelines (last updated 2026-10-16)Apple Developer
- App privacy details on the App StoreApple Developer
- Manage app privacyApp Store Connect Help
- Requesting access to protected resourcesApple Developer Documentation
- NSCameraUsageDescriptionApple Developer Documentation
- Privacy manifest filesApple Developer Documentation
- Adding a privacy manifest to your app or third-party SDKApple Developer Documentation
- Describing data use in privacy manifests (privacy report)Apple Developer Documentation
- iOS configuration (Info.plist)Capacitor docs
- Camera pluginCapacitor docs
- Privacy manifestCapacitor docs
- PermissionsExpo docs
- Privacy manifestsExpo docs
- Lovable AI (AI app context, checked 2026-11-21)Lovable docs
- Auth audit logsSupabase docs
- User ManagementSupabase docs
- Row Level SecuritySupabase docs
- Securing Edge FunctionsSupabase docs
- Tables not exposed to the Data API automaticallySupabase changelog
- information_schema.columnsPostgreSQL docs
Frequently asked questions
- Do I have to declare data that is stored in Supabase, not on my own server?
- Yes. Apple's definition of "collect" is about data leaving the device and being kept where you or your partners can access it. A Supabase database is your backend, so what the app saves there counts as collected by you.
- My AI calls go through an Edge Function. Do I still need AI consent?
- Yes. Guideline 5.1.2(i) is about personal data being shared with third-party AI, not about where the code runs. The user's text or photos still reach the AI provider, so tell the user which provider receives what and get explicit permission before the first request.
- Is sending data to an AI provider "tracking"?
- Not by Apple's definition on its own. Apple defines tracking as linking data from your app with third-party data for targeted advertising or advertising measurement, or sharing it with a data broker. An AI request needs the 5.1.2(i) disclosure and consent, and the data types still go on the label, but the tracking answer depends on what the data is used for.
- Can I change the App Privacy answers without releasing a new version?
- Yes. Apple's help page says updated answers are published on your product page after you click Publish. A changed privacy policy URL is different: it is released with your next app version.
- What happens if a purpose string is missing?
- Apple documents that access to the resource fails and the app might crash, and that App Review rejects apps containing code that accesses protected resources without a purpose string. Libraries count too: if a plugin references such an API, you need the string even if your app never uses that feature.
- My app is a Lovable web app wrapped for iOS. Does any of this apply?
- Yes. Apple says data collected through web traffic in web views must be declared, so the web code's analytics and the data it saves to Supabase go on the label. The native wrapper adds the purpose strings and the privacy manifest. Our guide on taking a Lovable app to the App Store covers the wrapper itself.
Related guides
Fixed-price audit
Want someone to check the whole app, not just this?
A review of data security, production readiness and App Store readiness for apps built with AI tools. 900 USD, a ranked list of fixes within 5 business days.