ExpoCut
Join the Beta →
Legal

Privacy Policy

Last Updated · October 9, 2026

ExpoTechIn ("we," "us," or "our") operates the ExpoCut mobile application (the "App") and the website expocut.com (the "Website"). This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our App and Website.

1. Information We Collect

1.1 Information You Provide

  • Beta Program Enrollment: If you sign up for our TestFlight or Closed Testing program through the Website, we collect your name, email address, and platform preference (iOS, Android, or both).
  • Contact Communications: If you contact us via email at [email protected], we collect the information you provide in your correspondence.

1.2 Analytics, Install Attribution, Crash Reporting & Updates

The App uses third-party services from Google, AppsFlyer and Expo to understand usage, measure which store listings and campaigns bring new installs, improve stability, and ship App updates:

  • Analytics: Analytics is enabled by default and can be turned off at any time with a single toggle in Settings. While enabled, the App sends anonymized usage events such as screen views, export lifecycle events (start, completed, failed, cancelled), and project creation events. These events may include your device model and operating-system version. The App does not use the advertising identifier for analytics on either platform, and analytics data is not used to track you across other companies' apps or websites.
  • Install Attribution (AppsFlyer): To learn which store listing, link or campaign led to an install, the App includes the AppsFlyer measurement SDK. It is governed by the same Analytics toggle in Settings: while enabled, AppsFlyer receives an install identifier generated for the App, your device model and operating-system version, IP address, app version, install and session timestamps, the Google Play install referrer (Android) or aggregated Apple SKAdNetwork postbacks (iOS), and the lifecycle events named above, such as a completed export. Subscription purchases are reported to AppsFlyer by our subscription-management service so we can measure campaigns, never with your payment details. The App does not ask for App Tracking Transparency permission and does not read the advertising identifier (IDFA / Android advertising ID) on either platform; attribution is not used to track you across other companies' apps or websites. Turning Analytics off stops the SDK and anonymises the installation. AppsFlyer processes this data on our behalf under its privacy policy.
  • Crash Reporting: Crash reporting is enabled by default and can be turned off at any time in Settings. While enabled, the App may send crash logs, device state (such as device model, OS version, and memory state), recent feature/screen breadcrumbs, and lightweight state labels needed to diagnose the failure. These reports do not include your media files, video frames, audio, or script text.
  • Over-the-air Updates: The App periodically checks for a newer release that matches your installed version. These checks carry only the version, release channel, and platform; they do not include personal data or project content.
  • What we do NOT collect: Project IDs, individual clip or layer identifiers, video durations, clip counts, file sizes, or any content of your media. We do not track which media you import, which effects you apply, or which audio you use.

1.3 Device Permissions

The App interacts with your device in the following ways:

  • Photos & Videos: With your permission, the App accesses photos, videos, and audio in your library so you can import them into your projects, and asks for permission to save exported videos back to your library. Where supported, the App can also read location metadata embedded in your media so it is preserved in the export.
  • Camera: With your permission, the App can use your camera to record video directly within the editor.
  • Microphone & Audio Routing: With your permission, the App can use your microphone to record audio for use in your video projects, and may adjust system audio routing (for example, between the speaker, earpiece, or a Bluetooth device) so playback and recording sound correct.
  • Background Operation: While a supported long-running task is active, the operating system may allow it to finish after you move away from the App. This does not itself collect or transmit personal data.
  • Local File Storage: The App stores project files, cached media, downloaded content, and exported videos in your device's local storage and cache. Project state is kept in an on-device database; this data remains entirely on your device.
  • Secure Storage: Sensitive items — such as cloud-AI API keys and the access token for the optional AI-agent connector — are stored in your device's secure storage so they are not accessible to other apps or to plain-text backups.
  • Notifications: With your permission, the App can show push notifications as described in Section 1.14. Declining the prompt, or turning notifications off later in your device settings, disables them entirely.
  • Local Network (MCP connector): On iOS, the App requests permission to communicate on your local network when you enable the optional in-app AI Agent connector. This is required for an external MCP-compatible AI client on the same Wi-Fi network to connect to the editor. No traffic from the connector is sent to ExpoTechIn servers; it is bound to the local network and only active while the connector is enabled.
  • Bonjour / mDNS service: To trigger and support the iOS Local Network permission, the App publishes and browses a private Bonjour service of type _expocut-mcp._tcp while the connector is enabled. The service exists only on your local network and does not transmit any project data or media off the device.

