Privacy Policy for Bloka Tag

Last updated 31 October 2026

1. Scope and contact

This notice covers the Bloka iOS and Android apps and bloka.shop. BLOKA operates the service. For privacy questions and rights requests contact blokatag@gmail.com. Core features do not require a Bloka account; this does not mean that no personal data is processed.

2. On-device data and permissions

Selected apps, groups, schedules, preferences, session history, statistics and object photos are stored on your device. iOS uses Apple Screen Time frameworks. Android accesses installed apps for selection; Accessibility detects the foreground app package and displays the blocking screen. The blocking feature does not read typed text or screen contents or upload your installed-app list. Optional notification access checks the originating app locally and can dismiss notifications during sessions without transmitting their contents. Camera, NFC, notifications, background operation and battery optimisation exemptions support enabled features. You can revoke permissions in system settings; related features may stop working. System backups may include local data depending on device settings.

3. Camera and AI processing

Object identification and comparison send one or two compressed photos, the object name and text instructions over HTTPS to our Cloudflare proxy. It can use Google Gemini, Cloudflare Workers AI and OpenAI if configured as a fallback. Failed requests may be retried with multiple providers. Reference photos also remain on your device. The image relay service does not maintain a photo archive but processes requests and logs technical results, timings, models and errors. Cloudflare processes network data including IP addresses for security and rate limits. Provider retention depends on applicable service terms and settings; we do not promise zero retention. Avoid faces, documents and sensitive data and submit only images you may share. Comparisons can be wrong and are not intended to identify people.

4. App analytics and advertising attribution

Both apps use Mixpanel with data collection in the EU region and a persistent pseudonymous identifier. Events may include app opens, version, platform and technical details, onboarding answers (age, occupation, habits and self-reported screen time), permissions, purchases and trials, group and schedule counts, session mode and duration, goals and streaks. Selected-app names and photos are not part of these events. iOS also integrates Meta App Events and a Cloudflare server connection for conversion, purchase and trial events, with event/transaction identifiers, amounts, currency and technical data. The advertising identifier is read when authorised through App Tracking Transparency. Denying ATT does not disable Mixpanel or all server communications. The reviewed app versions enable Mixpanel analytics automatically; this notice does not constitute tracking consent.

5. Purchases, access recovery, referrals and support

Apple and Google process in-app payments; Bloka processes product, purchase/trial status and transaction or purchase identifiers to verify access. We do not receive full payment card numbers from these stores. Stripe processes website payments; orders involve email, name, delivery address, optional phone, order items and payment/delivery status. A purchase email entered to restore tag access is processed to verify purchased access rights, including through our website and Stripe. Referral features may process codes, identifiers, progress and rewards and contact details if you request delivery. Support processes messages and attachments you send.

6. Website, email and tracking

The site uses Netlify hosting/functions, Cloudflare services/resources, Stripe checkout/orders and MailerLite email subscriptions/campaigns. Signup may include email, language, source and discount code. Unsubscribe using the email link or by contacting us. Meta Pixel and Conversions API may process page views, clicks, checkout/purchase events, IP, browser, identifiers and email or phone for matching, including hashes. Cookies and localStorage also support attribution, preferences, popups and A/B testing; test records are stored in Netlify Blobs. Hashing does not anonymise contact details. Advertising tracking requires prior consent where applicable; visiting or continuing to browse does not provide consent. Browser controls can clear or block storage but do not replace the site’s duty to obtain consent.

7. Purposes and legal bases

Data necessary for requested features, access verification, orders and support is processed to perform a contract or precontractual steps (GDPR Art. 6(1)(b)); tax records for legal obligations (Art. 6(1)(c)); data strictly necessary for security, abuse prevention and legal claims for legitimate interests balanced against your rights (Art. 6(1)(f)). Marketing and non-essential tracking require consent where applicable (Art. 6(1)(a) and device-access rules). OS permissions do not replace other required consent. Withholding necessary data prevents the relevant feature or order; promotional data is optional.

8. Recipients and international transfers

Recipients include the providers above, shipping carriers and advisers or authorities where necessary. Provider roles depend on applicable services and contracts. Mixpanel’s EU endpoint does not guarantee that all processing by all providers stays in the EEA. International transfers may occur and must use adequacy decisions or appropriate safeguards such as standard contractual clauses where required. Contact us for information about applicable safeguards.

9. Retention

Local settings and photos remain until deleted or app data is removed, subject to system backups. Order records are retained for fulfilment, support and applicable tax/legal periods; access-recovery records for as long as necessary to recognise purchased rights. Promotional contacts remain until withdrawal or the purpose ends, with suppression records where needed to honour opt-outs. Technical logs and analytics retention depend on purpose and provider configuration; we do not claim unverified automatic deletion periods. The website identifier cookie is set for 365 days; browser local storage copies may remain until cleared. Contact us for details of external service retention.

10. Rights, children and changes

Where applicable you may request access, correction, erasure, restriction and portability, object to legitimate-interest processing and withdraw consent without affecting prior lawful processing. To locate pseudonymous records we may need your installation identifier or sufficient request details. You may complain to the Italian data protection authority or your local authority. The service is not directed to children under 13; local parental authorisation and consent rules also apply to minors. Object comparison is not used for decisions with legal or similarly significant effects. We will publish updates here and communicate material changes appropriately.

11. Provider notices

Mixpanel · Meta · Google Gemini · Cloudflare · OpenAI · Stripe · Netlify · MailerLite

Back to Home