Privacy Policy
Last updated: November 18, 2026
Jānis Bērziņš operates the App and is responsible for the personal information described in this policy.
Categories of information collected
When you first access the catalog, the App sends a generated username to open a guest session. The service creates a separate, randomly named guest account, assigns it an ID and issues access and refresh tokens. You do not enter an email address or password. The App stores the tokens in the device's Keychain and uses them to authenticate requests.
When the App requests an episode, our service records your guest account ID, the episode and series IDs, and the request time. This event records the request, whether or not playback starts. Separately, our web server logs the request method, path and IP address. The service also uses the IP address to limit repeated requests to create guest accounts.
Your watch history as shown in the App, resume position, saved titles, saved episodes and likes are stored on your device. The App does not sync them to the service. If you email support, we receive your email address and the information you provide in your message.
Device identifier. On first launch the App creates a random device identifier and keeps it in the device's Keychain, so it stays the same after the App is reinstalled on the same device. The App attaches it to usage events and to every purchase.
Purchases. VIP subscriptions and coin packs are bought through the App Store. Apple processes the payment; the App never receives your card details. The App receives the purchase confirmation, sends the device identifier to Apple with each purchase, and keeps your coin balance and unlocked episodes on your device. For attribution and refund handling the App sends the App Store receipt, the product, its price and currency, and the attribution data described below to our purchase-attribution service.
Usage and analytics events. The App records how it is used: app opens and sessions, the screens you open, the series and episodes you start and finish, how long an episode played and how quickly it loaded, paywall views and closes, purchase attempts and their outcome, and actions such as likes, saves and settings changes. Each event carries the device identifier, a session identifier, the App version, the App Store country and a timestamp.
Advertising identifier and attribution. The App asks for permission to track through Apple's App Tracking Transparency prompt. Only if you allow it, the advertising identifier (IDFA) is collected and used to measure which ad campaigns brought people to the App. Without that permission the IDFA is not collected; the providers listed below still receive usage events with the App's own device identifier.
Crash and diagnostic data. If the App crashes or a component fails, the App sends a crash report with the device model, operating system version, App version and the technical state at the time of the crash.
Our analytics providers may derive an approximate location, at country or city level, from your IP address. The App does not access precise location.
How information is used
We use guest identifiers to maintain your session and requests to deliver the catalog and media. Episode request events from the last seven days are used to rank popular series. We use network data to operate the service and limit abuse, and support correspondence to answer your requests.
We use usage events to understand how the App is used, to improve it and to fix problems; purchase information to deliver what you bought, to process refunds and to measure revenue; device and advertising identifiers to measure the results of our advertising; and crash data to find and fix errors. The App does not show ads.
Third-party providers
The App includes software development kits from the providers below. Each receives the usage events, the device identifier, the information its software collects about the device (model, operating system, language, time zone, IP address) and, where you allowed tracking, the advertising identifier. They process this information to provide their service to us and under their own privacy policies.
- AppsFlyer — install and campaign attribution and purchase events. Privacy policy
- Meta Platforms (Facebook SDK) — usage events and one purchase event per purchase, with its price and currency, to measure and optimise our advertising on Meta's services. Automatic event logging is turned off. Privacy policy
- Google (Firebase Analytics and Firebase Crashlytics) — usage analytics and crash reports. Privacy and security in Firebase
- Yandex (AppMetrica) — usage analytics, purchase revenue and crash reports. Privacy policy
Our own purchase-attribution service receives the App Store receipt, purchase details and attribution data described above. If you allow it in the consent prompt shown after a purchase, we share your purchase details with Apple when Apple asks us for information about a refund request you made.
Hosting and media delivery infrastructure processes requests to provide the service. We do not sell your personal information. We may disclose information where required by applicable law.
Security and retention
The App communicates with the service, media hosts and the providers above over HTTPS and stores session credentials and the device identifier in Keychain. Guest accounts and episode request events have no fixed expiry. They remain in the active database until the guest account is deleted. The seven-day window applies to the popularity calculation. IP-based rate-limit records expire after their limit window, which lasts up to one hour.
Deleting a guest account removes the account and related records from the active database, including episode request events and session credentials held by the service. Existing web server logs and database backups are rotated separately. The oldest logs are replaced as newer logs fill the size limit. The service retains the five most recent database backups, made before database migrations. Previously recorded information may remain in those files until they are rotated out.
Information held by the third-party providers is kept for the periods set in their policies and their settings for our account. Deleting the guest account does not delete the device identifier or information already sent to those providers; contact us to request its deletion.
International transfers
The providers above may process information in countries other than the one where you live, where data protection laws may differ. Where applicable law requires it, such transfers rely on appropriate safeguards.
Your choices and rights
Open Profile and select Delete Guest Account to delete your guest account. Once deletion is confirmed, the App removes your local watch history, saved titles and episodes, and likes. If you choose Continue as Guest afterward, the App opens a new guest session. You can also clear your local watch history separately in Profile.
You can allow or stop tracking at any time in the iPhone Settings app, under Privacy & Security > Tracking. If you decline, the App works the same and the advertising identifier is not collected. After your first purchase, Profile shows Manage Consent, where you can change your answer about sharing purchase details with Apple for refunds.
Depending on applicable law, you may have rights to access, correct, delete or receive a copy of your personal information, restrict or object to processing, and complain to your local data protection authority. Contact us to exercise those rights or, where processing relies on consent, to withdraw it.
Children's privacy
The App is intended for people aged 13 and older. If you believe a child under 13 has used the App and provided personal information, please contact support@feitaspec.com so we can review the information and take appropriate action.
Updates and contact
We may update this policy and will post the revised version and effective date on this page. Contact Jānis Bērziņš at support@feitaspec.com.