1.4 Information from Third-Party Services

The App integrates with the following third-party services to provide stock media and audio content:

  • Pexels API: When you browse or search for stock photos and videos within the App, search queries and browsing activity are sent to Pexels (pexels.com). Pexels' own privacy policy governs how they handle this data. No personal information is shared with Pexels.
  • Freesound API (Android only): When the Android version offers online sound search and you use it, search queries are sent to Freesound (freesound.org). This integration is not available in the current iOS release. Freesound's own privacy policy governs its data handling.

1.5 AI Features

ExpoCut includes AI-assisted editing features such as background removal, chroma key (green-screen), auto reframe, on-device speech-to-text caption generation, on-device text-to-speech voiceover, and on-device audio cleanup / denoise. Every AI action is recorded as an undoable step and can be reviewed on-device.

  • On-device AI (default): Background removal, chroma key, auto reframe, speech-to-text caption generation, text-to-speech voiceover, and audio cleanup / denoise run locally on your device. Frames, audio, script text, and project data never leave your device for these operations.
  • Optional cloud AI (opt-in): If you configure a cloud AI endpoint and API key, the key is kept in secure device storage. Before the first chat request to that endpoint, ExpoCut names the destination and asks permission to send your prompt, recent AI chat, layer text and media names, timing, and project structure. The chat feature does not send your media files, video frames, or audio files. Consent is stored for that provider origin and is requested again if the endpoint changes. The provider may process or retain transmitted data under its own terms and privacy policy.

1.6 Text-to-Speech (Voiceover)

The App's optional text-to-speech feature lets you turn a written script into a voiceover track. Synthesis runs on your device — your script text is processed locally and the generated audio is saved with the rest of your project. Your script text is not sent to our servers or to any third party. The on-device voice model is downloaded once from our content delivery network the first time you use the feature; that download does not include your script.

1.7 In-App AI Agent Connector

ExpoCut includes an optional in-app connector that allows an external AI assistant to control the editor via a structured set of tools — such as adding layers, applying effects, capturing a canvas screenshot, exporting a project, applying a saved brand profile, importing media from a direct downloadable URL, or starting projects from bundled Templates and Reels. Important details:

  • The connector is off by default and must be explicitly enabled in the App's settings.
  • It runs entirely on your device and binds only to the local network; no traffic is sent to ExpoTechIn servers. On iOS, enabling the connector requests local-network permission so an external MCP client on the same Wi-Fi network can discover and connect to the editor.
  • While enabled, any AI client you authorize can read your project state, your bundled Template and Reel catalogs, your saved brand profiles (including any contact details and social handles you have stored), and your active project's layers — and perform editing actions on your behalf. Those actions are recorded as undoable steps in a local checkpoint log on your device.
  • If a connected AI client uses tools that download media from a URL (see Section 1.8) or call a cloud AI provider you have configured (see Section 1.5), the corresponding rules in those sections apply.
  • You are responsible for the third-party AI client you connect, including any data that client transmits to its own provider in order to operate.
  • You can revoke a connected client at any time by disabling the connector or removing the client's authorization in the App settings.

1.8 URL-Based Media Downloads

The App can import a direct URL that points to a downloadable media file, such as an MP4 or MP3. It does not provide a social-platform scraping or account-login service. When you use direct URL import:

  • The App sends a request to the host you provide to retrieve the media. That request will expose your device's network address to that host, as with any normal web request.
  • Downloaded media is stored locally on your device only.
  • We do not log, store, or transmit the URLs you enter or the content you download.
  • You are responsible for ensuring your use of downloaded content complies with the respective host's terms of service and applicable copyright laws.

