Privacy policy

Lokireddy IT Services (Kalyani Bhimavarapu), Vijayawada, Andhra Pradesh, India, the developer of the iWatchly apps and of iwatchly.com. Questions about this policy and requests about your data go to lokireddy.apps@gmail.com.

One sign-in works across the iWatchly apps and iwatchly.com. It is provided by Firebase Authentication, a Google service. Signing in with Apple or Google gives us the email address on that account (or, if you asked Apple to hide it, a private relay address that forwards to you), your name if the provider supplies it, and a user id. We do not receive your Apple or Google password. The same account, and therefore the same data, is visible in each app that supports it and on iwatchly.com. Deleting the account deletes the sign-in itself together with your data in every iWatchly app that uses it, as described in each app's section below.

iWatch PDF stores documents for you so they can be read on iPhone, Apple Watch and iwatchly.com. This section describes what that involves.

What is collected

• Your documents. PDFs you import are uploaded to our servers on Google Cloud (Cloud Storage and Firestore, United States region). From each document we derive page images and extracted text so it can be displayed on the Watch and searched. Documents added to a folder, tagged, starred or set for review carry that metadata too.
• Your account. The email address on your Apple or Google account (or Apple's private relay address if you chose to hide your email), your display name if the provider supplies one, and a user id issued by Firebase Authentication. Accounts created before 2026 may have an email address and password instead.
• Sharing. When you share a document, the recipient's email address, the document and an optional note are stored so the share can be delivered and revoked. The recipient sees your account email as the sender.
• AI features. When you use Ask this PDF or Test Yourself, the relevant text of that document, and your question, are sent to a language-model provider to produce the answer or the questions. Providers used are Google (Gemini) and Anthropic (Claude). Answers, conversations, question banks and your quiz attempts are stored with the document. The number of tokens used is metered against your monthly allowance. Nothing is sent for a document until you ask for it.
• Devices and notifications. A push-notification token for each device where you allowed notifications, used for review reminders and the one-time note that a quiz is ready.
• Subscription state. Whether your account has Pro, provided by RevenueCat from the App Store receipt. We never receive card or bank details; Apple handles payment.
• Usage and diagnostics. Firebase Analytics events about which features are used (for example, which import method) and Firebase Crashlytics crash reports, used to find and fix problems. The app does not record your screen or your sessions. If you allow tracking when iOS asks, Apple's AdServices attribution token is sent to RevenueCat to measure which App Store campaign an install came from. If you decline, it is not.
• Advertising measurement. The app includes Meta's Facebook SDK, which starts when the app opens and sends app events, such as installs and app opens, to Meta so we can measure our advertising on Meta's platforms. Your advertising identifier is included only if you allow tracking when iOS asks. The app does not use Facebook Login or Facebook sharing.
• Support chat. Messages you send through in-app chat are handled by Crisp and identified by your account.
• Email. Transactional email (a share notification, a sign-in code) is sent through SendGrid.

How it is used

To show your documents on your devices and on the web, to run the features you invoke, to keep the service working and to answer support requests. Analytics and crash data are used to improve the app, not to build advertising profiles.

Retention and deletion

Documents stay until you delete them. Deleting a document in the app removes it, its page images, text, quizzes and conversations from our servers, and from any device the next time it syncs. The iWatch PDF app does not have its own delete button yet. To delete your account and every document in it, use Account, then Delete account in iWatch Videos 3.0 or later, which deletes your whole iWatchly account, or email lokireddy.apps@gmail.com from the address on the account. Deleting the app from a device does not delete the synced copy on our servers.

AI Watch Translator (formerly Translate Now) turns speech and text into another language on iPhone and Apple Watch. Most of what it holds stays on your device; this section says exactly what leaves it.

What leaves your device

• The text you translate. It is sent over HTTPS to our own service on Google Cloud Run (project translate-it-now, United States region), which translates it with Google Cloud Translation and returns the result. Our request log records only how many items were sent, their length and the language pair, never the text, and that holds when a translation fails too.
• A usage log, without you in it. The text you translate is kept for up to 90 days, with no link to you, so we can see which phrases and language pairs people need and improve the app. Before it is stored, email addresses, web addresses, phone numbers and any run of two or more digits are removed and it is cut to 200 characters. From version 2.1 the app does not log anything longer than that at all. Alongside the phrase we keep the language pair, which part of the app was used (voice, conversation, text, camera, live, phrase book, watch or widget), whether it was the iPhone or the Watch, the app version, the original length and the hour of the request. Nothing in it identifies you: no account, no device identifier, no IP address and no time finer than the hour. The only view we read groups it into phrases translated at least three times on the same day. Each day's entries are deleted automatically after 90 days.
• Speech. When you tap the microphone, speech is turned into text by Apple's speech recognition, which may process the audio on Apple's servers under Apple's own terms. The resulting text then follows the path above. The app asks for microphone and speech permission the first time you use the microphone, not at launch.
• Speaking on Apple Watch (from version 2.1). With an internet connection, your recording is transcribed by Google Cloud Speech-to-Text on our behalf. We do not store the audio, and Google does not keep it or use it for training. The text is then handled like typed text, including the usage log. Without a connection, the recording is processed on your paired iPhone and does not leave your devices.
• Say it differently (from version 2.1). When you ask for other ways to phrase a translation, the sentence is rephrased either on your iPhone, on models with Apple Intelligence, or by an AI model (Gemini) running in our own Google Cloud project in the United States, which returns up to three alternatives. We do not store the request and it is never written to the usage log; our server records only the text lengths and the language pair. Google does not store these requests beyond serving them and does not use them to train its models. Nothing about you is sent with it.
• Usage events. Firebase Analytics records which features are used: the screen or action, the language pair, counts grouped into ranges rather than exact numbers, and whether the account is premium and signed in. It never receives what you translated or typed, your email address or your user id.
• Advertising measurement, only if you allow it. After onboarding, the app shows Apple's App Tracking Transparency prompt. If you allow tracking, your device's advertising identifier is shared with RevenueCat, our subscription service (and, in versions before 2.1, with Firebase Analytics), for one purpose: to measure which advertising campaign led to an install. Apple's AdServices attribution token, which needs no permission and names a campaign rather than you, is sent to RevenueCat for the same purpose. If you decline, no advertising identifier is collected and the app works exactly the same. You can change your answer at any time in iOS Settings › Privacy & Security › Tracking. The app shows no ads and contains no SDK that serves them, and we do not sell data.
• Notifications. If you allow them, a push token through Firebase Cloud Messaging. Permission is asked after you have used the app a few times, never at first launch.

What stays on the device

Your translation history and your phrase books are stored on the iPhone and on the Apple Watch and are not uploaded, and your free daily allowance is counted on the device too. Deleting the app deletes them. Syncing them to the web is planned for a later version, and this section will change when it ships.

Camera (from version 2.1). Reading text with the camera, and translating what it reads, happens on your iPhone with Apple's on-device recognition and translation. Photos and camera frames never leave the device. The first time you use a language pair, iOS may download a language pack from Apple.

Account and subscription

An account is optional. The app creates an anonymous identity with Firebase Authentication in the shared iWatchly project so your premium state works across your devices; you can sign in with Apple or Google in Settings to make it a full iWatchly account, the same one the other iWatchly apps use. Deleting your account in the app deletes the iWatchly account and its data across those apps. Premium is an auto-renewable subscription sold only through Apple's In-App Purchase, with RevenueCat checking the receipt; no card or bank details reach us.

Apple Watch

The Watch app works the same way, and takes your account and premium state from the paired iPhone.

iWatch Videos holds your own audio and video files so they can play on Apple Watch without an iPhone. What it collects depends on the version you run, and the difference matters, so both are stated.

Version 3.0 and later

• Your account. The same iWatchly account as iWatch PDF: the email address on your Apple or Google account (or Apple's private relay address), your display name if provided, and a Firebase Authentication user id. You may use the app without signing in; an anonymous identity is created on the device, and its library is moved into your account if you sign in later.
• Your media. Files you import are uploaded to Google Cloud Storage in a location only your account can read, together with a version encoded for the Watch, a thumbnail, its duration and a waveform. Titles, playlists and favourites are stored in Firestore.
• Your devices. An identifier for each iPhone and Apple Watch signed in, its name, and which items each has downloaded, so the app can show what is on the Watch.
• Subscription state. Whether your account has Pro, provided by RevenueCat from the App Store receipt. Apple handles payment; we never see card details.
• Podcast subscriptions (when available): the feed addresses you subscribe to and which episodes you downloaded.
• AI features (when available, and only for an item you ask about): the audio of that item is transcribed by a speech-to-text provider, and the transcript may be sent to a language-model provider to make chapters, summaries, answers or questions. Results are stored with the item and metered against your allowance.
• Screen recording. The app can record your iPhone's screen, with the playing app's audio and, if you switch it on, your narration from the microphone. Recording happens only when you start it yourself and choose iWatch Videos in iOS's recorder; nothing is recorded while no broadcast is running. The recording is written on the device into the app and is then treated like any other imported video: stored in your account's private cloud storage and available to your Watch.
• Microphone. Used for voice recordings you make in the app and, only if you turn it on, for narration during a screen recording.
• Photos. Only the videos you pick are copied into the library; the app does not read the rest of your photo library.

Between your devices, data moves over Apple's WatchConnectivity, and the Watch downloads media directly from your account's private cloud storage over an encrypted connection.

Version 3.0 uses no analytics, no session recording, no advertising SDKs and no tracking across apps.

Versions before 3.0

Earlier versions did not have accounts. Each install created an anonymous identity and a short transfer code; media you imported was uploaded to our storage so the Watch could download it, addressed by that code. Those versions also used Firebase Analytics, Firebase Crashlytics, Crisp support chat, Apple's AdServices attribution and TikTok's attribution SDK, and asked for tracking permission under iOS. Updating to 3.0 stops all of these. Libraries uploaded by earlier versions are kept for six months after 3.0 is released so they can be moved into an account, then deleted.

Retention and deletion

Media stays until you delete it in the app or on iwatchly.com. In version 3.0 and later, Account, then Delete account deletes your whole iWatchly account: after showing what each app holds and asking you to sign in again, it removes your iWatch Videos items, media, playlists and devices, your iWatch PDF documents and data, and the iWatchly sign-in itself, and clears the library on your iPhone and Apple Watch. You can also ask by emailing lokireddy.apps@gmail.com. It does not cancel an App Store subscription; cancel that in your Apple ID settings first. Deleting the app from a device does not remove the copy on our servers.

Watch Browser, AAC Talker, AI Watch Assistant are published by the same developer and this policy applies to them. Each app's App Store listing carries its own privacy label describing what that app collects; a section for each will be added here as it joins the iWatchly account. Questions about any of them go to lokireddy.apps@gmail.com.

The website runs no analytics and sets no advertising cookies. When you sign in, your session is kept in your browser's storage by Firebase and is used only to read your own data from the app backends. The blog is public and requires no account. The Ask iWatchly assistant answers questions from our own guides and app pages. Your question, and the earlier messages of that conversation, are sent from our server to Google's Gemini model (Vertex AI) to write the answer, and Google does not use it to train its models. We keep the question you asked, which of our pages it matched, and your thumbs up or down if you give one, for 90 days, so we can see what the site fails to answer and write a guide for it. We do not keep the answer, the rest of the conversation, your name, your email address or your IP address: the question is stored against the same one-way hash described next, and nothing else. To limit visitors without an account to three questions a day, we keep a count under a one-way hash of your IP address and a random id stored in your browser, plus a count for signed-in accounts; these counts are deleted within two days. The rest of the conversation stays only in your browser tab. Some posts include a YouTube video: nothing is loaded from YouTube until you press play, and the player then comes from youtube-nocookie.com, where YouTube (Google) handles your viewing under its own privacy policy. The website no longer offers a newsletter and collects no email addresses. Addresses given to the earlier newsletter signup are held by Mailchimp (Intuit), in an account that is now closed and sends nothing; write to lokireddy.apps@gmail.com to have yours removed.

Pro subscriptions and one-time purchases are sold only through Apple's App Store, inside each iPhone app. Apple processes the payment; we receive a receipt, not your card details. RevenueCat validates that receipt and tells our services whether your account has Pro. Nothing is sold on iwatchly.com.

• Google (Firebase Authentication, Firestore, Cloud Storage, Cloud Run, Firebase Cloud Messaging, Firebase Analytics, Crashlytics; Gemini for AI features and the website assistant; Cloud Translation and a BigQuery usage log for AI Watch Translator) — hosting, sign-in, storage, notifications, diagnostics, translation.
• Anthropic (Claude) — AI features in iWatch PDF.
• RevenueCat — subscription state from App Store receipts, and campaign attribution where you allowed tracking.
• SendGrid — transactional email.
• Mailchimp (Intuit) — holds addresses given to the earlier newsletter signup, which is closed.
• Crisp — support chat in iWatch PDF, and in iWatch Videos before version 3.0.
• Apple — payments, speech recognition in AI Watch Translator, and AdServices attribution where you allowed tracking.
• Meta (Facebook SDK) — advertising measurement in iWatch PDF.

Each processes data on our instructions under its own terms. We do not sell personal data, and we do not share it with anyone else except as the law requires.

Data travels over HTTPS and is encrypted at rest by Google Cloud. Access to documents and media is checked on every request against the account that owns them; files are served through short-lived signed links, never public addresses.

You can see and delete your data in the apps and on iwatchly.com. You can also ask us to access, correct, export or erase it, or object to a use of it, by writing to lokireddy.apps@gmail.com. If you are in the European Economic Area or the United Kingdom you may also complain to your data-protection authority.

The apps and the website are not directed at children under 13, and we do not knowingly collect data from them. If you believe a child has created an account, write to us and it will be deleted.

When this policy changes, the date at the top changes with it and the previous wording is replaced here. A change that affects what an app collects ships in the same release as the app.