Privacy Policy
Apps covered
Actra
Actra is a social challenge app for creating and completing tasks, submitting proof, sharing progress with a chosen audience, and managing memberships. This policy explains how Herazur handles your information.
Herazur: Discover People
A social discovery app for creating a profile, finding aligned people, joining communities, messaging safely, receiving notifications, and managing premium discovery features.
HomeRecall: AI Item Finder
A private home-memory app that lets signed-in users save where belongings are kept, find them with text or voice, share selected records with household members, and use an AI assistant to interpret item and location requests.
ADHD Daily Planner: Focus Calm
A calming daily planner with reminders, routines, task tracking, and optional account sync.
GigGuard: Contract Scanner
A freelance contract scanner that extracts text from documents and returns risk-oriented analysis.
PlateLens: AI Nutrition Coach
An AI-assisted nutrition app for signed-in users who log meals, scan food photos or barcodes, track body metrics, and manage premium access.
Recallo - CSV Flashcards
An on-device flashcard study app with CSV import, guest mode or optional sign-in, AI explanations, premium features, and ad-supported free access.
StoryBee: AI Bedtime Stories
An AI storytelling app that generates bedtime stories and related premium content.
SubGuard
A privacy-first subscription and free-trial tracker that primarily stores data on the device.
Landscape Design AI
An AI-powered landscape design app that processes user-selected images to generate design ideas and premium outputs.
Hafiz Hoca
An AI-assisted Quran learning app with audio practice, prayer-time features, premium access, and optional sign-in.
Azura: Matris Numeroloji
A numerology and personal guidance app with AI-generated interpretations, premium features, ads, and reminders.
Stitch Atelier: Puzzle
A cozy stitch-themed mobile puzzle game with local level progress, sound preferences, and optional rewarded ads for extra in-game help.
Push Ball: Physics Puzzle
A physics puzzle game with local level progress, scores, coins, unlockable ball skins, sound/language settings, and optional AdMob interstitial and rewarded ads.
Prompt Academy - AI Skills
An AI skills learning app with account sessions, premium access, and generation requests routed through a backend service.
AppPolish AI: UI Redesign
An AI visual redesign tool that analyzes user-selected mobile screenshots and returns visual redesign results and visual analysis.
Brushloop: Toothbrush Timer
A 2-minute toothbrush timer and brushing habit tracker that keeps your brushing history on your device, with an optional account, optional reminders and an optional Premium subscription.
Liferung: Level Up Your Life
Liferung is a real-life progression app: quests earn XP, levels grant Skill Points, skills unlock features such as Focus Mode and the Quest Splitter, and Journeys break bigger goals into chapters that end with a Boss Quest. This policy explains what Liferung stores in your account, what the optional AI features send, and how to delete everything.
PCOS Lab
PCOS Lab is a private cycle, symptom, meal, experiment and lab-result tracker for people with PCOS. By default it collects nothing: no account is created for you, nothing you log is uploaded, and no analytics or crash reporting runs. An account, cloud backup, usage analytics and crash reports are four separate switches, each off until you turn it on yourself. PCOS Lab does not diagnose or treat anything, makes no predictions about your cycle, and does not interpret lab values.
Slowroll: Stop Doomscrolling
Slowroll puts friction in front of the apps you open without meaning to: a breathing pause, an intention question, a short physical challenge. To do that it has to notice which app you just opened, which is the most sensitive thing it does — so it is worth being exact about it. Slowroll has no server of its own. Your rules, your schedules, your intercept history and your streak are written to a database on your phone and are never uploaded; there is no analytics, no crash reporting, no advertising and no tracking of any kind. Two optional things do reach the network — signing in, and buying the paid tier — and neither of them moves your rules or your history off the phone. The blocking itself runs with the network switched off.
Geçtim: Ehliyet Sınav Soruları
Geçtim is an offline-first practice app for the Turkish driving licence e-exam: topic questions, full mock exams, traffic signs, animated questions and lessons. Everything works without an account; signing in is optional and only backs up your study progress. There are no ads, and the full version is a one-time purchase. This policy explains how Herazur handles information in the app.
Privacy Policy
Information we may collect
Account and profile
Firebase account identifiers, email address and sign-in provider information; your Actra username, display name, profile photo, bio and preferences. Firebase Authentication handles email/password and Google sign-in.
Challenges and social activity
Challenges, descriptions, programs, participation, check-ins, completion and review decisions, progress, XP, rewards, follows, friendships, groups, direct challenges, posts, comments and reactions. We also store audience preferences, notification choices, blocks and reports.
Photos, proof and shared content
Photos and text you choose to upload for your profile, task proof or social posts, with related account identifiers and timestamps. Proof is available to you and authorized reviewers. Social sharing is a separate action governed by the audience shown in the app; profile and creator content may be visible to other users or on public share pages. Recipients may copy content they can see.
Device, notification and usage information
Push notification tokens, app and device information, IP addresses processed when connecting to our services, usage events such as screen views and challenge actions, and crash reports and technical diagnostics. Firebase Analytics measures app usage; Firebase Crashlytics helps diagnose failures.
Purchase and membership information
Product identifiers, purchase records, subscription status, expiry, renewals, cancellations, refunds and an account-linked billing identifier. RevenueCat and Google Play process these records to verify and restore Plus and Creator Pro access. Actra does not receive your full payment card details.
Local storage and support
The app stores sign-in state, cached profile and activity data, preferences and account-specific drafts on your device. If you contact support, we process the contact details and information you send to respond and verify privacy requests.
Account and profile information
This can include your email address, sign-in provider details, and basic profile information associated with your account.
Profile and discovery information
Name, username, headline, bio, interests, tags, social links, profile visibility settings, message settings, follower/following relationships, badges, profile activity signals, and similar information you choose to add or generate by using the app.
Profile and community images you choose to provide
Avatar images, profile banner images, and community cover images you select from your device and upload to personalize your profile or communities.
Messages and message requests
Message text, sender and receiver identifiers, timestamps, read state, request status, and message-access signals used to provide conversations and safety controls.
Community and event activity
Communities you create or join, community memberships and roles, join requests and moderation decisions, announcements, event participation, and related activity timestamps.
Safety, privacy, and account-deletion requests
Blocks, reports, report reasons, profile privacy settings, message access preferences, and account deletion requests submitted in the app or through this website.
Push notification data
Android push tokens, platform, optional device identifier, app version, notification delivery records, notification content metadata, and read status needed to deliver and manage notifications.
App activity
This can include feature usage, screen visits, interactions, and similar product signals used to understand how the app performs.
Device and diagnostic information
This can include app version, coarse device details, crash-related information, and technical diagnostics needed to keep the service reliable.
Purchase and subscription information
This includes subscription tier, entitlement status, purchase tokens, restore events, and similar billing-related information supplied by the app stores or subscription providers.
Item, location, and home-memory records
Item names, aliases, descriptions, the physical storage locations you describe, source notes, visibility choice, record history, timestamps, and derived semantic embeddings used to save and find your belongings. The locations are descriptions you enter about objects in your home; HomeRecall does not request your device location.
Household and sharing information
Household name, membership, owner or member role, invitation metadata, and whether a record is private or shared with members of your household. Household-scoped records can be viewed and searched by current members of that household.
Audio recordings you intentionally submit
This includes voice recordings or spoken input used to power audio-based features you request.
Search and AI assistant input
Questions, typed notes, transcribed speech, recent conversation context, and accessible item records needed to answer where an item is or prepare an item-location draft. AI-generated answers, drafts, and embeddings are also processed to provide these features.
Planner data
Tasks, routines, focus sessions, streaks, preferences, and similar content you choose to save inside the app.
Reminder and notification preferences
This includes whether you opt in to reminders and the schedules or settings required to deliver those reminders.
Contract files and images you choose to scan
Documents, photos, extracted text, and related contract analysis inputs that you explicitly upload or capture.
Nutrition profile and body metrics
Name, age, sex, weight, height, target weight, activity level, nutrition goals, calculated macro targets, and weight-history entries you choose to save.
Meal logs and nutrition records
Meal type, timestamps, food items, notes, AI-generated nutrition estimates, and related meal-history data you choose to save.
Meal photos and barcode inputs you choose to scan
Images you capture or select for AI meal analysis, plus barcode values you scan to retrieve packaged-food details.
Advertising and attribution data
Ad-supported builds may process advertising identifiers and related measurement signals subject to your platform settings and applicable law.
Flashcards, deck metadata, and study progress
Deck names, optional descriptions, card front/back text, CSV-imported content, review difficulty, repetition counters, correctness counts, and last-studied timestamps you create or update in the app.
Local app settings and guest-mode state
Guest mode status, total XP, and similar app state or preferences stored on your device so the app can reopen in the state you chose.
AI explanation requests you explicitly trigger
When you tap the AI explanation feature, the selected card question and answer, language preference, and the generated explanation result are processed to return the explanation you requested.
Story prompts and generated content
Prompts, preferences, personalization inputs, generated stories, and related content you request through the app.
Subscription tracking records
Service names, billing dates, trial dates, notes, categories, reminder settings, and other subscription data you choose to save.
Images and media you choose to provide
This includes photos or other media you explicitly select, upload, or attach to use an app feature.
Generated results
This includes outputs created for you by AI or cloud-powered features, together with the input needed to produce those results.
Location data
Approximate or precise location may be used when a feature depends on location context, such as prayer times or direction tools.
Learning progress and community profile data
Practice history, streaks, profile information, reading progress, or community-related data you choose to save.
Personal profile inputs
Birth-related details, profile information, choices, and other inputs you provide to generate numerology-based guidance.
Local game progress and settings
Highest unlocked level, stars earned for completed levels, sound preferences, and similar gameplay settings are stored locally on your device.
Advertising and SDK diagnostics
Rewarded ads are served through Google Mobile Ads (AdMob). Depending on your device settings and applicable law, the ad SDK may process IP address, advertising identifiers, app interactions such as ad views or taps, and diagnostic information for ad delivery, measurement, and fraud prevention.
Local game progress, scores, coins, and settings
Best score, unlocked and completed levels, level stars, last played level, coins, unlocked skins, selected skin, skin ad progress, sound preference, language preference, and theme preference are stored locally on your device so the game can restore your progress and settings.
Local gameplay statistics
The game stores local per-level counters such as starts, completions, failures, retries, best time, and best stars. These records are kept on your device and are used to maintain gameplay state and progression feedback.
Advertising, consent, and SDK diagnostics
Push Ball uses Google Mobile Ads (AdMob) for interstitial ads and rewarded ads. Depending on your device settings, consent choices, region, and applicable law, Google Mobile Ads may process IP address, advertising identifiers, ad views, ad taps, app interactions related to ads, consent status, and diagnostic information for ad delivery, frequency capping, measurement, and fraud prevention.
Learning progress and saved preferences
Course progress, onboarding choices, premium access state, and similar data needed to continue where you left off.
Prompt and generation requests
Prompts or other inputs you intentionally send to AI-powered learning or playground features.
Screenshots and reference images you choose to provide
AppPolish processes the screenshot or reference image you intentionally select so it can analyze the design and generate a visual result.
Prompts and design preferences
This includes the prompt, requested visual direction, screen type, and other choices you provide to guide the analysis and image generation.
Brushing records and settings (stored on your device)
Morning and evening brushing sessions (date, time, timer length, or a manual "Already brushed" log), optional floss days, toothbrush replacement dates, XP, levels, achievements, personal records, and app settings such as reminder times, sound, vibration, theme and timer length. These records are saved only in the app's local storage on your device; we do not receive them.
Account information (only if you sign in)
An account is optional. If you create one, Firebase Authentication processes your email address, a Firebase user ID, your sign-in method (email and password, or Google), whether your email address is verified, and, for Google sign-in, the name Google shares with the app. Passwords are handled by Firebase Authentication; we never see or store them. Your brushing history is not uploaded or linked to your account.
Usage analytics and crash reports
Unless you turn off "Share usage & crash reports" in Profile > Your data, Firebase Analytics records app usage events such as screens opened, onboarding completed, a brushing session completed (morning or evening, timer or manual log, duration and XP gained), levels, achievements and weekly goals reached, Premium plans viewed or unlocked, and sign-in, sign-out and account deletion. Firebase Crashlytics collects crash reports and diagnostics such as stack traces, device model, operating system and app version. These services use Firebase installation and app instance identifiers and approximate location derived from IP address. Events do not include your name, email address or account ID, and the app does not use the Android advertising ID.
Premium purchase and subscription information
When the app starts, it checks with RevenueCat whether Brushloop Premium is active on this device. When you view plans, buy, or restore Premium, RevenueCat and the app store also process the products you choose, subscription and free-trial status, renewal and expiration dates, and purchase tokens or receipts. These records are linked to an anonymous RevenueCat app user ID or, while you are signed in, to your Brushloop account user ID (not to your name or email), so Premium can be restored on your other devices, and include basic technical information needed to validate purchases, such as app version, operating system, store country, and IP address. We never receive your payment card details.
Account and profile information
Liferung needs an account. Firebase Authentication processes your email address, a Firebase user ID and your sign-in method (email and password, or Google Sign-In); with Google sign-in it also receives the name and email address Google shares with the app. Your Liferung profile stores your display name, your email address, the life categories you choose as focus areas, whether onboarding is complete, and the times the profile was created and last updated. Passwords are handled by Firebase Authentication; we never see or store them.
Quests, Journeys and progress history
Everything you create is stored in your own account area in Cloud Firestore: quests (title, description, category, difficulty, due date, repeat rule, reminder time, status, completion and skip history, and sub-quests created with the Quest Splitter), Journeys with their chapters and Boss Quest, unlocked skills, achievements, focus sessions (start time and duration), XP transactions, daily statistics including the anti-abuse counters, weekly reviews, and your level, rank, total XP, Skill Points and momentum streak. Only your signed-in account can read or write this data; Liferung has no social feed and other users cannot see it.
Text you send to the optional AI features
Smart Journey generation and, with Liferung Plus, suggested steps in the Quest Splitter are optional and only run when you start them. When you use them, the text you submit is sent to a Google Gemini model through Firebase AI Logic so it can return a draft: for a Journey the goal you type plus any optional context you add (category, target date, prior experience, minutes per day); for step suggestions the quest title, description and category. Requests are authorized with your Firebase Authentication and App Check tokens, so the app carries no separate API key. We do not log the text you submit or the model output; only counts, error types and status codes are recorded. Nothing is saved to your account until you review the draft and keep it.
Reminder settings and notification tokens
Your notification settings are stored with your profile: the master switch, quest reminders, daily quest reminders, Journey target reminders, and the daily planning reminder with the time you choose. The reminders themselves are scheduled by your device operating system using the device time zone, so their content stays on the device. If you allow notifications, Firebase Cloud Messaging issues a push token for that device, which is stored in your account together with the platform and an update timestamp so Liferung can reach the devices you use.
Usage analytics, crash reports and app integrity
Firebase Analytics records product events such as a quest completed, a skill unlocked, a rank-up, a focus session finished or a Plus plan viewed, with your Firebase user ID set as the analytics user ID. By design these events never include quest titles, descriptions, notes, goals, Journey text or your email address. Firebase Crashlytics collects crash reports and diagnostics such as stack traces, device model, operating system and app version, and likewise contains nothing you wrote. Firebase services use installation and app instance identifiers and process the IP address of the connection, from which approximate location can be derived. Firebase App Check uses Google Play Integrity to confirm that requests come from a genuine, unmodified installation.
Liferung Plus purchase information
Liferung Plus (annual, monthly or lifetime) is sold through Google Play and managed with RevenueCat. Your RevenueCat app user ID is your Firebase user ID, so Plus follows your account to your other devices. RevenueCat and Google Play process the plans you view, buy or restore, entitlement, trial, renewal, expiry and cancellation status, purchase tokens or receipts, and the basic technical details needed to validate a purchase such as app version, operating system, store country and IP address. They never receive your quests, Journeys or notes, and we never receive your payment card details.
Data kept on your device
The app keeps a local copy of your account data through Firestore offline persistence so quests and Journeys can be read and edited without a connection, along with your sign-in state, preferences such as theme and accent, and the counters that limit how often the AI features run. This local copy is removed when you clear the app storage or uninstall the app.
Health records stored on your device
Everything you enter is written to the app’s private storage on your phone: cycle and bleeding days, symptom entries, meals and what they were made of, weight if you choose to record it, notes you type, experiments (what you tried, the dose, the dates, why you stopped), lab results you type in, and your settings such as which symptoms you track, reminder time, units, theme and language. This is health information, and in most places it is treated as a special category of personal data; on your device it is protected by your phone’s app sandbox and by whatever device encryption you have enabled. With every switch left off, this is the whole of it: we have no copy and no way to obtain one.
Account information, only if you create an account
If you choose to sign up, we store the email address you register with — or the address and display name your Google account provides — together with an account identifier, through Firebase Authentication acting as our processor. That is all an account is for. It unlocks no feature, it is not required to use the app, and creating one uploads none of your health records. Legal basis (GDPR / KVKK): performance of the service you asked for, Art. 6(1)(b) GDPR.
Cloud backup of your records, only if you turn it on
With backup switched on, a copy of the days you logged (symptoms, flow, weight, notes and meals), your experiments, your lab results and your tracked-symptom list is kept in your account in Google Cloud Firestore, in the eur3 multi-region (Belgium and the Netherlands); the data does not leave the European Union at rest. Your reminder time, theme and language are not sent. Only your own signed-in account can read it: the Firestore security rules admit a request only when the authenticated user id matches the owner of the record, and there is no administrative path, no shared collection and no query that spans users. Switching backup off deletes the cloud copy and stops anything further being sent, leaving what is on your phone exactly as it is. Legal basis: your explicit consent to the processing of health data, Art. 9(2)(a) GDPR.
Usage analytics, only if you turn it on
A switch of its own, off by default. Usage analytics records which screens and features are opened, and how often — for example that a day was logged, or that an export was taken — through Firebase Analytics acting as our processor. It cannot carry anything you logged: the app can send only a fixed list of event names and, at most, a count of your own records, with no free-text field and no way to pass a value, so a symptom, weight, note, date or lab value cannot reach analytics even by mistake. Legal basis: your consent, Art. 6(1)(a) GDPR, withdrawable at any time.
Crash reports, only if you turn them on
A second, separate switch, also off by default; turning analytics on does not turn this on. If the app crashes, Firebase Crashlytics sends the technical stack trace and your device model and operating system version, so the fault can be found and fixed. Nothing you typed is attached, and no account identifier is attached. Switching either sharing switch off stops collection at the SDK level — not merely our own calls — and deletes anything captured that has not yet been sent. Legal basis: your consent, Art. 6(1)(a) GDPR, withdrawable at any time.
Subscription status, only if you subscribe to Pro
Pro is an optional paid tier. It needs no account in this app and changes nothing about what is stored or uploaded. Until you open the Pro screen, nothing about payments runs at all: the purchase library is not started and no payments company is contacted; if you already subscribe it starts at launch instead, to check whether the subscription is still active. The payment is handled entirely by Apple or Google, and the app never sees your card number, your billing address or your name. RevenueCat sits between the app and the store and answers one question — whether this installation’s subscription is active — receiving a random identifier it generates for the installation, the store’s own purchase receipt, and the device and country information the store attaches to it. It is never told your email address, your account in this app, or anything you have logged. Attribution and advertising-identifier collection are switched off in that library, and no advertising identifier is read.
Exports and shares you start yourself
Data leaves your phone in no other way than when you deliberately send it: an export as CSV or JSON, a PDF summary for an appointment, or a shared progress card, which renders an image containing only aggregate numbers and shows it to you before anything is shared. Each is built on the device and handed to your phone’s share sheet; where it goes next is your choice, and that destination’s own privacy policy then applies — your email provider, cloud drive or messaging app. We are not a party to it and cannot see it.
Which app is in the foreground (accessibility service)
Blocking works by way of Android’s accessibility service, which tells Slowroll when a new app window comes to the front. The service is declared for one event type — a window changing — and with screen-content retrieval switched off, so the system does not hand it the text on your screen at all. Slowroll cannot read your messages, your passwords, what you type or what you browse inside another app; it learns a package name such as "com.instagram.android" and the moment it appeared, decides in memory whether a rule applies, and discards the rest. Nothing from this stream is transmitted anywhere, and the only trace kept is the intercept record described below.
Your rules and history, stored on your phone
Slowroll writes to a private database on your device: the apps you chose to watch and how each is configured (pause length, intention question on or off, challenge type and target, any custom task name you typed), your schedules, a record of each intercept — the app, the time, why it fired, what you chose, how long you spent on the screen and how much of the challenge you completed — a per-app daily open count, your streak, and your settings such as theme, reminder time and grace period. This lives in the app’s sandbox on your phone. We have no copy of it and no way to obtain one.
The intention question
When the intercept screen asks why you are opening an app, your one-tap answer and anything you type in the note field stay in memory for as long as that screen is open and are then discarded. Neither is written to the database, and neither leaves the device. The question exists to make you pause, not to build a record.
Usage access, for the Statistics tab
If you grant usage access in Android settings, Slowroll asks the system for the screen-time figures it already keeps — foreground time and launch counts per app — and shows them to you. They are read when you open a screen that needs them, never copied to a server, and never combined with anything else. Revoking usage access empties the Statistics tab and changes nothing about blocking.
Motion sensors, only during a challenge
Push-up, squat and burpee challenges read the accelerometer and proximity sensor while the challenge screen is open, and the step challenge reads Android’s step counter, which is why the app asks for physical-activity permission. Readings are counted in memory and thrown away as the screen closes; only the number of reps or steps you completed is kept, alongside that intercept. Nothing is shared, and the app works without the permission — every other challenge type is unaffected.
Account information, only if you create an account
Signing in is optional and entirely separate from everything above. If you choose to sign up, Firebase Authentication — acting as our processor — stores the email address you register with, or the address and display name your Google account supplies, along with an account identifier. That is the whole of it. An account uploads none of your rules, history or statistics, and it unlocks no feature: blocking, schedules, challenges and statistics are identical signed in and signed out. Legal basis (GDPR / KVKK): performance of the service you asked for, Art. 6(1)(b).
Purchase records, only if you buy the paid tier
The paid tier is sold through Google Play, and its entitlements are managed by RevenueCat acting as our processor. Opening the subscription screen asks RevenueCat which plans exist; buying one hands you to Google Play, which takes the payment. No card number, billing address or other payment detail ever reaches the app or us. What RevenueCat then holds is a purchase record: which product you bought, when it started and when it renews or expires, the store’s transaction identifier, the country the store reports, and an identifier the SDK generates for the app on your device. Signed out, that record sits under an anonymous identifier; signed in, the app links it to your account identifier so the subscription follows you to a new phone. We can see in the RevenueCat dashboard that a subscription exists and what state it is in — nothing about how you use the app. Legal basis (GDPR / KVKK): performance of the contract you entered into, Art. 6(1)(b). RevenueCat’s privacy information: https://www.revenuecat.com/privacy/
Android’s own backup, if you have it on
Slowroll takes part in Android Auto Backup, so if backup is enabled on your phone your rules, history and settings can be copied into your personal Google Drive backup and restored when you set up a new device. That copy belongs to your Google account, not to us; we cannot read it. You control it in your device’s Google backup settings.
Study progress and settings stored on your device
Your answers, mock exam results, Yanlışlarım (review box) items, bookmarks, sign progress, streak and daily statistics, and your settings (exam date, licence class, daily goal, reminder time, text size, theme) are stored in a local database on your device. If you do not sign in, they never leave your device and we cannot see them.
Account information (only if you choose to sign in)
If you create an account with email and password, Firebase Authentication processes your email address, a password hash and a unique account identifier. If you continue with Google, it receives your Google account email, name, profile photo URL and account identifier from Google. We never see your password or your Google password.
Cloud backup of your progress (only when signed in)
While you are signed in, a compressed copy of the study progress and settings listed above is stored in Cloud Firestore under your account, together with the backup time, app and content version, platform, size and a checksum, so you can restore it after reinstalling or changing phones. The backup contains no question texts, no payment data and no content from other apps.
Anonymous usage events
Product events such as a question being answered (with its category and whether the answer was correct), a mock exam being started or finished (score, duration, unanswered count), a lesson being listened to or a share card being created, together with an app-instance identifier, device model, operating system, app version and an approximate country or city derived from the IP address. No name, email address, phone number or advertising identifier is collected, and events are not linked to your identity.
Crash and diagnostic information
If the app crashes or hits an error, a crash report with the stack trace, device state, app version and a Crashlytics installation identifier may be sent so the problem can be fixed. No user identifier is attached.
Purchase information
When you buy or restore the full version, Google Play or the App Store processes the payment and RevenueCat receives the purchase receipt and an anonymous RevenueCat identifier to confirm and restore access. Automatic collection of device identifiers in RevenueCat is turned off. We never receive your payment card details, and the full-version status is not stored in our own database.
Question error reports
If you use "Bu soruda hata mı var?", only the question ID and the reason you selected are sent as an anonymous event. The optional note you type stays on your device.
Privacy Policy
How we use information
Provide the app
Authenticate accounts, synchronize activity, run challenges and review proof, calculate progress and rewards, display content to its permitted audience, and deliver notifications you enable.
Payments, reliability and safety
Verify and restore purchases, maintain subscription access, diagnose crashes, understand feature usage, prevent abuse, process reports and blocks, respond to support and privacy requests, and meet applicable legal obligations.
Your choices and rights
Edit your profile and manage discovery, progress visibility, history, comments, blocks and notification preferences in the app. Depending on applicable law, you may request access, correction, deletion, a copy of your information, or object to or restrict certain processing by contacting herazur41@gmail.com. Where processing relies on consent, you may withdraw it. You may also contact your local data protection authority.
Authenticate users and secure accounts
We use account data to sign you in, keep your account secure, and restore access across sessions or devices.
Sync app data across devices
When an app supports cloud sync, we use account-linked data to keep your saved content available on more than one device.
Provide personalized app features
We use the information needed to enable the specific personalized features you choose, such as local context or guided practice.
Provide discovery, profiles, communities, and messaging
We use profile, interest, follow, community, and message data to rank discovery results, show public profiles, operate communities, enforce message limits, and help users communicate safely.
Deliver reminders and notifications
We use reminder settings to schedule the notifications you ask the app to send.
Manage premium subscriptions
We use billing and entitlement data to sell, restore, validate, and manage premium access.
Improve product quality and performance
We use analytics and diagnostics to understand reliability, troubleshoot issues, and improve app experience.
Respond to support and deletion requests
We use contact and account details to verify requests, answer support questions, and process privacy-related actions.
Meet legal, tax, security, and fraud-prevention obligations
We may process limited data when necessary to comply with law, enforce agreements, prevent abuse, or protect users and the service.
Save, find, and share your home memory
We use item, location, household, and visibility information to store records, search your accessible memory, maintain location history, and show household records only to authorized household members.
Generate the output you request
When you use an AI or cloud-powered feature, we process the input you provide so the app can return the requested output, analysis, or guidance.
Protect accounts and operate the service
We use limited request and diagnostic information to authenticate requests, prevent abuse, investigate failures, and keep the service reliable.
Serve or measure ads in supported versions
In ad-supported versions, ad-related data may be used to deliver, cap, measure, or protect advertising activity.
Look up packaged-food details from scanned barcodes
We process barcode values you scan so the app can fetch matching product information and prefill a food entry.
Import or export content you choose
We process files or records only to complete the import, export, backup, or sharing action you request.
Store records locally on your device
Some apps are designed to keep your records on-device so core functionality works without maintaining a remote user database.
Run the brushing timer and track your habit
Your on-device records are used to guide brushing sessions zone by zone, show today's morning and evening status, weekly and monthly progress, XP, levels, achievements and personal records. This processing happens on your device.
Provide optional accounts
If you sign in, your account information is used to authenticate you, verify your email address, reset your password, keep Premium available on devices where you sign in, and delete your account when you ask.
Improve reliability and the app
Aggregated usage analytics show which features help people keep a brushing habit, and crash reports help us find and fix problems. You can turn both off at any time in Profile > Your data.
Run the progression system
Your quests, Journeys and history are used to award XP, calculate levels, ranks, Skill Points, skill unlocks, achievements, streaks, charts and weekly reviews, to show the current Main Quest and your active Journey, and to apply the anti-abuse limits that stop the same action from being repeated for XP.
Give you an account, and a backup if you ask for one
An account exists so that a cloud copy can belong to someone. Cloud backup exists so your records survive a lost or replaced phone and follow you to another device. Both are optional, both are off until you switch them on, and each can be switched back off in the same place you turned it on.
Notice a watched app and show the intercept
The foreground-app signal exists for one reason: to decide, within a fraction of a second, whether the app you just opened has a rule and what should stand in front of it. A foreground service keeps that monitor and its session timers alive so an intercept fires the instant it is needed rather than a minute later.
Show you your own numbers
Your intercept history, open counts and streak are kept so the app can show you how often you reached for something and how often you turned back. They are for you to read, and nobody else receives them.
Give you an account, if you want one
An account exists so that a future shared-streak feature has something to attach to. Today it does nothing else, and there is no sync: creating one does not move your data off the device.
Sell and restore the paid tier
Purchase records exist so the app can tell whether the paid capabilities are unlocked, restore them when you reinstall or change phones, and keep working while the store retries a declined card. The blocking engine never asks this question. Watching an app, the pause screen, the intention question, effort-to-unlock, strict mode, session lengths and daily caps are free on as many apps as you like; what the subscription adds is longer history, the remaining challenge types and more than two schedules. A lapsed subscription never removes configuration you already made.
Optional sign-in and progress backup
If you sign in, we use your account to authenticate you, back up your study progress, restore it on a new device, and delete it when you delete your account. Signing in unlocks no feature and is never required.
Sell and restore the one-time full version
We use purchase data only to unlock, verify and restore the one-time full version. There are no subscriptions and nothing renews automatically.
Privacy Policy
Permissions and sensitive access
Selected photos and camera
When you choose to attach a photo, the app uses the system photo picker or camera flow. Only media you choose to submit is uploaded. Actra does not request contacts, microphone or precise-location access in the current Android app.
Notifications
Notification permission allows task updates, reminders and social activity notifications. You can change this permission in Android settings and adjust categories in Actra.
Notifications
to send reminders, alerts, or updates you choose to receive
Photos and media
to let you select images or media from your device
Microphone
to record audio you intentionally submit for app features
Camera
to capture an image you intentionally want the app to analyze or save
Files and documents
to let you import, export, or attach files you choose
Location
to provide location-aware features such as prayer times or direction tools
Vibration
to give a gentle haptic cue when it is time to switch brushing zones and when a session ends; you can turn vibration off in the app
Run at startup
to restore your scheduled brushing reminders after the device restarts
Internet and network state
to sign in to an optional account, send usage analytics and crash reports (unless turned off), and load, buy, restore and verify Premium through RevenueCat and the app store; brushing, tracking and reminders work offline
Google Play billing
to let you buy or restore Brushloop Premium through Google Play
Vibration
to give a short haptic cue with reminders and focus session alerts; you can turn reminders off entirely in Settings
Run at startup
to re-schedule your pending reminders after the device restarts; Liferung uses inexact alarms and does not request exact-alarm permission
Internet and network state
to sign in, sync your quests, Journeys and progress, run the optional AI features, receive push notifications, and load, buy, restore and verify Liferung Plus; creating and editing quests also works offline and syncs later
Google Play billing
to let you buy or restore Liferung Plus through Google Play
Notifications
If you turn on the daily check-in reminder, the app asks your phone to schedule local notifications. These are alarms your device sets for itself: no push server is involved and no notification content leaves the device. The app requests no camera, microphone, contacts, photos, files or location access.
Accessibility service
This is how the app knows a watched app was opened, and without it nothing is blocked. It is declared for window-change events with screen-content retrieval off, so it cannot read what is on your screen. You grant it yourself in Android settings and can revoke it there at any time.
Display over other apps
The pause and challenge screen has to appear on top of the app you just opened. Without it, the intercept would arrive behind the very app it is meant to stand in front of.
Usage access
Only for the Statistics tab, so the app can read the screen-time figures Android already keeps. Blocking works without it.
Physical activity
Only for the step-count challenge, which reads Android’s step counter while that challenge is running. Decline it and every other challenge type still works.
Notifications
For the ongoing notification Android requires while the monitor is running, and for the optional daily reminder. These are scheduled by your own device; no push server is involved and no notification content leaves the phone.
Battery optimisation exemption and run at startup
Offered, never required. Some manufacturers stop background monitors, which would silently switch blocking off; the exemption and the boot receiver are what make blocking survive a restart or an aggressive battery manager.
Notifications
requested only when you tap "Hatırlat" to receive at most one study reminder per day at the time you choose; you can turn it off in the app or in system settings
Privacy Policy
Data retention and deletion
We keep personal data only for as long as needed to operate the relevant app, provide the feature you requested, resolve disputes, enforce agreements, and meet legal, tax, fraud-prevention, or security obligations. Data stored locally on your device generally remains there until you delete it or uninstall the app.
Each app-specific page may include additional retention notes where a feature stores account, subscription, AI, or exported file data differently.
Privacy Policy
Account deletion resources
If an app allows account creation, you should provide both an in-app way to start deletion and a web resource that can be linked in Play Console.
- Actra account deletion page
- Herazur account deletion page
- HomeRecall account deletion page
- Calm Planner account deletion page
- GigGuard account deletion page
- PlateLens account deletion page
- Recallo account deletion page
- StoryBee account deletion page
- Landscape Design AI account deletion page
- Hafiz Hoca account deletion page
- Azura Matris account deletion page
- Prompt Academy account deletion page
- Brushloop account deletion page
- Liferung account deletion page
- PCOS Lab account deletion page
- Slowroll account deletion page
- Geçtim account deletion page
Privacy Policy
Security
We use reasonable administrative, technical, and organizational safeguards designed to protect personal data against unauthorized access, loss, misuse, or alteration. No method of transmission or storage is perfectly secure.
Privacy Policy
Children's privacy
Unless an app-specific page says otherwise, our apps are intended for a general audience and are not knowingly designed to collect personal data from children under 13 without appropriate legal basis or parental involvement.
Privacy Policy
Contact
Developer: Herazur
Privacy contact: furkangokaytolucc@gmail.com
Support email: furkangokaytolucc@gmail.com
Address: Contact by email for mailing address, Turkiye
We aim to respond to verified privacy requests within 30 days.