1.9 Imported Third-Party Project Files

The App can open third-party project files — including motion-graphics templates, common editing-project XML formats, animated-graphic JSON files, and color-grading files. When you import such a file:

  • The file is parsed entirely on your device; we do not receive a copy.
  • If the imported file references external assets (for example, an image hosted on the web or a remote stock clip embedded in a template), the App will fetch those assets from the host the file points to.
  • Imported templates may fetch referenced stock photos or videos from Pexels. On platforms where Freesound is available, they may also fetch referenced audio. The rules in Section 1.4 apply.

1.10 Brand Profiles

The App lets you save one or more brand profiles so you can stamp consistent branding into projects with one tap. A brand profile can include a brand name, slogan, logo image, mailing address, phone number, email address, and social-media handles for platforms you choose to enter (Instagram, TikTok, YouTube, Twitter/X, Facebook, LinkedIn, Snapchat, Pinterest, Threads, and a generic website link).

  • Brand-profile fields are entirely optional. The App never asks you to fill any of them — they only contain what you choose to add.
  • All brand-profile data is stored on your device in the App's local storage. We do not transmit it to ExpoTechIn servers.
  • When you apply a brand profile to a project (manually or through the in-app AI agent connector — see Section 1.7), the matching values become layer content in your project. If you then export, share, or upload that project, those values travel with the exported video.
  • You can edit or delete any brand profile at any time from the App's settings. Deletion is immediate and local.
  • If you authorize an external AI client through the connector, that client can read and modify your brand profiles as part of its editing actions. Disable the connector to prevent this.

1.11 Bundled Content & Asset Downloads

Some bundled creative content — such as light-leak overlays, fonts, on-device AI / voice / caption models, sample media, and Template / Reel assets — is downloaded on demand from ExpoCut's content delivery network (CDN) the first time you use it, rather than being shipped inside the App. When the App fetches this content:

  • The request retrieves files from our CDN and, as with any normal web request, exposes your device's network address to the CDN.
  • No account, project content, or personal information is sent in order to download bundled content.
  • Downloaded content is cached locally on your device.

1.12 Account, Email Verification, Subscriptions & Licensing

You can install and use ExpoCut on the Free plan with no account and no sign-up. An ExpoCut account is created only when you choose to verify an email address for optional account, support, or eligible cross-platform features. An Apple subscription can be purchased and restored through the App Store without an ExpoCut-issued license code. When you create an account:

  • Email verification (one-time code): We send a one-time code to the email you enter to confirm it's yours. There are no passwords. Your email is stored on our servers as a salted, irreversible hash used as your account identifier, plus an encrypted copy used only to send the transactional notices described below. We do not store your email in plain text.
  • Device identifier: A stable, opaque device identifier may be used for account security, fraud prevention, support, and Android license restoration. On iOS, paid access is determined by the App Store subscription transaction rather than an ExpoCut device-slot or custom-code grant.
  • Offer eligibility: Apple and Google determine eligibility for their store-managed trials and promotional offers. Android-only promotions may use a minimal device marker to enforce stated one-use rules; this marker is not used to issue a custom paid entitlement on iOS.
  • Purchase & support records: When you buy, renew, change, or cancel a subscription, the app store and our subscription-management provider report identifiers such as a transaction ID, store, environment, product, and entitlement status. We use these to provide access, handle refunds and chargebacks, provide support, and prevent fraud. We never receive your card, bank, or billing details. On iOS, these App Store records are the sole authority for paid access.
  • Subscriptions & payment: Paid plans are purchased and auto-renew through the Apple App Store or Google Play, via a subscription-management service. Payment is processed entirely by the app store — we never see or store your card, bank, or billing details. We receive only your subscription status (plan, period, active/expired, refund) so we can unlock the right features.
  • Entitlement and license records: We store the minimum store subscription status needed for access, support, expiry and refund handling. Android or eligible cross-platform account features may also use a digitally signed license record. Paid iOS access remains based on the verified App Store entitlement and is restorable across supported Apple devices.
  • Promotional codes: iOS discounts or complimentary access use Apple-managed offers or Offer Codes; we receive the resulting entitlement status, not the code or payment details. If an Android-only ExpoCut license code is offered, we retain its hashed issuance/redemption record to prevent reuse and provide support.
  • Transactional email notices: Using the encrypted email above, we may email you about account and subscription events — a verification code, a new device added to your license, a subscription that won't renew, an expiry, or a refund. These are service messages, not marketing.
  • Activity log: Your account keeps a private activity history (sign-ins, plan changes, device additions/removals, license backups/restores) so you can review it in the App's Membership screen. It is tied to your account identifier and stored on our CDN.

