This Privacy Policy explains how Videoro (“we”, “us”, “our”) processes personal data when you use the Videoro app for iPhone and Android (the “App”) and the website at videoro.co (the “Website”). Where something works differently on the two platforms, we say so. Please read it together with our Terms of Use.
01Who we are
The data controller responsible for the processing described in this policy is the Videoro team. You can reach us at support@videoro.co for any question about this policy or your personal data.
This policy covers the App on iPhone and on Android (identifier com.videoro.app on both platforms), the Website and the server that supports them. It does not cover third-party services that have their own privacy policies, such as Apple, Google, the App Store and Google Play, even where they are used together with Videoro.
02Your photos and videos
The photos, videos, music and voice recordings you import, the projects and drafts you create and the templates you save for yourself (“My templates”) are stored on your device. Editing them, including with the AI tools (for example background removal, object removal, face retouch, colorize, voice and music separation and captions), is processed on your device. This media is never uploaded to us. The only exception is a community template that you choose to publish (section 6).
Faces and bodies. Tools such as Retouch, Reshape, Makeup, Body, Hair Color, Skin Tone and Hide faces detect the position of faces, facial features, body outlines, skin and hair so that an adjustment lands in the right place. Detection runs on your device only while you edit; the results are not stored, are not used to identify anyone and never leave the device. We do not create or process biometric identifiers.
Auto captions on iPhone use an open-source speech recognition model (Whisper) that runs on your iPhone. The model is not part of the App download: the first time you create captions, the App downloads the model file once (about 60–190 MB, depending on your iPhone) from our server, or from Hugging Face, where it is published, if our server cannot be reached, and checks it before use. This download sends only what any file download does, such as your IP address and basic device and app details; it does not include your audio, your Analytics ID or any account data. After that, captions are created on your iPhone, also without an internet connection. If the model cannot be used on your iPhone (for example when there is not enough free memory) or cannot be downloaded, the App uses Apple’s speech recognition framework instead. In that case iOS may send the audio of the clip to Apple for transcription, which Apple handles under its own privacy policy. The audio is never sent to us.
Describe your edit lets you pick photos and videos, write in your own words what the video should be, and get an editable project made only from your own media. It works like this:
- On your device: the App analyses the clips you picked on your device: what kind of scene it is (short labels such as “beach” or “food”), how many people or faces appear (a number only; nobody is identified), motion, sharpness and colours, loudness and tempo, and, where an on-device speech model is available, a few short sentences of what is said in the clip.
- Sent to plan the edit: only this short text summary (no photos, video frames or audio) and the description you typed, the options you chose (length, format, captions, music) and your language are sent over HTTPS to our server. Our server sends the summary and your description to our AI provider, Anthropic, PBC (Claude), which returns an edit plan: which parts of which clips to use, in what order, with which text and settings. Anthropic processes this data on our behalf to provide the feature; under its commercial terms it does not use it to train its models.
- Back on your device: the App builds the project from the plan on your device, using only your own media. Videoro does not create new images, video or music.
- Checking the edit: after the edit is built, a few small preview frames of it (at most 8 still images, about 512 pixels, with the texts and captions of the edit) may be sent over HTTPS to our server and on to Anthropic, together with the plan, so the AI can spot visible problems such as unreadable text, text over a face or a very dark shot, and fix the plan. The frames are used only for this check: they are not stored on our server, not written to our logs and, under Anthropic’s commercial terms, not used to train its models. This check is free and can be switched off by us at any time.
- Changing the edit: if you ask for a change (for example “make the captions bigger”), your change request is sent with the current plan and the same text summary, and is kept like your description (up to 7 days).
- Describe your photo: when you describe how one photo should look, the App analyses it on your device (size, brightness and colour statistics, the main colours, short scene labels, where faces, people and objects are as boxes, and a little camera data such as ISO) and sends that text summary, your description and one small preview of the photo (about 512 pixels) over HTTPS to our server and on to Anthropic, which returns a list of edits. The App applies them on your device with its own tools; the full photo never leaves your device. The preview is used only for that one request: it is not stored on our server, not written to our logs and, under Anthropic’s commercial terms, not used to train its models. The summary, your description, change requests and the returned edits are kept like other Describe requests (up to 7 days).
- Account and credits: Describe your edit needs a Videoro account because each plan uses one credit (section 4). We link each request to your account to count credits, prevent abuse (for example at most 20 plans per hour) and let the App safely retry a request.
- Retention: we keep the summary, your description and the returned plan for up to 7 days, only to troubleshoot problems and to answer a retried request without charging twice; then they are deleted automatically. We keep a technical record without that content (status, time, number of clips, duration, processing time and cost) for up to 400 days. Prompts are not written to our logs and are not shown in our admin tools.
Please don’t type sensitive personal information about yourself or others into the description.
Caption translation on iPhone. When you translate your auto captions with Translate (credits, section 4), the App sends the caption text of that video, line by line, the chosen languages and any names you asked to keep, over HTTPS to our server and on to Anthropic, PBC (Claude), which returns the translated lines. No video, audio or images are sent, and the caption timing stays on your phone. The text you send is not written to our logs or stored on our server; we keep only the translated lines for up to 7 days, so a retried request is answered without charging twice, and then delete them automatically. We keep a technical record without the text (languages, number of lines, status, time, processing time, cost and credits) for up to 400 days. Under Anthropic’s commercial terms the text is not used to train its models. If the feature is switched off, the App uses Apple’s on-device translation instead, which runs on your iPhone.
Auto captions on Android use an open-source speech recognition model (Whisper) that runs on your device. The model is not part of the App download: the first time you create captions, the App downloads the model file once (about 60–190 MB, depending on your device) from Hugging Face, where it is published, and checks it before use. This download sends Hugging Face only what any file download does, such as your IP address and basic device and app details; it does not include your audio, your Analytics ID or any account data. After that, captions are created on your device, also without an internet connection. On devices where this model cannot be used, or if it cannot be downloaded, the App uses Android’s speech recognition service instead, preferring its on-device recognizer. If no on-device recognizer is available for the language, the speech service installed on your device (usually Google’s) may process the clip’s audio under its own privacy terms. The audio is never sent to us.
Caption translation and other Google ML Kit features on Android. On Android, some tools use Google ML Kit: subject segmentation (provided through Google Play services), face detection, language identification and caption translation. ML Kit processes your images and caption text on your device; they are not sent to Google. Translation language packs (about 30 MB each) are downloaded from Google once and then work offline. As described in Google’s ML Kit data disclosure, ML Kit sends Google limited diagnostic and usage information, such as device and app details, performance metrics, error codes, the languages identified or chosen for translation and an identifier used for these metrics, which Google uses to maintain and improve ML Kit and does not share with third parties.
Permissions. The App asks only for the access a feature needs, when you first use it:
- Photos and videos: to import media and save exports. On Android 14 and later you can allow access to selected photos and videos only.
- Camera: only when you use Shoot to take a photo or record a video.
- Microphone: only to record a voiceover or the sound of a video you shoot, and, on Android devices where captions use the system speech recognition service, to create captions.
- Speech recognition (iPhone): only to create captions when the on-device Whisper model cannot be used, and to find the spoken parts of the clips you pick for Describe your edit (on your device only).
- Notifications: only if you switch on daily editing ideas. These are scheduled on your device; we do not run a push notification service.
Videos and photos you shoot in the App are saved to your photo library and edited on your device; they are not sent to us. You can change these permissions at any time in the iOS Settings app or in Android Settings → Apps → Videoro → Permissions.
We do not use your photos, videos, audio or projects to train machine-learning models.
03Usage analytics
To understand which features are used, find bugs and decide what to improve, the App sends usage events to our server. They are linked to a random identifier that the App creates on first launch (the “Analytics ID”). It is not your Apple ID or Google account and not the device advertising identifier (IDFA on iPhone, the advertising ID on Android), and a new one is created if you delete and reinstall the App. The same applies on iPhone and Android.
| Category | What we receive |
|---|---|
| Install | Analytics ID, platform (iOS or Android), distribution channel (App Store, TestFlight, Google Play or a test build), whether Pro is active and which plan |
| Device | Phone manufacturer and model, operating system version (iOS or Android), app version and build |
| Settings | Language and region setting (locale, including the country it names), the App language you chose and time zone. We do not use GPS or IP-based location |
| Usage | Screens opened, tools used, templates viewed or used, export settings, settings changed (for example notifications on or off), sign-in steps (which provider and whether it worked, never your email address), session start and length |
| Diagnostics | Whether an AI tool or export succeeded, how long it took and a short error code |
| Search | Only the number of results and the length of the query. The search text itself is not stored |
| Purchase steps | When the Pro screen is shown and whether a purchase was started, completed or cancelled |
| Ads | Whether a rewarded ad was offered, watched or unavailable (see also ad records in section 7) |
If you sign in, your account is linked to your Analytics ID. We use analytics only in aggregate or pseudonymous form to run and improve Videoro. We do not use it for advertising or share it with advertisers, and we do not use third-party analytics services.
Opting out: open Videoro → Me → Settings and switch off “Share usage analytics”. The App stops sending events and asks our server to delete the events already collected from your device and to clear the stored device details. You can switch it back on at any time.
04Purchases and subscriptions
Videoro Pro is sold through Apple’s App Store on iPhone and through Google Play on Android, and the store processes the payment.
App Store (iPhone). To confirm your subscription and keep it working, the App sends us the transaction record that Apple signs, and Apple’s servers notify us when a subscription starts, renews, is cancelled, refunded or expires. These records contain the transaction and original transaction IDs, the product, price and currency, the App Store country (storefront), purchase, renewal and expiry dates, and whether a free trial or offer was used. They are linked to your Analytics ID and, if you are signed in, to your account.
Google Play (Android). Payments are made with Google Play Billing. When you subscribe, the App asks Google Play to attach your Analytics ID to the purchase as an obfuscated account identifier, so that the purchase can be matched to your device. After a purchase or a restore, the App sends us the purchase token, order ID, product, purchase time and auto-renew status. Our server verifies the purchase token directly with Google using the Google Play Developer API, and Google’s Real-time developer notifications tell us when a subscription starts, renews, is paused, put on hold, cancelled, refunded or expires; each time, our server reads the current state from Google again. We store what Google returns: the order ID and purchase token, the product, base plan and offer, the price and currency, the country or region of your Google Play account, start, renewal, cancellation and expiry dates, the subscription state, whether a free trial was used and whether it was a test purchase. These records are linked to your Analytics ID and, if you are signed in, to your account. We use that link to give the same account Pro access on your other signed-in devices, including on the other platform; only the account most recently signed in on the purchasing device gets it.
Purchase and app checks (Android). On Android, Pro is switched on only after our server has confirmed the purchase with Google; the App keeps that confirmation for up to three days so Pro still works offline. To protect paying users and our service from altered copies of the App and fake purchases, the App also asks Google Play Integrity for a short-lived signed verdict and sends it to our server with your Analytics ID. The verdict tells us whether the App was installed from Google Play and is unmodified, and whether the device passes Google’s basic integrity checks; it contains no photos, videos, contacts or precise location. We keep only the latest result for each installation (deleted after 30 days without a new check), treat it as valid for up to 24 hours, and use it only to decide whether paid features such as Describe your edit and caption translation can run.
We never receive your name, email address, Apple ID or Google account password, or payment card details from Apple or Google. Restoring purchases works through Apple or Google Play without a Videoro account.
If we give you Pro access directly (for example for testing or after a support request), we store that grant with your account, together with its duration and an internal note.
Credits for Describe your edit. Credits are one-time (consumable) in-app purchases in packs of 300, 800 or 1800; a Videoro Pro subscription also includes monthly credits (300 a month, 400 on the yearly plan). Your credit balance is kept with your Videoro account on our server, so you need to be signed in to buy or use credits. When you buy a pack, the App sends us the transaction record that the store signs (on iPhone, Apple’s signed transaction; on Android, the Google Play purchase token); we verify it and add the credits to your account. We keep a ledger of every change to your balance: credits added by a purchase or by Pro, credits used for a plan, credits taken back after a refund and adjustments made by our team, each with its date, the product and the store transaction ID. A credit is only used when an edit plan is delivered; if a request fails, nothing is used.
05Optional account
You can use every editing feature without an account. An account lets your Pro access follow you to a new device, including from iPhone to Android and back when you use the same Google or email sign-in on both, and is required to publish community templates and to use Describe your edit, because your credits are kept in your account. If you choose to sign in, we receive:
- Sign in with Apple (iPhone only): a unique user identifier issued by Apple and, if you choose to share them, your name and email address. You can use Apple’s “Hide My Email”, in which case we only receive a private relay address. To be able to revoke access when you delete your account, we also store a token issued by Apple for this purpose.
- Google Sign-In: your Google account identifier, name and email address. On iPhone you sign in on Google’s sign-in page; on Android you choose your Google account in Android’s own account picker (Credential Manager), and Google gives the App a signed ID token that it sends to our server. We ask Google only for your basic profile and email address, and we do not receive access to your Google account or its data.
- Email sign-in: the email address you enter and, if you add it, your name. We send a one-time 6-digit code to that address; the code is stored only in hashed form and deleted within a day.
We verify the sign-in token with Apple’s or Google’s public keys and then create a session for your device. We store only a one-way hash of the session token; sessions expire after 90 days. We keep your account record (provider, identifier, name, email, created and last-seen dates) and link it to your Analytics ID so that purchases and Pro access can be matched to your account and templates can be published under it.
06Community templates
Publishing a template is optional and happens only when you choose “Share as template” and confirm. When you do, the App uploads to our server:
- the template recipe (a JSON file): clip lengths, transitions, filters, speed, effects, photo motion, and any text and emoji stickers in your edit;
- a short preview video (silent, up to 15 seconds) and a poster image made from your edit. These show your photos and videos;
- the title and category you choose and, only if you switch on “Show my name”, your first name.
Music, voiceovers and picture-in-picture layers are never included. Every template is reviewed by our moderators before it is published. Once approved, the template, preview and poster are visible to all Videoro users and to anyone with the link. If a template is rejected, the reason is shown to you in Me → Shared by me.
Reports. If you report a template, we store the reason, any details you add and your Analytics ID (so a device can report a template only once). Using a template does not upload your media; we count the use with the template ID and your Analytics ID for up to 3 days to avoid double counting.
You can delete a published template at any time in Me → Shared by me. It is removed from the feed and its files are deleted from our server. Please only publish content you have the right to share; see the community rules.
07Advertising
Videoro Pro has no ads. On the free plan, exported videos carry a small Videoro watermark. On the export screen you can choose to watch a short rewarded video ad to remove the watermark from that project and unlock 1080p and 60 fps for it. An ad is loaded and shown only when you tap to watch one, never at launch or while you edit.
Rewarded ads are provided by Google AdMob (Google LLC; Google Ireland Limited for users in the EEA, UK and Switzerland). When you choose to watch an ad, Google’s Mobile Ads SDK in the App sends Google information such as your IP address (and an approximate location derived from it), device and app details, ad interaction data (impressions, completion, taps), diagnostic information and a device advertising identifier: on iPhone, the IDFA only if you allow tracking; on Android, the Android advertising ID (unless you have deleted it) and an app set ID. Google uses this to deliver and measure the ad, prevent fraud and, where you allow it, personalise ads. See how Google uses information from apps that use its services and Google’s Privacy Policy. We only receive aggregated reports from Google. Your photos, videos and projects are never shared with Google or any advertiser.
App Tracking Transparency (iPhone). The first time you choose to watch an ad, iOS asks whether Videoro may track you. If you choose “Ask App Not to Track”, the IDFA is not shared and the ads you see are not based on your activity in other companies’ apps and websites. You can change this at any time in iOS Settings → Privacy & Security → Tracking.
Android advertising ID. Android does not ask apps to request tracking permission; the advertising ID is a device setting. You can reset it or delete it at any time in Android Settings → Google → Ads, or Settings → Privacy → Ads, depending on your device. If you delete it, Google’s SDK cannot use it and ads are not personalised based on it. The App itself never reads or stores the advertising ID; only Google’s SDK uses it, and only when you choose to watch an ad.
EEA, UK and Switzerland. On both platforms, before any ad is requested, the App uses Google’s consent tool (User Messaging Platform) to ask for your consent. You can refuse, and you can change your choice later in Videoro → Me → Settings → Ad privacy choices (shown where Google’s consent tool applies). Without consent, ads may be limited (non-personalised) or unavailable, and your export keeps the watermark.
Ad records. To count ads and the income they earn, the App sends our server a short record each time a rewarded ad is shown, completed, closed early or fails: where in the App it was offered, the ad unit, the ad network that served it, the estimated revenue Google reports for that view (amount, currency and precision) and the time. Ad records contain no advertising identifier. They are sent even if you switch analytics off, but then without your Analytics ID; if analytics is on, they include it so we can see ad income per device in aggregate.
08Server logs and security
When the App or a browser connects to our server, we record technical request logs: the time, the requested path (without query parameters), the response status, how long it took and the IP address. We use them only to keep the service secure and reliable, for example to detect abuse, enforce rate limits and investigate errors. Logs do not contain the content of your requests, sign-in tokens or your Analytics ID.
The Website does not use cookies, analytics or tracking scripts. All its fonts, images and scripts are served from our own server.
09Support requests
If you email us, we process your email address, the content of your message and anything you choose to include (such as your Analytics ID, device model or screenshots) only to answer you and resolve your request.
10Legal bases for processing
Where the EU or UK General Data Protection Regulation (GDPR) applies, we rely on the following legal bases:
| Purpose | Legal basis |
|---|---|
| Accounts, sessions | Performance of a contract with you (Art. 6(1)(b)) |
| Purchases, Pro access, credits | Performance of a contract (Art. 6(1)(b)); keeping financial records is a legal obligation (Art. 6(1)(c)) |
| Caption translation | Performance of a contract at your request (Art. 6(1)(b)); keeping the translated lines for 7 days to answer retried requests is our legitimate interest (Art. 6(1)(f)) |
| Describe your edit | Performance of a contract at your request (Art. 6(1)(b)); keeping requests for 7 days for troubleshooting and abuse prevention is our legitimate interest (Art. 6(1)(f)) |
| Community templates | Performance of a contract at your request (Art. 6(1)(b)); publication is your choice and you can withdraw it by deleting the template |
| Moderation, reports | Our legitimate interest in a safe community and compliance with App Store and Google Play rules and the law (Art. 6(1)(f), Art. 6(1)(c)) |
| Usage analytics | Our legitimate interest in understanding and improving Videoro (Art. 6(1)(f)); you can object at any time by switching analytics off |
| Rewarded ads | Your consent, collected through Google’s consent tool in the EEA, UK and Switzerland (Art. 6(1)(a)); elsewhere, performing the reward you requested (Art. 6(1)(b)) |
| Ad records | Our legitimate interest in accounting for the income that keeps the free plan free (Art. 6(1)(f)); keeping financial records is also a legal obligation (Art. 6(1)(c)) |
| Logs, security | Our legitimate interest in protecting the service and its users (Art. 6(1)(f)) |
| Support requests | Our legitimate interest in answering you (Art. 6(1)(f)) and, where relevant, our contract with you |
Where we rely on legitimate interests, we have weighed them against your rights and kept the data to the minimum needed. Where we rely on consent, you can withdraw it at any time without affecting earlier processing.
11Service providers and sharing
We share personal data only with the following providers, and only as far as needed for the purposes described above:
- Apple (iPhone): App Store payments, subscription notifications, Sign in with Apple and speech recognition for captions.
- Google: Google Sign-In; on Android also Google Play (payments with Google Play Billing, purchase verification with the Google Play Developer API and Real-time developer notifications, and Google Play Integrity to detect altered copies of the App), Google ML Kit (section 2) and, on some devices, the system speech recognition service used for captions.
- Google AdMob: rewarded ads on the free plan, with Google’s User Messaging Platform for consent (section 7).
- Anthropic, PBC (Claude): plans edits for Describe your edit. It receives the text summary of the clips you picked, your description and any change you ask for, and, to check a finished edit, a few small preview frames of it, and for Describe your photo one small preview of that photo (section 2); never your original photos, videos, audio, name, email address or Analytics ID. It processes them on our behalf as our processor.
- Hugging Face, Inc.: hosts the open-source caption model that the App downloads once on Android, and on iPhone if our server cannot be reached (section 2). It receives only the technical details of that download.
- Hetzner Online GmbH: hosting of our server and database in data centres in Germany (European Union), acting as our processor.
Apple, Google and Hugging Face act as independent controllers for the data they process under their own terms. We may also disclose information if required by law or by a valid request from a public authority, to report illegal content, to protect the rights, safety and property of our users or of us, or as part of a merger, acquisition or sale of assets, in which case this policy will continue to apply to your data.
We do not sell personal data, and we do not share it for cross-context behavioural advertising ourselves. The only exception is the advertising identifier that Google’s ad SDK may receive when you choose to watch an ad (section 7): on iPhone only if you allow tracking, which you control in iOS Settings → Privacy & Security → Tracking; on Android unless you delete the advertising ID in Android Settings.
12International transfers
Our server and database are hosted in Germany, in the European Union. If you use Videoro from outside the EU, your data is transferred to the EU to be processed. Apple and Google may process data in the United States and other countries; they rely on the EU–U.S. Data Privacy Framework and the European Commission’s Standard Contractual Clauses. Anthropic processes Describe your edit requests in the United States and other countries; we rely on the Standard Contractual Clauses in its data processing terms. Hugging Face may serve the caption model download from servers in the United States and other countries. Our team may access the data from countries outside the European Economic Area that may not have an adequacy decision. Where such a transfer takes place, we protect it with appropriate safeguards, such as the Standard Contractual Clauses. You can ask us for more information about these safeguards.
13How long we keep data
| Data | Retention |
|---|---|
| Analytics events | Deleted automatically after 90 days, or immediately when you switch analytics off |
| Device details | Kept while you use the App; deleted or anonymised no later than 13 months after your device last contacted us, or cleared when you switch analytics off |
| Account | Until you delete your account |
| Sign-in sessions | 90 days, then deleted automatically |
| Published templates | Until you delete them or your account, or until we remove them under our Terms |
| Unfinished uploads | Deleted after 24 hours |
| Reports | While the reported template exists |
| Template use counts | 3 days |
| Purchase records | App Store and Google Play purchase and subscription records: as long as required by tax and accounting law (up to 7 years). If you delete your data, or your device has not contacted us for 13 months, they are kept without the link to you |
| Credit ledger | As long as your account exists; purchases also as long as tax and accounting law requires (up to 7 years). When you delete your account, the balance is deleted and the ledger is kept without the link to you |
| Describe your edit requests | The clip summary, your description, your change requests and the returned plans: 7 days, then deleted automatically. Preview frames sent to check an edit: not stored. The technical record without that content: 400 days |
| Store notifications | The raw messages Apple and Google send us about subscription changes: 25 months, then deleted automatically (test messages after about 13 months) |
| Ad records | 25 months, then deleted automatically. The link to your Analytics ID is removed when you switch analytics off, delete your data, or your device has not contacted us for 13 months |
| Email sign-in codes | Stored only as a hash and deleted automatically about a day after they expire |
| Server logs | Up to 30 days, then overwritten |
| Moderation records | Records of moderation and account actions (for example a Pro grant or a block): 3 years |
| Support emails | Up to 2 years after your request is resolved |
| Backups | Database backups are rotated daily and only the most recent 14 are kept, so deleted data disappears from them within about 14 days |
14Security
All connections between the App, the Website and our server are encrypted with HTTPS. App Store purchase records are verified with Apple’s signatures, Google Play purchases directly with Google, and sign-in tokens with Apple’s and Google’s keys. We store session tokens and admin sign-in codes only as one-way hashes. Access to the server and the admin panel is limited to authorised team members, requires a one-time code sent by email, and every administrative action is logged. No method of transmission or storage is completely secure, but we work to protect your data and will notify you and the authorities of a personal data breach where the law requires it.
15Your rights
Depending on where you live, including under the GDPR in the EEA and UK, the California Consumer Privacy Act (CCPA/CPRA) and the Law of the Republic of Azerbaijan “On Personal Data”, you have the right to:
- access the personal data we hold about you and receive a copy;
- correct inaccurate data;
- delete your data (“right to be forgotten”);
- restrict processing in certain cases;
- object to processing based on legitimate interests, including analytics;
- data portability: receive the data you provided in a structured, machine-readable format;
- withdraw consent at any time, where processing is based on consent;
- opt out of the sale or sharing of personal data (California). We do not sell or share personal data ourselves; to stop the advertising identifier reaching Google, deny tracking in iOS Settings → Privacy & Security → Tracking, or delete the advertising ID in Android Settings (section 7);
- not be discriminated against for exercising these rights;
- lodge a complaint with a supervisory authority, in particular in the country where you live or work, or where you believe your rights were infringed.
Many of these you can exercise yourself in the App: switch off analytics in Me → Settings, delete templates in Me → Shared by me, and delete your account (section 16). For anything else, email support@videoro.co and include your Analytics ID (Me → Settings → Analytics ID) so we can find your data. We may need to verify your request and will respond within one month (45 days for California requests); we may extend this where the law allows and will tell you if we do. You may use an authorised agent where the law allows.
16Deleting your account
If you are signed in, open Videoro → Me and, in the account section, tap Delete account. This works the same on iPhone and Android and permanently deletes from our server:
- your account record (identifier, name and email address) and all your sign-in sessions;
- every template you published, including the preview videos, posters and their reports;
- any Pro access we granted to the account;
- your credit balance (unused credits are lost) and the content of any Describe your edit requests still stored (clip summary, description and plan). Credit ledger entries and the technical records of those requests are kept only without the link to you, for the periods in section 13.
For Sign in with Apple, we also revoke Videoro’s access to your Apple ID. For Google Sign-In on Android, the App also clears its saved sign-in on your device; you can remove Videoro from your Google Account at any time under Security → Your connections to third-party apps & services. If your session has expired, the App asks you to sign in once more to confirm it is you. If you are offline, the deletion is completed the next time the App can reach our server.
Deleting the account does not cancel your subscription. Cancel it in iOS Settings → your name → Subscriptions, or on Android in the Google Play Store app → your profile → Payments & subscriptions → Subscriptions.
Without the App. If you no longer have the App installed, email support@videoro.co from the email address linked to your Videoro account and ask us to delete it. We delete the same data as above, usually within a few days and no later than one month after we have confirmed the request comes from you.
Usage analytics are not linked to you after the account is deleted. To delete them too, switch off “Share usage analytics” in Me → Settings, or email us and we will delete all data linked to your Analytics ID.
17Children
Videoro is not directed to children under 13, and we do not knowingly collect personal data from them. In the EEA and UK, users under 16 (or the lower age set by their country) may only create an account or publish templates with the consent of a parent or guardian. If you believe a child has given us personal data without the required consent, contact us and we will delete it.
18Changes to this policy
We may update this policy from time to time. We will change the effective date at the top of this page and, if a change is significant, tell you in the App before it takes effect. Previous versions are available on request.
19Contact
For questions about this policy or to exercise your rights, email support@videoro.co.
Questions about your data? We usually reply within one or two working days.
Email us