1. Scope
This Privacy Policy explains how SodCode handles information when you use version 1.0.0 of the SRT Editor Android app. The app may also display the name “SubSync” within its interface. In this policy, both names refer to the same app.
This policy applies to SRT Editor, not to Android, Google Play, a document provider, sharing destination, email provider, or other third-party service you choose to use with it. For the SodCode website, see our website privacy policy.
2. Privacy at a glance
- SRT Editor does not require an account and does not provide cloud synchronization.
- Subtitle parsing, editing, validation, conversion, and export happen on your device. The app does not send subtitle contents to SodCode or an app-operated server.
- The app uses Google AdMob to show banner, interstitial, rewarded interstitial, rewarded, native advanced, and app open ads when their formats are enabled. Ad requests are configured as non-personalized, and Google’s consent tools are used where required.
- The app reads non-secret advertising switches and ad unit IDs from Firebase Realtime Database. These settings may be cached locally.
- The app stores preferences, recent-file snapshots, and temporary recovery data in app-private local storage so you can reopen work.
- A subtitle file leaves the app only when you save it to a destination or deliberately share it with another app or service.
3. Subtitle files the app accesses
SRT Editor accesses an SRT or WebVTT file only after you select it with Android’s system file picker or ask Android to open that file with SRT Editor. The app accepts UTF-8 subtitle files up to 5 MB. It does not request broad access to your device storage.
To provide its editing features, the app processes the selected file’s contents and related information, including subtitle text, cue times, cue identifiers and WebVTT settings, filename, format, source URI or path supplied by Android, file metadata, and validation or parsing notices derived from the file.
4. Information stored on your device
The app keeps up to eight recent-file snapshots in app-private storage. A snapshot can include the filename, format, cue count, last opened time, source URI or path, subtitle text, timings, identifiers, settings, metadata, warnings, and edit state. This lets a recent file be reopened without requesting the source again.
While you edit, the app may also keep one recovery snapshot containing the current subtitle document so interrupted or unsaved work can be restored. Preferences stored locally include theme, timestamp display, cue-card layout, large-change confirmation, default export format, filename suffix, text direction, and onboarding status.
These records are not uploaded by SRT Editor. Depending on your device, operating-system version, manufacturer, and Android backup settings, Android or your device provider may back up eligible app-private data under that provider’s own privacy policy. You can manage device backup in Android settings.
5. Saving and sharing files
When you choose Save New File, Android’s save interface lets you choose where the exported SRT or WebVTT file is written. The selected storage provider may be local or cloud-based. That provider handles the saved file under its own terms and privacy practices.
When you choose Share Subtitle File, SRT Editor creates a temporary copy in its cache and opens Android’s share sheet. The file is disclosed only to the destination you select. A chosen app or service may store, transmit, or otherwise process it. Temporary share files may remain in app cache until Android or the app clears the cache, you clear app data, or you uninstall the app.
6. Advertising, consent, and remote configuration
SRT Editor uses Google AdMob to request and display banner, interstitial, rewarded interstitial, rewarded, native advanced, and app open ads. Rewarded formats can provide an ad-free session after the user chooses and completes an ad. The app requests non-personalized ads. Google may process information such as your IP address, app and device information, advertising or other device identifiers where available, consent choices, ad impressions and interactions, and diagnostic or fraud-prevention data. Google handles that information under its own policies.
Subtitle text, filenames, source paths or URIs, recent-file snapshots, recovery data, and exported subtitle files are not included in SRT Editor’s AdMob requests. The app does not use a separate analytics or crash-reporting service. Existing feature-event calls use a local no-operation implementation and do not record or transmit events.
At startup and periodically while active, the app may contact Google Firebase Realtime Database to retrieve an AdMob master switch, a test-or-live mode switch, ad unit IDs, and an update timestamp. The last valid configuration is stored in app-private local storage. The configuration request does not contain subtitle content, but Firebase may receive ordinary network metadata such as an IP address and request diagnostics.
7. Information you send us
If you contact support, we receive your email address and anything you choose to include, such as your app version, Android version, issue description, or attachment. We use it to respond, investigate the request, protect our services, and meet legal obligations. Please do not send subtitle files or other sensitive content unless it is necessary for your request and you are comfortable sharing it. Our email and hosting providers may process support information on our behalf, and we may disclose it where required by applicable law.
8. Third-party services
Google AdMob and its consent platform, Google Firebase, Android’s file picker, document providers, sharing destinations, device backup services, Google Play, email providers, and website hosting providers are operated by third parties. They may process information under their own privacy policies when you use them. SRT Editor does not control a file after you save or share it with a destination outside the app. We do not sell subtitle data. You can learn more in the Google Privacy Policy and Google’s information about data from apps that use its services.
9. Retention and deletion
The app keeps up to eight recent-file snapshots; older snapshots are displaced as newer files are opened. A recovery snapshot remains until you discard it, a successful save clears it, later recovery data replaces it, you clear app data, or you uninstall the app. Preferences remain until changed, app data is cleared, or the app is uninstalled.
Clearing SRT Editor’s storage or uninstalling it removes local app-private data from the device, subject to any separate operating-system backup. Exported files and copies already sent to another app or service must be deleted from that destination. Support messages are retained only as long as reasonably necessary to handle the request, maintain business records, resolve disputes, or comply with law. Google determines retention for information it processes through AdMob, consent services, and Firebase under its own policies.
10. Your choices and rights
You choose which files to open, whether to restore or discard recovery data, where to save exports, and whether and where to share a file. You can clear the app’s cache or storage, manage Android backup, or uninstall the app through your device settings. Where Google requires an ad privacy entry point, the app displays an Ad privacy choices item in Settings so you can review or change the available consent choices. You may decline the rewarded ad offer without losing any editing, saving, or sharing feature.
Depending on where you live, you may have rights to ask about, access, correct, delete, restrict, or object to our processing of personal information. Because the app has no account and does not send subtitle content or locally stored work to us, we generally cannot access or delete information stored only on your device. Contact us about information you deliberately sent to support; we may need enough information to verify and locate it. Requests concerning information processed by Google may also need to be directed to Google.
11. Children’s privacy
SRT Editor is a general utility and is not directed to children under 13. The app does not ask users to create an account or provide personal information. If you believe a child has sent personal information to us through support, contact us so we can investigate and delete it where appropriate.
12. Security
SRT Editor minimizes data access by using Android’s system picker, app-private storage, user-initiated save and share flows, and encrypted HTTPS connections for advertising, consent, and remote configuration. It does not request broad storage access. We use reasonable administrative and technical safeguards for support messages. No storage or transmission method is completely secure, and the security of exported, backed-up, shared, advertising-related, or emailed information also depends on your device and the provider or destination you choose.
13. Changes to this policy
We may update this policy when SRT Editor, its platform integrations, or legal requirements change. The date at the top identifies the current version. Material changes may also be communicated through the app or its store listing where appropriate.
14. Contact
For privacy questions or requests about SRT Editor, email sodcode.app@gmail.com.