1.13 Affiliate / Referral Program

If you choose to join the optional affiliate program from within the App, we maintain the records needed to attribute referrals and calculate commissions:

  • Your unique referral code and the share link generated for it.
  • Accounts that subscribed using your code — stored as hashed account identifiers, not names or emails — and a commission ledger (amounts, eligibility, refunds, payouts).
  • Referral attribution does not itself change an iOS price or entitlement. If an Apple-managed offer is available, Apple determines eligibility and displays the actual offer in its purchase flow. Android-only referral handling is identified separately where available.
  • Payouts are arranged manually; if you request one we will contact you at your verified email to settle it.

1.14 Push Notifications

The App can show you push notifications — a quiet heads-up when a new version is available, editing tips and new features, and occasional offers on ExpoCut plans. Notifications are delivered through Google's Firebase Cloud Messaging (FCM) on both Android and iOS (via Apple Push Notification service). They are off until you allow them in the system prompt (the in-app request names all three categories), and each category can be switched off individually in Settings › Notifications.

  • How targeting works: Instead of registering your device with us, the App subscribes itself to a small set of FCM "topics" derived on your device — platform, country and language of your device locale, device brand and model, operating-system version, installed App version, plan tier, a whole-hour timezone bucket, and the notification categories you opted into. A campaign is addressed to topics (for example "Android users on version 5.8 in Pakistan"); Google delivers it to the devices subscribed to them.
  • What we do NOT store: ExpoTechIn does not receive or store your push token, device identifier, topic list, or any record of which notifications you received. The push token exists only on your device and within Google's messaging service. We keep no per-user notification data on our servers — only the campaigns themselves (text, audience description, send time).
  • What a notification contains: A title, a short message, optionally an image, a campaign identifier, and an in-app destination (such as the app-store listing or a template). Notifications never contain your media or project content.
  • Frequency: Notifications are quiet by design (no sound), limited to a few per month, and are not sent during night hours in your timezone bucket.
  • Google: Firebase Cloud Messaging processes the push token and topic subscriptions on Google's infrastructure under Firebase's privacy terms. Tapping a notification records an anonymised "opened" event only while Analytics (Section 1.2) is enabled.

1.15 Web Page (HTML) Layers

An HTML layer shows a live web page from a secure (https) address you choose, or HTML you paste in yourself, as part of your video.

  • Loaded directly from the website: The App loads the page straight from the website you chose, as a normal web request; it is not routed through ExpoTechIn servers. Unless you turn on “Stay signed in” for that layer, the page loads without site storage.
  • Pasted HTML: HTML you paste in is stored inside your project on your device, like the rest of your project data.
  • Stay signed in (optional, off by default): You can turn this on per layer. The page then uses the App’s own web session on your device — cookies and site storage — so a site you have signed in to shows as signed in. You sign in yourself, in an in-app browser opened with “Sign in…”. An AI assistant connected through the in-app connector (Section 1.7) can switch the option on or off for a layer, but it cannot sign in for you.
  • Your session stays on your device: The App never sends the saved session to ExpoTechIn or anyone else; only the website itself receives its own cookies, as in any browser. The session is kept across App restarts until you remove it with “Sign out of all sites”, which clears the saved sign-ins and site data for every HTML layer.
  • What gets recorded: An exported video contains whatever the page shows while the layer is on screen, including anything visible while you are signed in — you decide what to record, so check the page before you export or share.

