Privacy Policy

bake · Version 2.2 · Effective September 28, 2026

Hunyeon Studio processes only the information needed to provide bake.

Information we process

Optional Apple or Google sign-in details; subscription, credit and Apple transaction records; Google Play purchase tokens and their hashes, order IDs, product IDs, hashed identifiers linking purchases to a bake account, subscription/payment status, expiry times, paid amounts/currency and refund information; An image the user chooses as a profile photo; and, when you run Instagram account analysis, the public username you enter, public name, bio, website, profile-photo URL and account metrics. Account analysis processes up to 40 recent public posts’ IDs, captions, hashtags, media types, permalinks, timestamps, likes, comments, views and representative thumbnails. When you save a shopping link or use it for AI video planning, we process the public Coupang/Naver product URL, public product identity, product name, representative-image URL and page metadata. AI video planning may process the topic, revision request, selected identity/style settings, saved Instagram-analysis key message and key audience when Content is enabled, text and Coupang page metadata, public Naver Store product-detail images, and public-video audio and frames from references you select. AI voice generation processes only the selected cut caption and voice type. Auto Cut and Auto Captions process low-bitrate audio, analysis ranges, cut identifiers, duration and time mapping from the on-device video the user selects. When you allow system notifications and turn on notifications in the app, we store the Expo push token and device platform (iOS/Android). We also store account notification-inbox records, including notification kind, title, body, related-screen data, creation time and read time.

For Android AI requests, we process a randomly generated installation identifier, a hash derived from the account and installation identifiers and request contents, a Google Play Integrity security token, and verification results for the app package, version, signing certificate, app license and device integrity.

We verify and restore Google Play purchases, grant subscription access and credits without duplicate grants, verify refunds, and assess monthly-subscription conversion and settlement for affiliate-code users. We verify the authenticity of Android apps, devices and requests, and prevent tampering, replay and abuse.

Processors and purpose

Supabase provides authentication, database, private temporary audio storage and serverless functions and stores and removes user-selected profile photos privately and stores Google Play purchase-verification, ownership-linking, payment/refund records and account-linked consent, job, billing, Expo push-token/platform and notification-inbox records plus public-product snapshots kept separate from user accounts. Anthropic processes video-planning inputs, Coupang page text and metadata, selected public Naver Store product-detail screens, the saved Instagram-analysis key message and key audience when selected, and public Instagram profile/account/post text, public metrics and representative thumbnails to create AI results. OpenAI processes audio, frames and captions when you select a public Instagram video reference, and low-bitrate analysis audio and time mapping from an on-device video only when you run Auto Cut or Auto Captions. Bright Data collects the public profile, recent posts and representative thumbnails for the Instagram username you enter; public post/video information when you select a public Instagram reference; public Coupang product-page text and metadata; or public Naver Store product-page text and detail images when you select a shopping reference. ElevenLabs processes a selected cut caption and voice type only when you choose AI voice generation. 650 Industries, Inc. (Expo) processes the Expo push token, notification title/body and related-screen data for the period needed to relay a notification to Apple Push Notification service (APNs) or Firebase Cloud Messaging (FCM). Apple provides optional sign-in, App Store billing and APNs system-push delivery. Google provides optional sign-in, Google Play in-app billing, purchase/subscription verification, restoration and refund checks, Play Integrity app/device/request verification, and Firebase Cloud Messaging (FCM) delivery. Cloudflare provides proxying and security, including Android security-token/verdict processing and request-replay prevention. Push identifiers, device platform and notification content are used only for service notifications, not for advertising, user tracking or advertising profiles.

When you choose a profile photo, we upload the selected image to private Supabase storage to display it in the same account. Profile photos are displayed using access-limited links with an expiry time.

Google and Supabase process purchase tokens, order information and hashed account-linking identifiers for Google Play purchase verification. For Android security verification, Google processes a request hash, app metadata and device-attestation information; bake’s Cloudflare server processes security tokens, verdicts and replay-prevention records. Request contents are hashed before being passed to Google for this security check.

Retention and equivalent protection

Analysis reports and a minimized public-profile summary remain until account deletion or a user deletion request. Original Instagram thumbnails are downloaded only temporarily for the AI request and are not stored separately. Instagram connection data or access tokens created by an earlier app version are never used by the new public-username analysis and are deleted upon account deletion or a user deletion request. Public product identity, product name, representative-image URL, provenance and structured public-reference analysis results may be cached for up to 14 days without a link to a user account. Original representative images and product-detail screenshots are not copied or retained separately. Auto Cut and Auto Captions analysis audio is privately retained only during request processing; deletion is attempted after success, failure or cancellation, and transient failures are retried by automated cleanup. Generated transcript, cut-boundary and caption results and billing records may remain until account deletion or a deletion request for result recovery and dispute handling. Notification-inbox records remain until account deletion, including while push is turned off. The current-device Expo push token is unregistered when you turn off in-app notifications or sign out, account-linked tokens are deleted upon account deletion, and the token is disabled when the push provider reports it as invalid. Provider-side retention and deletion follow each provider’s commercial contract and data-processing policies. We review contractual/data-processing terms and public security materials to confirm protection equivalent to this Policy and applicable law, and require processing to be limited to service delivery.

Access to Google Play purchase-verification and ownership-linking records is restricted. We retain them as needed for purchase restoration, refund checks, and prevention of duplicate grants or reuse by another account; they are not all deleted immediately upon account deletion. Payment records subject to a statutory retention duty are kept for that period. Other records are deleted when their processing purpose has been fulfilled and they are no longer needed. You can request access to or deletion of these records using the contact information below.

Play Integrity tokens and verdicts are used to verify requests. A one-use record based on the token hash is stored with a five-minute validity period and removed by automated cleanup after expiry. Google-side security-data retention and deletion follow Google’s Play Integrity data-handling policy.

Uploaded profile photos are removed when you replace or delete the photo or delete the account. Transient file-deletion failures are queued for retry. Account deletion is completed after stored profile photos have been removed.

Your choices

Public Instagram account analysis and AI features are optional. Account analysis does not use Instagram login, a Meta connection or an access token. Onboarding consent for public-account, reference, AI-planning and AI-voice features does not include audio from a private on-device video. Before the first Auto Cut or Auto Captions request, a separate disclosure identifies the data sent to OpenAI, its purpose and deletion timing. Declining blocks audio extraction, upload, the AI request and credit charge, not local editing. You can prevent future transfers by not using the optional AI features. Delete consent records by deleting your bake account in Profile → Account, deleting app data, or requesting withdrawal. To withdraw consent or request suspension of processing, email hunyeon.studio@gmail.com. Turn off push in Profile → Notification Settings; this unregisters the current-device push token and cancels scheduled local notifications while notification-inbox records remain until account deletion. You may permanently delete your account in Profile → Account. See our data deletion instructions.