Privacy Policy
Effective date: October 28, 2026
This Privacy Policy applies to the OpLoop mobile application for Android and iOS, hereby referred to as the “Application,” and the OpLoop website at oploop.app. The Application and website are provided by StudioJson, hereby referred to as the “Service Provider.”
This Privacy Policy explains what information the Application may process, how it is used, and what choices you have. Most of it applies to both platforms. Where the Android and iOS versions work differently, mainly in how blocking is carried out on the device, the difference is described in a part marked for that platform. By using the Application, you agree to the processing of information as described in this Privacy Policy.
1. Privacy Summary
The Application is a blocker for applications and websites that operates primarily on your device. Blocking decisions, routines, the applications and websites you select, usage statistics, and records of blocking events are stored locally on your device and are not transmitted to the Service Provider. The rules of a Circles challenge, which include the applications and websites that challenge blocks, are the exception described in Section 6.
The main categories of information that are transmitted are:
- account information, such as your email address and a display nickname, if you choose to sign in;
- achievement badge unlock state, if you are signed in;
- if you join Circles challenges, your nickname, avatar, challenge participation and results, points and items, check-ins, and a device check value, as described in Section 6;
- purchase, subscription, and entitlement status, when you purchase or use paid features;
- information used to attribute an installation to a referral, invitation, or partner link, as described in Sections 6 and 10;
- advertising identifiers and related information, when advertising is displayed on the free tier;
- analytics identifiers, application usage events, tier, device information, and approximate region, as described in Section 9;
- technical information needed to deliver a feature you use, such as push tokens for notifications, as described in Section 7;
- an anonymous report of a blocking message, if you choose to report one;
- information you submit on the website, such as your email address if you ask to be notified about a release;
- a diagnostic summary, if you choose to send a support email from within the Application, as described in Section 4.
Signing in is optional. The Application’s blocking features and paid features operate without an account.
The Application does not include its own crash reporting library. It does not request access to your location, contacts, camera, microphone, photos, files, calendar, messages, or call logs.
2. How Blocking Works on Your Device
On both platforms, blocking is decided on your device. What the Application uses to decide whether something should be blocked stays on the device and is not transmitted to the Service Provider. Android and iOS give applications different tools for this, so each is described separately below.
If you take part in a Circles challenge and blocking stays turned off for longer than the challenge allows, the Application reports that the challenge has ended for that reason. Only that fact is reported; nothing used for blocking is sent (see Section 6).
On Android: Accessibility Service
The Android version uses the Android Accessibility Service to provide its blocking features. Through it, the Application identifies which application is in use and, for features you enable, examines what is on the screen to the extent those features require — for example, recognising a short-form video screen, or reading the address of a website open in a web browser so that blocked websites can be blocked.
This happens on your device, and its only use is deciding whether to block and operating the blocking features, such as returning to the home screen or closing a blocked window. Information obtained through the Accessibility Service is not stored beyond what is needed for that purpose and is not transmitted: the Application keeps no record of what you viewed, browsed, or typed, and does not collect passwords, account credentials, or payment details. Records of blocking events are stored on your device so that the Application can show your own statistics.
The Accessibility Service may also be used to keep features you use, such as Circles check-ins, working reliably while the device is in use.
You may disable the Accessibility Service at any time in Android Settings. The Application’s blocking features will not operate while it is disabled.
On iOS: Screen Time
The iOS version uses Apple’s Screen Time capabilities, with the access you grant, and blocking is applied by iOS according to the rules you set. The Application does not see which applications or websites you select in a readable form, and it cannot read the content of other applications, the pages you visit, or what you type.
Your selections, rules, and usage statistics stay on your device and are not transmitted to the Service Provider. Some figures shown in the Application are estimates.
You may revoke the Application’s Screen Time access at any time in iOS Settings. The Application’s blocking features will not operate while access is revoked.
3. Information Stored on Your Device
The following information is stored in local storage on your device, such as a local database, preference files, or the Application’s shared container. Except for the items expressly noted below, it is not transmitted to the Service Provider and no server-side copy exists.
- routines, including schedules, blocking modes, overlay tones, and escape policies;
- application groups and the applications, categories, and websites you have selected to block or allow;
- blocking events, including when a blocking screen was shown and for which application or website;
- application usage information, such as daily usage minutes;
- temporary unlock and pass usage;
- focus session records, including mode and duration;
- records of which blocking messages have been shown, and which you have reported (the report itself is sent — see Section 4);
- achievement badge unlock state (synchronised to your account if you sign in — see Section 5);
- your nickname (synchronised if you sign in — see Section 4), daily reset time, pass policy, language, and other settings.
Usage and installed applications (Android)
The Android version may use Usage Access and the list of applications on your device to show the application selection screen, apply blocking rules, and calculate usage statistics. This is done on your device, and this information is not transmitted.
Backups and deletion
Some information stored by the Application may be excluded from, or included in, device backups depending on the platform and your backup settings. Deleting the Application deletes most of its locally stored information, which cannot be recovered by the Service Provider. Certain identifiers may remain on the device after deletion where the operating system retains them.
4. Information You Provide
Signing in is optional. The Application’s blocking features operate without an account, and paid features may be purchased and used without an account. If you choose to sign in, you may do so with a supported sign-in provider, such as Google or Apple, or with an email address that receives a verification code. The Application does not use passwords.
If you sign in, the following information is processed:
- your email address, or an address provided by your sign-in provider, held by the authentication provider so that verification codes can be sent and the account identified;
- a provider identifier and the information the provider shares with your permission, such as a name, if you sign in with a provider such as Google or Apple;
- a display nickname;
- account timestamps, such as the date the account was created.
The Service Provider’s account record contains an account identifier, a nickname, timestamps, badge state, and, if you join Circles, the information described in Section 6. Your email address is held in the authentication provider’s access-controlled schema, which is required in order to send sign-in codes. The Service Provider does not store an additional copy of it in its own tables.
Nickname
A nickname is generated on your device when the Application is first launched. Until you join Circles, it is a display name that is not required to be unique and is not shown to other users; if you sign in, it may be synchronised so that it is available on a new device. When you join Circles, the nickname you confirm must be unique within Circles and is shown to other people as described in Section 6.
Message reports
If you report a blocking message, the Application sends the identifier of that message, its language, the type of blocking screen it appeared on, the reason you selected, the message pack version, and the time of the report. This is used to find and rewrite messages that land badly. The report is sent without an account token and carries no identifier of you or of your device, so it cannot be attributed to you or linked to your other reports. It does not include which application was being blocked, and nothing is sent unless you choose to report.
Release notifications
If you ask on the website to be notified about a future release, the Service Provider stores the email address you enter, the referral or campaign code and any campaign parameters contained in the link you arrived through, the address of the page that referred you, the country reported by the content delivery network, your browser language, and the platform your browser reports. Your IP address is not stored.
This information is used to email you about releases and significant updates and to understand which channels people arrive through. It is not used to build a profile of you, is not combined with any information from the Application, and is not sold or shared for anyone else’s marketing.
Asking to be notified does not create an account, and is unrelated to the Application and its blocking features. Every such email contains an unsubscribe link, and unsubscribing takes effect without signing in.
Referral and invitation links
If you open a referral, partner, or challenge invitation link, the Service Provider may process the code from that link and related technical information in order to direct you to the right application store and attribute the installation, including through temporary identifiers created for that purpose. This information is not used to identify you.
Support requests
If you contact support from within the Application, an email may be prepared containing technical and diagnostic information, such as your device model, operating system and application versions, language, and information about the Application’s recent operation and settings, and identifiers that help look into your request, such as the identifier used for your purchases. Nothing is sent until you send the email yourself, and you may review and edit it before sending. When sent, the Service Provider receives that information together with your email address and the content of your message.
5. Achievement Badges
The Application awards badges when cumulative activity reaches defined milestones. If you are signed in, badge unlock state may be synchronised to the Service Provider so that badges are available after a change of device.
A synchronised badge record consists of the badge’s identifier and the time at which the badge itself was unlocked. It does not include which application was involved, the date or time of any individual blocking or usage event, or any other detail of your activity. The underlying events remain on your device and are not transmitted.
If you are not signed in, badges are stored only on your device. If you sign out, synchronisation stops. If you delete your account, synchronised badge state is deleted with it; badges stored on your device are unaffected.
6. Circles Challenges
Circles is an optional feature for joining time-limited challenges with other people. Joining requires signing in and confirming a nickname. Circles is not required for blocking or for paid features.
If you join Circles, the Service Provider processes:
- the nickname you confirm, a normalised form of it used to keep nicknames unique, and when it was last changed;
- the avatar, colour, and frame you choose, the items you hold, and a record of points earned from completed challenges and spent in the in-app shop;
- for each challenge you join: the challenge, when you joined, its start and end times calculated from your daily reset time and time zone, your platform, your participation status (such as waiting, running, passed, or failed), the reason a participation ended (for example, withdrawal, signing out, blocking turned off for longer than the challenge allows, a change of time, time zone, or installation, or no check-in for an extended period), the times of your check-ins, the number of completed Lockdown sessions where a challenge counts them, points awarded, and whether you have viewed the result;
- so that a participation stays with the device it was joined on: a device check value derived from identifiers on your device (the identifiers themselves are not sent), the time the Application was installed, and your time zone;
- check-ins that the Application sends while a challenge is in progress, carrying the information needed to determine the result, not what you do on the device;
- if you create a challenge: its title, its rules (the applications, websites, or short-form screens it blocks, including display names you give them, or its Lockdown target), its dates, and the icons of the selected applications, which are uploaded from your device;
- if you apply for community challenges: the address of the social media post you submit and when you submitted it;
- if you report another participant or a challenge: the reason you selected, the challenge, and the participant reported.
Circles does not receive anything examined on screen, your usage time, your blocking records, or your routines outside a challenge.
What other people can see
Other people can see your nickname, avatar and colour, and your status in each challenge you join (waiting, running, passed, or failed). The reason a participation ended is shown only to you. Participants of official challenges can be seen by anyone using the Application. Participants of a challenge created by a user can be seen by anyone who has that challenge’s code, including before they join. A challenge’s title and rules, including its application names and icons, are visible to the same people.
If several people report a nickname, it may be hidden from others. If you share an invitation or a result card, the text or image is passed to the sharing application you choose; result cards are created on your device and are not uploaded to the Service Provider.
Invitation links
If you install or open the Application through a challenge invitation link, the code from that link is used to open that challenge and may be sent to the Service Provider to determine whether the challenge owner is an affiliate partner. If so, the installation is attributed to that partner and the partner’s introductory offer is shown; otherwise no affiliate attribution is made. The code is not used to identify you.
Leaving Circles
You may withdraw from a challenge at any time in the Circles tab; the participation remains in your challenge history as withdrawn. Deleting your account deletes your Circles information, as described in Section 16.
7. Sign-In, Session Security, and Notifications
When you sign in, the authentication provider records the IP address associated with the session for the duration of that session as a standard security measure. This information is not used to estimate location, to identify you across services, or for advertising purposes.
Signing out removes the server-side session for that device. If you do not sign in, no session is created and no IP address is recorded for this purpose.
Sessions are refreshed when a feature that requires an account needs them.
Notifications and timer updates
Notifications are shown only if you allow them in your device settings. To deliver notifications and live timer updates, such as a focus session timer on the iOS Lock Screen, the Application may send the Service Provider a push token and the content to be displayed. This does not include account information or the applications you block, and it is kept only as long as needed to deliver the update.
8. Advertising
The free tier of the Application displays advertising in designated places on some of the Application’s own screens. Advertising is never displayed on the blocking screen or during a focus session, and is never part of deciding whether something is blocked. Subscribing to the paid tier removes advertising: on the paid tier the advertising code does not run and no advertising request is made.
Advertising is served by Google AdMob. In order to serve and measure advertising, AdMob may process:
- your device’s advertising identifier, where available: on Android, the Android Advertising ID; on iOS, the Identifier for Advertisers (IDFA), only if you allow tracking when iOS asks;
- device and network information, such as device model, operating system version, language, and approximate region derived from IP address;
- advertising interaction data, such as impressions and clicks;
- diagnostic and performance information about the advertising service itself.
Advertising partners do not receive blocking records, application usage statistics, the applications or websites you have selected to block, the list of applications installed on your device, your routines, your email address, or your account identifier.
The Application itself sends nothing about you with an advertising request. Advertising events, such as impressions, clicks, and revenue, may be recorded for reporting under the anonymous application user identifier described in Section 10, without information about which applications or websites you block, your usage, or your routines.
The free tier may also offer a temporary trial of a paid feature, such as Lockdown, in exchange for watching rewarded advertisements. Where such a trial is offered, completion of the advertisement is verified by Google AdMob and the entitlement provider so that the trial can be granted. The verification identifies the advertisement and the anonymous application user identifier, and contains no information about your use of the Application.
On Android, you may reset or delete your Advertising ID in Android Settings. On iOS, the Application asks for permission to track before the IDFA is used, and you may change that choice at any time in iOS Settings under Privacy & Security. If you are located in a region where consent is required, such as the European Economic Area, the United Kingdom, or Switzerland, the Application presents a consent request before personalised advertising is used, and that choice may be changed later. Subscribing to the paid tier removes advertising from the Application.
Google’s processing of advertising data is governed by its own privacy policy, available at policies.google.com.
9. Analytics
The Application uses Google Analytics for Firebase on both the basic and pro tiers to understand how people move through the Application, improve the Application, and measure the performance of advertising campaigns.
Google Analytics for Firebase may process:
- a Firebase application instance identifier;
- your device’s advertising identifier, where available and permitted (on iOS, only if you allow tracking);
- application usage events, such as onboarding progress, whether permissions and required settings have been configured, paywall views, and purchase steps;
- your tier, recorded as basic or pro;
- device and application information, such as device model, operating system version, language, and application version;
- an approximate region derived from your IP address.
RevenueCat may send subscription status changes, including trial conversion, renewal, cancellation, and expiration, to Google Analytics together with the Firebase application instance identifier. Where analytics consent is required, RevenueCat sends this information only while that consent is in effect.
The Application also uses Tenjin to measure which advertising campaigns lead to installs and subscriptions. Tenjin may process your device’s advertising identifier where available and permitted, device and application information, IP address, onboarding events, and subscription status changes sent by RevenueCat. Tenjin is not used in regions where consent is required, such as the European Economic Area, the United Kingdom, or Switzerland.
Neither Google Analytics nor Tenjin receives anything examined on screen, application usage statistics, lists of installed or blocked applications or websites, blocking records, routines, your email address, or your account identifier. The Application does not set a Google Analytics user ID.
If you are located in a region where consent is required, such as the European Economic Area, the United Kingdom, or Switzerland, the Application is configured so that analytics identifiers are not used before you consent. Until then, only limited event information without these identifiers may be sent, which Google uses to estimate aggregate measurements. The consent request applies to both the basic and pro tiers, and you may change your choice later in the Application’s settings.
10. Payments, Trials, and Entitlements
Paid features are sold through the application store from which you installed the Application, such as Google Play or the Apple App Store, as subscriptions or other purchases offered there. Subscription status and entitlements are managed through RevenueCat.
- The Service Provider does not receive or store payment card information. Payment is processed by the application store.
- An anonymous application user identifier is assigned when the Application is first run, so that paid features may be purchased and used without an account.
- If you subsequently sign in, that identifier is linked to your account identifier so that purchases can be restored on another device. The Service Provider stores a record of this link.
- Purchase-related information, including subscription status, renewal state, trial eligibility, and entitlement validity, is processed to determine whether paid features are available.
- If you install the Application through a partner link (for example, a link shared by a content creator), the partner’s code is used to attribute the installation to that partner and to present the partner’s introductory offer, as described in Section 4. It is not used to identify you.
The entitlement provider may also collect device and application information as part of its own service, governed by its own privacy policy.
11. Information Not Collected
The following categories of information are not collected by the Application.
| Category | Reason |
|---|---|
| Screen content, typed input, credentials | On Android, examined on-device only, in memory, to decide whether to block; on iOS, not available to the Application. Never stored or transmitted |
| Browsing history | Website blocking is decided on the device; no record of the sites you visit is kept or transmitted |
| Application usage transmitted off the device | Statistics are calculated or shown locally |
| List of installed applications transmitted off the device | Used locally only on Android; not available to the Application on iOS |
| Precise location | No location permission is requested |
| Contacts, calendar, messages, call logs | No such permission is requested |
| Camera, microphone, photos, files | No such permission is requested |
| Crash reports from the Application’s own crash reporting | The Application includes no crash reporting library of its own. Diagnostic information is added only to support emails you choose to send (see Section 4). Third-party services may collect diagnostics about their own operation, as described in Sections 8 and 13 |
| Payment card information | Processed by the application store |
The Service Provider does not sell personal information and does not share personal information with third parties for their own independent marketing purposes.
If the Application’s collection practices change, this Privacy Policy will be updated to describe the change before the version that introduces it is released.
12. How Information Is Used
Information described in this Privacy Policy is used to:
- determine on your device whether an application or website should be blocked;
- display the blocking screen and select a message;
- calculate usage statistics, baselines, and comparisons;
- award and display achievement badges;
- run Circles challenges, including determining results, showing participants, awarding points and items, keeping nicknames unique, moderating reported content, and preventing a participation from being carried over by reinstalling or by changing the device’s time;
- provide sign-in and make your nickname and badges available on another device;
- keep timers and notifications you have enabled up to date;
- attribute installations to referral, invitation, and partner links;
- verify and restore paid entitlements and manage subscriptions and trials;
- serve and measure advertising on the free tier;
- measure onboarding and conversion, improve the Application, and measure the performance of advertising campaigns;
- respond to support requests and investigate reported problems;
- maintain security, prevent abuse of trials, referrals, or entitlements, and comply with legal obligations.
13. Third-Party Services
The Application and website use third-party services that process information under their own privacy policies, including:
- Google Play Services, Google Play Billing, and the Google Play install referrer (Android);
- Apple App Store and in-app purchase, Apple Push Notification service, and Apple platform services such as Screen Time (iOS);
- Google Sign-In and Credential Manager, and Sign in with Apple;
- Google AdMob;
- Google Analytics for Firebase;
- Tenjin;
- RevenueCat;
- Supabase;
- Resend;
- Cloudflare.
These services may process information for purposes including authentication, purchase processing, entitlement verification, backend storage, push delivery, email delivery, analytics, advertising, website delivery, and service reliability. The Service Provider may add or replace service providers for these purposes; where a change materially affects the information processed, this Privacy Policy will be updated.
15. Your Choices
- You may use the Application without signing in. Blocking features and paid features operate without an account.
- You may delete your account within the Application, under Settings. Deletion requires confirmation and cannot be undone. Routines, application groups, and passes remain on your device. You may also request account deletion without the Application — see the account deletion page.
- You may sign out to stop badge synchronisation without deleting your account. Signing out ends any Circles challenge in progress.
- You may choose not to join Circles. If you join, you may withdraw from a challenge at any time in the Circles tab, change your nickname and avatar, and report a participant or a challenge.
- On Android, you may disable the Accessibility Service or revoke Usage Access in Android Settings. Blocking or statistics will not operate while they are disabled.
- On iOS, you may revoke Screen Time access in iOS Settings. Blocking will not operate while access is revoked.
- You may turn off notifications, and on iOS Live Activities, in your device settings.
- On Android, you may reset or delete your Advertising ID in Android Settings. On iOS, you may allow or deny tracking in iOS Settings. These choices affect the identifier used for both advertising and analytics. You may also subscribe to the paid tier to remove advertising.
- You may change your advertising and analytics consent choices in the Application’s settings if you are located in a region where consent is requested.
- You may unsubscribe from release notifications at any time using the link in any such email. No sign-in is required.
- You may uninstall the Application to delete all locally stored information.
- You may contact the Service Provider to request access, correction, deletion, or other assistance.
Certain features will not operate if required permissions are denied or revoked.
16. Data Retention
Information stored on your device is retained until you delete it within the Application or uninstall the Application. Certain records are removed automatically in the course of normal operation.
Account information is retained while your account exists. When you delete your account, the account record, synchronised badge state, and your Circles information — nickname, avatar and items, points, challenge participations, community challenge applications, and reports you made or received — are deleted.
A challenge you created is deleted, together with its uploaded icons, when you delete it. Challenges you created remain after your account is deleted, so that people who joined them can continue, and are no longer associated with you.
Short-lived technical records, such as temporary link identifiers, scheduled notification content, and records kept to prevent abuse, are deleted after a short period in the course of normal operation.
Purchase and entitlement records may be retained by the application store and by the entitlement provider under their own retention rules, including where retention is required for accounting, tax, refund handling, or dispute resolution. The Service Provider may retain limited records where reasonably necessary to prevent repeated trial abuse, payment abuse, or entitlement misuse. Such records are intended to be limited and not directly identifying on their own.
Google Analytics event data is retained for 14 months.
A request to be notified about a release is retained until that notification has been sent, and in any event no longer than twelve months from the request, after which it is deleted. Unsubscribing removes you from any further notification.
Support correspondence is retained for as long as reasonably necessary to handle the request and any related follow-up.
17. Security
The Service Provider uses reasonable technical, administrative, and organisational measures to protect information. Network requests are encrypted in transit. Access to backend data is restricted by row-level security rules, and account deletion is performed by a server function that acts only on the account of the authenticated caller.
No method of transmission, storage, or processing is completely secure, and absolute security cannot be guaranteed. You are responsible for maintaining the security of your device, operating system, and sign-in account.
18. Children’s Privacy
The Application is not directed to children under the age of 13, or a higher age where required by applicable law. The Service Provider does not knowingly collect personal information from children under 13 without appropriate consent where required.
The Application contains occasional mild profanity in its blocking messages and is rated accordingly on the application store. If you are a minor, you should use the Application only with the consent and supervision of a parent or legal guardian.
If you are a parent or guardian and believe that a child under 13 has provided personal information through the Application, contact the Service Provider at [email protected]. Reasonable steps will be taken to delete such information.
19. International Users
The Application may be used in different countries and regions. Account, entitlement, and analytics information may be processed and stored in countries other than the country in which you reside, including through the third-party services listed in Section 13. Data protection laws in those countries may differ from those in your location. Where required, reasonable steps are taken to protect information in accordance with applicable privacy laws.
For users in the Republic of Korea, personal information is transferred overseas as follows. Each transfer is made electronically over an encrypted network connection at the time the relevant feature is used.
| Recipient (country) | Information | Purpose | Retention |
|---|---|---|---|
| Supabase, Inc. (servers in Singapore) [email protected] | Account identifier, email address, provider identifier, nickname, badge state, session IP address, and, if you join Circles, the information described in Section 6; attribution codes and temporary link identifiers; push tokens and notification content | Sign-in, account and badge synchronisation, Circles challenges, install attribution, and notifications | Until you delete your account; session IP address for the duration of the session; temporary records for a short period |
| Resend, Inc. (servers in Japan) [email protected] | Email address and the content of the sign-in code email; for release notifications requested on the website, the email address | Sending sign-in codes and requested release notifications | Delivery records up to 30 days |
| RevenueCat, Inc. (United States) [email protected] | Anonymous application user identifier, account identifier if you sign in, purchase and subscription status, and advertising slot and revenue events | Verifying and restoring paid entitlements, trials, and revenue reporting | As described in Section 16 and the recipient’s policy |
| Google LLC (United States) — AdMob Google privacy contact form | Device advertising identifier where available and permitted, device and network information, advertising interactions, and advertising diagnostics, on the free tier | Serving and measuring advertising | Under Google’s retention rules |
| Google LLC (United States) — Google Analytics for Firebase Google privacy contact form | Firebase application instance identifier, device advertising identifier where available and permitted, application usage events, tier, device and application information, approximate region derived from IP address, and subscription status changes sent by RevenueCat | Improving the Application and measuring advertising campaign performance | 14 months |
| Tenjin, Inc. (United States) Tenjin privacy policy | Device advertising identifier where available and permitted, device and application information, IP address, onboarding events, and subscription status changes sent by RevenueCat | Measuring advertising campaign performance | Under Tenjin’s retention rules |
| Apple Inc. (United States) — Apple Push Notification service Apple privacy contact | Push tokens and notification content | Delivering notifications and live timer updates on iOS | Under Apple’s retention rules |
You may refuse these transfers. Blocking and paid features work without an account, so you may refuse the Supabase and Resend transfers by not signing in and not joining Circles. Subscribing to the paid tier stops advertising and the AdMob transfer. Turning off notifications and Live Activities for the Application on iOS stops the Apple Push Notification service transfer. Where an analytics consent choice is available, you may refuse or withdraw it in the Application’s settings; the Application’s core features remain available when you do so. The RevenueCat and Tenjin transfers, and analytics where no consent choice is offered, are necessary to operate the Application; you may refuse them by not installing or by uninstalling the Application, after which it cannot be used.
20. Regional Privacy Rights
Depending on your location, you may have rights to request access, correction, deletion, restriction, objection, portability, withdrawal of consent, or information about how your personal information is processed.
To make a privacy request, contact the Service Provider at [email protected]. Identity verification may be required before a request can be answered. Certain requests may be limited by legal, security, fraud prevention, payment, or entitlement verification requirements.
Requests relating to blocking records, usage statistics, or the applications and websites you block with your own routines cannot be fulfilled by the Service Provider, as that information is stored only on your device. It may be reviewed within the Application and deleted by deleting the Application.
21. Changes to This Privacy Policy
This Privacy Policy may be updated from time to time. When changes are made, the updated version is posted on this page with a revised effective date, or otherwise made available through the Application or the website.
You are advised to review this Privacy Policy periodically. Continued use of the Application after changes become effective indicates that you acknowledge the updated Privacy Policy.
22. Contact
If you have questions or suggestions regarding this Privacy Policy, contact the Service Provider at:
StudioJson[email protected]
This address is also the contact channel for access, correction, deletion, consent withdrawal, and other privacy-related requests.