1.16 On-Device AI Image & Video Creation (AI Local Model) — Experimental

Create Image, AI Change, Create Video and Animate Photo are labelled “AI Local Model” in the App. They run generative AI models entirely on your device. These features are experimental and offered for testing.

  • Your content stays on your device: Prompts, pictures you attach or animate, and the images and videos you create are processed locally and are not sent to ExpoTechIn or any third party.
  • Model downloads: The models are downloaded once, on request, directly from Hugging Face (huggingface.co), a third-party model-hosting service. Like any download, the request reveals your IP address and standard request information to that service. If you add an optional Hugging Face access token, it is kept in secure storage on your device and sent only to huggingface.co. You may instead load model files from your device, a network drive, or a link you enter; the App then fetches the file directly from the address you chose. Downloaded models stay on your device until you delete them in Settings › AI Integration › Models.
  • Impact on your device: Running these models puts a heavy, sustained load on your device’s processor, graphics, memory and battery and uses several gigabytes of storage. Your device may become hot, slow down, drain its battery quickly, or close the App during a run.
  • Results: Generated images and videos may be inaccurate, unexpected or unsuitable. You are responsible for how you use and share them.
  • Agreement before first use: Before your first run, the App shows these points and asks you to agree. The agreement and its date are stored only on your device. You can withdraw it at any time in Settings › Privacy & Data; the App will ask again before the next run.
  • AI assistants (MCP): An AI assistant connected through the in-app connector (Section 1.7) can use these features only if you switch on “Allow use on MCP” in Settings › AI Integration › Models (off by default), you have accepted the agreement, and the model is already on your device. An assistant cannot turn the setting on, accept the agreement, or start a model download for you.
  • No responsibility for hardware impact: These features are provided “as is” for testing, and you use them at your own risk. To the extent permitted by law, ExpoTechIn and ExpoCut are not responsible for any damage to or wear of your device, overheating, battery drain, loss of data, or the content of generated results arising from their use.

1.17 AI Servers (Create Image & Create Video on another computer)

Optionally, you can run Create Image, AI Change, Create Video and Animate Photo on an AI server you add in Settings › AI Integration › Models — for example a computer on your own Wi-Fi network, or a hosted service with an OpenAI-compatible images API. The App then shows “AI Server” instead of “AI Local Model”.

  • What is sent: When a feature is set to a server, the App sends that server your prompt, any pictures you attach, change or animate, and the size and length settings, then downloads the result. Nothing is sent until you add a server and choose it for a feature.
  • Who receives it: Only the server address you entered. If that server is operated by a third party, it processes your data under its own terms and privacy policy. ExpoTechIn does not receive or store your prompts, pictures or results.
  • API keys: An API key you enter is kept in secure storage on your device and sent only to that server’s address. Removing the server deletes the key.
  • AI assistants (MCP): The “Allow use on MCP” setting (Section 1.16) also covers servers: an assistant can start a run only when it is switched on, and the run goes to the server you chose.

1.18 Clone Voice (voice recordings)

Clone Voice lets you save a voice by recording 5–15 seconds of speech in the App or by choosing an audio or video file. You then type text (up to 400 characters, optionally with expression tags such as laugh, sigh or whisper) and the App speaks it in that voice; the result is added to your project as an audio layer. Clone Voice runs an on-device voice model entirely on your device and uses the same “AI Local Model” agreement as the features in Section 1.16.

  • What is collected: The voice sample you record or choose, the name you give the saved voice, the text you type, and the audio the App generates from it.
  • Processed and stored only on your device: Your voice recordings, saved voices (“My voices”) and generated audio are processed locally and kept in the App’s storage on your device. They are never uploaded to ExpoTechIn or anyone else, and no voiceprint or other biometric data leaves your device.
  • Not used to identify anyone: A saved voice is used only to speak the text you type. We do not use it to identify or recognise you or anyone else, and we do not share, sell or upload it.
  • Model download: The voice model (about 720 MB) is downloaded once, on request, directly from Hugging Face (huggingface.co), in the same way as the models in Section 1.16. Like any download, the request reveals your IP address and standard request information to that service; it does not include your recordings or text. After that, Clone Voice works offline.
  • Permission confirmation: Before a voice is saved, you must confirm: “This is my voice, or I have the speaker’s permission to use it.” The time of that confirmation is stored with the saved voice on your device only and is not sent anywhere.
  • Other people’s voices: Do not record or upload someone else’s voice — including a child’s — unless you have the right permission (for a child, from a parent or guardian).
  • Retention and deletion: A saved voice stays on your device until you delete it. You can rename or delete each saved voice in the App (long-press the voice › Delete), and deleting the App removes all of them. Generated clips are ordinary audio files in your project and are removed when you delete them or the project.
  • Impact on your device: Generating speech uses your device’s processor, memory and battery and needs a device with enough memory. Like the features in Section 1.16, Clone Voice is experimental, provided “as is”, and the no-responsibility terms in that section also apply.
  • AI assistants (MCP): With “Allow use on MCP” switched on (Section 1.16), a connected AI assistant can see the names of your saved voices and ask the App to speak text in one of them; the audio is made on your device and added to your project. An assistant cannot record, upload or save a voice, accept the agreement, or start the model download for you.

2. How We Use Your Information

  • Beta Enrollment Data: To send you TestFlight or Closed Testing invitations and communicate about the beta program.
  • Device Permissions: Solely to provide the video editing features you request (importing media, recording, exporting).
  • Third-Party API Queries: To display stock media search results within the App.
  • AI Requests (opt-in): To execute an optional cloud AI capability you have configured and triggered, and return the result to your device.

3. Data Storage and Security

3.1 On-Device Processing

Video editing, rendering, effects processing, undo/redo history, and project management occur on your device by default. On-device AI capabilities also run locally without transmitting frames or audio. The Android version may offer an optional Community sharing action: if you deliberately use it, ExpoCut uploads the shared template recipe, rendered demo video, thumbnail, optional author metadata, and technical request data such as IP address. Community sharing is disabled in the current iOS release.

3.2 Caching

The App maintains temporary in-memory caches for API search results (for example, Pexels photo listings and, on supported non-iOS releases, Freesound audio listings) to improve performance. These caches are automatically invalidated daily and are cleared when the App is closed.

3.3 No Cloud Sync

ExpoCut does not provide automatic cloud storage or sync for projects or media. Project data remains on the device unless you deliberately use an optional sharing or external-provider action described in this policy. Community submissions, where available, use the retention period selected by the uploader and are capped at 60 days; deleting a submission may end access sooner. Minimal account, subscription, support, and eligible Android referral/license records may also be stored as described in Sections 1.12 and 1.13.

4. Data Sharing and Disclosure

We do not sell, trade, rent, or otherwise share your personal information with third parties, except in the following circumstances:

  • Legal Requirements: If required by law, regulation, or legal process.
  • Safety: To protect the rights, property, or safety of ExpoTechIn, our users, or the public.
  • Google (Analytics & Crash Reporting): Usage events and crash diagnostics as described in Section 1.2, only after you enable the corresponding in-app setting.
  • Google (Push Notifications): If you allow notifications, your device registers with Firebase Cloud Messaging and subscribes to the topics described in Section 1.14. ExpoTechIn never receives the push token or a per-device record; we only send campaign text and its topic audience to Google for delivery.
  • AppsFlyer (Install Attribution): The install-attribution data described in Section 1.2, only while the in-app Analytics setting is enabled. No media, project content or advertising identifiers are shared.
  • Expo (App Updates): Version and release-channel checks may be made for App updates. No project content is shared.
  • Third-Party APIs: Search queries are transmitted to Pexels and, on supported non-iOS releases, Freesound as described in Section 1.4.
  • Cloud AI Providers (opt-in): After the destination-specific consent described in Section 1.5, the App sends the prompt, recent chat, and relevant textual project context to your configured provider. The chat feature does not send media files, frames, or audio files.
  • Community hosting (Android, opt-in): A Community submission includes the template bundle, demo video, thumbnail, optional author metadata, and request IP address, retained for the selected period up to 60 days. This feature is disabled in the current iOS release.
  • External Hosts (URL & Template Imports, Web Page Layers): When you import media from a URL, open a template that references remote assets, or add a web page as an HTML layer, the App contacts the hosts that the URL, template or page points to (as described in Sections 1.8, 1.9 and 1.15).
  • AI Model Hosting & AI Servers (on request): Model downloads go directly to Hugging Face (Section 1.16). If you choose an AI server for a feature, your prompt and the pictures used for that feature go to the server you added (Section 1.17).
  • Clone Voice (never shared): Voice recordings, saved voices and generated audio stay on your device and are not shared with, sold to, or uploaded to ExpoTechIn or anyone else. Only the one-time model download goes to Hugging Face (Section 1.18).
  • App Stores & Subscriptions: When you purchase or restore a subscription, the Apple App Store or Google Play processes your payment and reports your subscription status to us through a subscription-management service. We share only what is needed to verify entitlements; we do not send them your media or project content.
  • AI Agent Clients (opt-in): When you authorize an external AI assistant via the in-app connector, that client receives the project data needed to perform the editing actions you request.

5. Children's Privacy

ExpoCut is not directed to children under the age of 13. We do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe your child has provided us with personal information, please contact us at [email protected] and we will delete such information. Clone Voice recordings stay on your device and are never sent to us; do not save a child’s voice without permission from a parent or guardian (Section 1.18).

6. Your Rights and Choices

6.1 Analytics and Crash Reporting

You can disable or re-enable analytics and crash reporting at any time from the App's Settings. When disabled, no usage events or crash data will be transmitted.

6.2 Push Notifications

You can turn each notification category on or off in Settings › Notifications, or disable notifications for the App completely in your device's Settings. Switching a category off unsubscribes your device from the matching topic immediately; because we hold no per-device record, there is nothing further to delete on our side.

6.3 Device Permissions

You can revoke any permission (camera, microphone, media library, notifications) at any time through your device's Settings. Revoking permissions may limit certain App features.

6.4 Data Deletion

Since all project data is stored locally on your device, you can delete it at any time by:

  • Deleting individual projects within the App.
  • Clearing the App's cache and data through your device Settings.
  • Uninstalling the App, which removes all associated local data.
  • Account data: If you created an account, initiate full deletion in Settings ▸ Membership ▸ Account ▸ Delete account. We reauthenticate the request, delete or anonymize the account data described on our Delete Your Account & Data page, and request deletion of the linked RevenueCat customer record used for subscription processing. We retain only records required by law. Email support remains available if the in-app flow cannot be completed. Account deletion does not cancel a store subscription; Apple and Google subscription and refund records remain governed by their policies.

6.5 On-Device AI Agreement, Models & AI Servers

You can withdraw the on-device AI agreement in Settings › Privacy & Data, delete downloaded models and switch “Allow use on MCP” off in Settings › AI Integration › Models, and remove an AI server (which deletes its saved API key) from the same screen.

6.6 Saved Voices (Clone Voice)

You can rename or delete any saved voice in the App (long-press the voice › Delete); deletion is immediate and local. Deleting the App removes all saved voices. Generated clips can be deleted like any other audio in your project. The on-device AI agreement and the voice model can be withdrawn or deleted as described in Section 6.5.

6.7 Beta Program

If you enrolled in our beta program, you can request removal at any time by emailing [email protected].

7. Third-Party Links and Services

The App and Website may contain links to, or integrate with, third-party services. We are not responsible for the privacy practices of these services. We encourage you to review their privacy policies:

8. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. We will notify you of any material changes by posting the updated policy on this page with a revised "Last Updated" date. Your continued use of the App or Website after changes constitutes acceptance of the updated policy.

9. Contact Us

If you have questions or concerns about this Privacy Policy, please contact us at:

  • Email: [email protected]
  • Address: ExpoTechIn, Office 12, 1561 N Central Ave, Valley Stream, NY