Privacy policy

Caspian Tools is a software studio operating at caspiantools.com. For the products we host — the Workspace, EntirelySafe, iCompetent, and the Zekio Android app — we are the data controller for the personal data described in their sections below. For the products that run on your own machine, there is usually no personal data for anyone to control; each section says so explicitly.

For any question about this policy, or to exercise the rights set out below, email privacy@caspiantools.com.

The sections in Across everything are the commitments and mechanics that hold for the whole studio — what we never do, how this marketing site itself behaves, and how to get your data out or deleted.

Product by product then covers each thing we ship. Every product section answers the same three questions in the same order:

• What it collects — the data the product actually handles.
• Where it lives — your machine, our servers, or a third party.
• What leaves your device — every outbound request the product makes, and what triggers it.

Where the answer is "nothing", the section says nothing rather than padding it out. A short section is a good sign.

These hold for every product on this page, with no exceptions:

• We never sell, rent, or trade your personal data.
• We never use advertising networks, advertising identifiers, or cross-site tracking, and we set no advertising cookies anywhere.
• We never use session-replay or behavioural-profiling tools. No Mixpanel, PostHog, Segment, Heap, Amplitude, FullStory, or similar.
• We never join analytics data to your account, and never collect anything through analytics that identifies you personally.
• We never read the contents of your source code, repositories, or files except where a product section below names the exact feature that does so, at your explicit request.
• We never send marketing email. Our email is transactional only.

This is the public marketing site — the pages you are reading now. It is a static export with no accounts and no server-side logic of its own.

Analytics. We use Google Analytics 4 (measurement ID G-VMPE9NHWPJ) to understand which pages are used and roughly where visitors are. How we ask for it depends on where you are, so that we follow the consent rules that apply to you.

• EU/EEA, UK, and Switzerland — where prior consent is legally required, nothing analytics-related loads until you choose Accept in the consent banner. No script, no cookie, no call to Google Analytics happens before that. Decline (or ignore the banner) and it never loads. We detect your region from your browser's time zone, not by sending your IP address to any location service.
• Everywhere else — Google Analytics loads by default. You can opt out at any time via Cookie settings in the footer.

When analytics is active it collects which pages you view, approximate location (country/region, derived from a truncated IP that GA does not store), and device and browser type. Google LLC is an additional processor for that data; this may involve transfer to and processing in the United States under Google's terms. Opting out (or withdrawing consent) stops further collection and clears the analytics cookies.

Storage this site uses. Your analytics choice, kept locally in your browser (not a cookie sent to us) so we only ask once; and, only while analytics is active, Google Analytics' _ga and _ga_* cookies, which are removed when you opt out. That is the entire list.

You have the right to access, export, and delete your data. To exercise any of these, email privacy@caspiantools.com from the address on your account, naming the product. We aim to respond within 14 days.

For the Workspace, account deletion removes your authentication record, your user profile document, your stored GitHub and AI provider keys, and your membership in every workspace and project. Workspaces you solely own are deleted with all their contents. Workspaces you share with other members remain; your individual edits become attributed to your deleted-user record.

For EntirelySafe and iCompetent, deletion removes your account and profile. Content you published into a shared space — a forum topic, a reported incident, an assessment another organization relies on — is handled as each of those sections describes.

For Zekio, deletion removes your account, profile, test history, favourites, leaderboard entries, reviews, the reports you filed, and your avatar — and you can do it yourself from inside the app. See Deleting your account and data in the Zekio section for exactly how to ask and what happens.

For the products that run entirely on your own machine — Caspian Security, Caspian Emulator, Caspian Office, Caspian Defender, and the offline parts of the two VS Code extensions — there is nothing for us to export or delete, because we never had it. Uninstalling and deleting the product's local files is the complete removal.

Caspian Tools products are not directed at children. If you are under 16, please do not create an account on any of them. If you believe a child has signed up, email us and we will delete the account.

We log changes to this page in the repository's commit history and call them out in the changelog. The Last updated date at the top reflects the most recent change.

The authenticated developer workspace — projects, tasks, notes, sprints, milestones, flows, and GitHub Issues sync. This is the only product of ours that stores the work you do in it on our servers.

What it collects. When you sign in: your email address, display name, and avatar URL as provided by your sign-in provider (Google, GitHub, or email-and-password), plus a Firebase user ID assigned to your account. When you use it: the tasks, notes, sprints, milestones, projects, flows, and comments you create; attachments you upload; workspace and project membership records; and per-event in-app notifications addressed to your account.

Where it lives. All of it is stored in Firebase services (Firestore, Auth, Storage, Cloud Functions), hosted by Google Cloud in region europe-west4 (Eemshaven, Netherlands). Cloud Functions execute in the United States us-central1 region as a deployment constraint, but they do not persist data outside Firestore. Google Cloud is the only processor for the data you create.

Cookies and browser storage. A session HTTP-only cookie holds your Firebase session, set when you sign in and cleared when you sign out; Firebase Auth's own client-side storage (cookies and IndexedDB) keeps you signed in across tabs.

GitHub integration. If you connect a GitHub account so that tasks push to GitHub Issues, your GitHub OAuth access token is issued by Firebase Auth's GitHub provider and then stored server-side, in a vault at /githubTokens/{uid} that is denied to every client by our Firestore security rules and readable only by the Cloud Function that performs the push. It never touches browser storage. Storing it is what lets your edits sync in the background instead of opening an authorization popup on every edit. Disconnecting GitHub in Settings deletes the stored token, and so does deleting your account.

We never receive or process the contents of any private GitHub repository beyond the specific issues that the product opens, edits, or closes on your behalf, the dependency manifests read by the optional dependency scan, and the one-off source snapshot read by the optional security scan — both only on repositories you bind to a project, and the security scan only when a member presses Scan or the project owner has turned on its daily auto-scan.

Security scan. Pressing Scan on a project's Security tab downloads the repository's default branch, using the pressing member's GitHub token, into temporary storage inside a single Cloud Function run. That run checks it with the Caspian Security engine and deletes the copy before it finishes; no source code is kept, and none of it is sent anywhere else. What is stored is the list of findings — rule, severity, file path, line number, and the rule's own message — readable by members of that workspace. The text a rule matched is deliberately discarded, so a detected secret is never copied into the report. The project owner can also turn on a daily auto-scan (off by default); it works the same way, once a day, using the owner's GitHub token, and can be turned off at any time on the same tab.

AI features (bring your own key). AI features are off unless you supply your own provider API key. That key is stored server-side in a second client-denied vault at /aiKeys/{uid}; only the Cloud Function that makes the call can read it. When you invoke an AI feature, the text it needs — the prompt for that feature — is sent to the provider you chose, under your own account with them and their terms. We record per-call usage (feature, model, token counts, cost) so you can see your own spend against your own budget cap. Disconnecting clears the key.

Email. Transactional only — currently invite emails, when a workspace owner adds you. We use the Firebase Trigger Email extension; the underlying SMTP provider sees the recipient address and message body.

Task, sprint, and milestone tracking inside your editor. It is local-first: cloud sync is opt-in and off until you pair it.

What it collects. Nothing, until you pair. Your tasks live in files in your own project. The extension sends us no telemetry, no usage statistics, and no crash reports.

If you pair it with a Workspace. Pairing opens a page on caspiantools.com where you sign in and pick a workspace; a Firebase token bound to that account and workspace is minted and returned to the extension, and the refresh token is kept in VS Code's SecretStorage, which is encrypted at rest by your operating system's keychain. From then on, the tasks, sprints, and milestones you have chosen to sync are stored in the Workspace exactly as the Workspace section describes, and every write is stamped with the account that made it so the two sides can tell each other apart. Unpairing stops the sync and discards the stored token.

GitHub. Tasks attributed to a project with a bound repository can be pushed to that repository's Issues. The push is authored as you.

AI triage. If you enable AI-suggested triage, the task text is sent to the AI provider you configured, under your own key and their terms. We are not in that path and never see the request.

Markdown notes pinned to your project. Same shape as Caspian-Taskmaster: local files first, optional sync, no GitHub leg — notes have no GitHub representation and are never pushed there.

What it collects. Nothing, until you pair. Your notes are markdown files in your own project folder. No telemetry.

If you pair it with a Workspace. The same pairing flow and the same SecretStorage token handling as Caspian-Taskmaster, under its own separate key, so the two extensions sign in independently on one machine. Synced notes are then stored in the Workspace as described in the Workspace section. Deletion is bidirectional: a note you delete locally is deleted in the cloud, and a note deleted in the cloud is deleted locally.

The security scanner — VS Code extension, CLI, MCP server, and GitHub Action. The rule engine runs entirely on your machine. Your code is never uploaded to us, in any channel.

What it collects. Scan findings, ignore decisions, and learning data (rule effectiveness, fix patterns, learned safe patterns) are stored per workspace on your own disk. The .caspianignore file is written into your project so your team can share it — nothing about it reaches us.

Telemetry is off by default. If you turn it on, it shares anonymized rule-effectiveness statistics: rule codes and numeric counts only. No code, no file paths, no project names. The Preview Telemetry Data command shows you the exact payload before you enable it, and you can turn it off at any time.

AI fixes are opt-in, per invocation. Before anything leaves your workspace, a dialog names the file, the provider (Anthropic, OpenAI, or Google), and exactly how much code will be sent. By default only about twenty lines around the finding are sent — not the whole file — and the fixed region is spliced back in locally. Full-file context is a setting you have to turn on deliberately. The provider is billed to your own API key, which is stored in VS Code's OS-backed SecretStorage and never written to settings.json.

Dependency checks. The optional OSV.dev check sends dependency names and versions only to api.osv.dev — never your code. npm audit behaves as npm normally does.

Android emulator and device management inside VS Code. It is a front end for Google's own Android SDK tools running on your machine.

What it collects. Nothing. There is no account, no sign-in, and no telemetry. Settings stay in your VS Code configuration; screenshots, screen recordings, logcat exports, and capture runs are written to a folder inside your own project.

What leaves your device. Only downloads you ask for: when you choose automatic SDK setup, the extension fetches the Android SDK command-line tools, platform-tools, emulator, and system images from Google's own distribution servers. Those are ordinary downloads to Google, subject to Google's terms, and they carry nothing about you or your project. Everything else — ADB, the emulator, logcat, file browsing, screen mirroring — is local traffic between your editor and a device you control.

The free offline toolkit of PDF, image, and utility tools. Every tool runs in your browser, on your device.

What it collects. Nothing. There is no account and no sign-in.

Your files are never uploaded. The tools process files in the browser tab itself; no file you open is transmitted to us or to anyone else, and we have no server that could receive one. It is installable and works offline, and you can download the whole app as a single self-contained HTML file and run it with no network at all — which is also the easiest way to verify this claim for yourself.

What leaves your device. When you use the hosted version, your browser requests the page and its assets from our host and checks for a newer version, the same as visiting any web page. Nothing about your files is part of that request.

A React e-commerce library you install into your own application, with your own Firebase project behind it.

What it collects. Nothing, for us. We publish source code; we run no service for it and have no access to any deployment of it. Nothing in the library reports back to Caspian Tools.

Who the controller is. If you ship a store built with it, your customers' data lives in your Firebase project, on infrastructure you own, and you are the data controller for it — including the obligation to publish your own privacy policy and to configure the Firestore security rules the library ships as a starting point. Any payment or email provider you connect is your relationship with that provider, not ours.

The health, safety, and environment community platform at entirelysafe.com — news, incidents, events, vacancies, courses, business directory, and forums. It is a hosted service with accounts, so it holds more personal data than anything else we ship apart from the Workspace.

What it collects. Your account identity from your sign-in provider (email-and-password or Google); the profile you choose to fill in, which can include a bio, company affiliation, country, language, and a resume with work experience, education, skills, and projects; the content you submit — articles, incident reports, events, vacancies, courses, businesses, classifieds, forum topics and replies, comments; your bookmarks, course enrolments, quiz scores, and certificates; and in-app notifications addressed to you. Aggregate analytics — page views, search queries, share counts — are recorded for the site itself.

Where it lives. Firebase (Firestore, Auth, Cloud Storage), hosted by Google Cloud.

Published content is public. Anything you publish — a forum post, an incident report, a job listing, a comment — is visible to the world and is the point of the platform. Submissions from ordinary accounts are held as drafts for admin review before they go live. Your member profile is visible in the member directory. Deleting your account removes your account and profile; content already published into shared discussions may be retained in place so that threads other members took part in remain readable — tell us if you want a specific post removed and we will remove it.

Third parties. Paid courses are checked out through PayPal, which receives what it needs to take the payment; we store the resulting order record, not your card details. Certain editorial features use an AI provider (Google Gemini, OpenAI, or Anthropic) and a text-to-speech provider to draft or narrate course and article content — these operate on editorial material, not on member profiles. Stock imagery is fetched from Pexels. Administrators can issue scoped API keys for external integrations; those keys grant access to the site's content API and are revocable from the admin panel.

The competency-management platform at icompetent.com — define skills, have assessors evaluate your team, and carry a portable competency profile between organizations. Hosted by us, with accounts.

What it collects. Your account identity and profile; the competencies, skills, and evidence attached to your profile; assessment records — who assessed what, when, and with what outcome; and the organization and assessor relationships that connect those records together.

Where it lives. Firebase (Firestore, Auth) on Firebase App Hosting, hosted by Google Cloud. A single sign-on session cookie is scoped to the.icompetent.com domain so that the marketing site and the application share one sign-in.

Your profile is portable by design. The point of the product is that an assessment follows you rather than being locked to one employer, which means an organization you join can see the competency record you bring. An assessment someone else recorded about you is that assessor's record as much as yours; we will not silently rewrite it, but you can always see it, dispute it with us, and take your profile elsewhere.

Third parties. Some features use Google Gemini for AI assistance; the text those features need is sent to Google under their terms. No assessment data is used to train anyone's model.

Zekio (zekio.caspiantools.com) is a free practice-test app for exams taken in Turkey — the LGS high-school entrance exam, the YÖS for international students, and the İSG occupational safety specialist exam — published on Google Play by Caspian Tools. It has no ads, no subscription, and no in-app purchases. An account is optional: without one you can browse the tests, take any of them, see your score and read reviews, and nothing about you is sent to us. You need an account to keep your results in it, appear on the leaderboard, save favourites, have a profile, and write or report a review — the paragraphs below about your account, your use of the app and the leaderboard apply only once you create one.

What it collects — your account. You register with an email address and password, or with Google Sign-In. We store your email address, a display name, and the Firebase user ID assigned to your account. A two-step onboarding, which every new account goes through, asks for the language you study in and the exam you are preparing for, which also sets your school grade where the exam has one. Your country is kept in your profile and shown as a flag on the leaderboard. All of these stay editable from your profile. Zekio does not ask for your date of birth. A profile photo is optional — if you choose one it is uploaded to our storage bucket as users/{uid}/avatar.jpg.

What it collects — your use of the app. Your test history, which tests you have passed, the avatars you have unlocked, and the score entries written when you finish a test. If you rate or review a test, your star rating and review text are stored with your display name and avatar, and are shown to everyone who opens that test — including people using Zekio without an account. Reviewing is optional; taking tests is what the app is for.

The leaderboard is visible to other students. When you finish a test while signed in, a score entry carrying your display name, country, and score is written to the leaderboard, which every signed-in Zekio user can read. It is not readable by people without a Zekio account, and a test finished without an account never reaches it. Please treat your display name as visible to other students — and, on a review you write, to anyone who opens that test — and do not use your full legal name. Nothing else from your profile — not your email, exam, grade, or history — is ever visible to another user.

No analytics, and no advertising ID. Zekio contains no analytics SDK. Firebase Analytics — the only thing that had ever contributed one — was removed before the app was published, and the app's manifest blocks the advertising-ID permission so that no future dependency can bring it back. Zekio never reads or transmits the Android Advertising ID, shows no ads, and runs no advertising or ad-measurement SDK. It contains no Crashlytics or any other crash-reporting SDK either, so we receive no automatic event or crash data about how you use the app.

What stays on your device. The first-run flag and the markers that decide which tests carry a "new" badge are kept in the app's local storage only, and downloaded question packs are cached on the device so that tests work offline. If you use Zekio without an account, the tests you finish — which test, your score and the date — are kept there too, so that your level, points and streak survive closing the app; clearing the app's data deletes them. None of that is transmitted to us or to anyone else, and signing in does not upload a guest's results: an account shows only its own history. Your favourites are the exception: they are kept on the device and saved to your account as users/{uid}/favorites, so the tests you star are still there when you sign in on another device.

Where it lives. Google Firebase — Authentication, a Firestore database named zekio, a Cloud Storage bucket named zekio-app, and Cloud Functions — hosted by Google Cloud. Google acts as our service provider for all of it. We do not share, sell, or transfer your data to any third party, and no data from Zekio is used to train anyone's AI model.

Age, and a note for parents. Zekio is built for students aged 13 and over and is not directed at children under 13. We do not knowingly collect data from anyone under 13. If you are a parent or guardian and believe a child under 13 has created an account, email privacy@caspiantools.com and we will delete the account and everything attached to it. Parents and guardians may use that same address to ask what we hold about their child, to request a copy, or to have it deleted.

Your rights under KVKK (Turkey). Zekio's users are primarily in Turkey. Under Article 11 of Law No. 6698 on the Protection of Personal Data (KVKK), you have the right to learn whether your personal data is processed and to request information about it, to learn the purpose of the processing and whether it is used accordingly, to know the third parties to whom it is transferred at home or abroad, to request correction of incomplete or incorrect data, to request its erasure or destruction, to require that any correction or erasure be notified to third parties to whom the data was transferred, to object to a result produced solely by automated analysis, and to claim compensation for damage arising from unlawful processing. Caspian Tools is the data controller (veri sorumlusu). Address your request to privacy@caspiantools.com.

Your rights under GDPR. Where the GDPR applies to you, you have the rights of access, rectification, erasure, restriction, portability, and objection, and the right to lodge a complaint with your supervisory authority. Our legal basis is the performance of our agreement with you, which covers everything needed to run your account and deliver tests. We process nothing for analytics or advertising. The same address reaches us.

Caspian Defender (defender.caspiantools.com), published by Caspian Tools, blocks apps and websites on the phone it is installed on. It has no account, no server behind it, and no analytics, and it is built so that there is nothing for us to collect even if we wanted to.

What it collects. Nothing, for us. There are no accounts, no ads, no advertising identifier, no analytics, and no crash reporting, and we operate no servers for the app — there is no address for your data to be sent to. Your rules, your history, and your keys stay in the app's private storage on your device, excluded from cloud backup and from device-to-device transfer.

What leaves your device. Two kinds of traffic, and only these:

• DNS lookups. Defender runs a local VPN (VpnService) that carries DNS and nothing else: only resolver addresses are routed into it — Defender's own stand-in resolver, plus the public resolvers an app might address directly instead of asking the system — so your browsing, your messages, and every other kind of traffic never reach the app. That is a property of how the tunnel is configured, not a promise about our conduct. A lookup is decided on the device — blocked, held back for a few seconds, redirected (where a rule asks for safe search) to a search engine's own filtered front end, or forwarded untouched to the resolver your network already gave the device (or, for a query an app addressed to a public resolver directly, that same resolver). We run no resolver. Whoever could see your DNS before you installed Defender sees exactly the same queries afterwards. Defender keeps no log of the names it looks up; what it writes down is the much smaller set of names it acted on, described under what is stored below, and that stays on the phone. Debug builds sample a few queries to ask Android which app owns the connection; release builds never ask, and nothing is recorded either way.
• A blocklist download, when you tap one. Defender maintains no blocklists of its own. It offers a short catalog of well-known malware, phishing, and tracker lists, and a field for any URL you type. Tapping one makes a single HTTPS request to that server (currently urlhaus.abuse.ch, phishing.army, small.oisd.nl, pgl.yoyo.org, or raw.githubusercontent.com, none of them ours), which — as with any download — sees your device's IP address and the usual request metadata. The list is kept on the phone as an ordinary set of names in a rule. Nothing about you, your rules, or your usage is sent with the request. There is no subscription and no background refresh: a list is fetched once, when you ask, and never again on its own.

The accessibility service. To hold back an app, Defender needs to know which app just came to the front. Its accessibility service subscribes to one event type — a window coming to the front — and reads the package name of that window. It is configured with canRetrieveWindowContent="false", so it cannot read what you type, what you read, or what is on the screen. Nothing it sees leaves the device.

If you turn on scroll pauses in a rule, and only while a rule uses them, it also subscribes to scroll events. A scroll event says that a list in the app in front moved, and how far; Defender uses it to count roughly how many items you have scrolled past, and every so many it lays a three-second pause over the screen. It does not say what is in the list, and nothing about it is stored or leaves the device.

Optional permissions, all off until you turn them on.

• Usage access — for screen time (how long each app was in front today, how often it was opened, how often the screen came on) and for a fallback app blocker, which asks Android which app is in front roughly once a second instead of relying on the accessibility service. Screen time is read from Android when the screen opens and never stored by Defender.
• Notification access — to take notifications from a blocked app off the shade, and separately to count how often each app posts one. Counts only: package, day, and a number, kept ninety days. There is no place in the database for a title, a body, a sender, or a time.
• Location — requested for one reason: from Android 10 on, an app cannot read the name of the Wi-Fi network it is joined to without it, and that name is what a place rule matches on. Your coordinates are not requested, used, stored, or sent, and there is no background-location permission. The network name you put into a rule is stored with the rule. Because Android tells an app in the background nothing about the network, the name of the network the phone is on is also kept from the last time Defender could read it, beside an identifier for that one connection, so a place rule keeps working while the phone stays on it; it is overwritten at the next read and never leaves the device. Skip the permission and everything else in the app still works.
• Physical activity — the driving lock subscribes to vehicle-journey start and end events from Google Play services' activity recognition: two events per journey, no location and no route. Defender keeps the current state, not a history of journeys. The API is part of Google Play services, a Google component on your phone under Google's own terms; Defender sends it nothing but the subscription.
• Calls — a rule can limit phone calls to a list of numbers. To do that Defender asks Android to make it the phone's call redirection app and its caller ID & spam app, two roles you grant on Android's own dialog from the rule's Calls card. With them, the phone shows Defender each call being dialled or ringing in, and Defender lets it through or stops it by comparing the number with the rule's list on the device. Nothing about a call is sent anywhere. On Android 11 and later it may also ask for contacts permission, for one reason: without it the phone never shows a screening app a call from a saved contact. Defender does not open your contacts — adding a number "from contacts" uses Android's own picker, which hands back only the one number you chose.
• Device administrator — only so that Android refuses to uninstall the app while it is active. It declares an empty policy list: Defender cannot wipe the device, lock the screen, reset or read a password, or watch what you do. The administrator can be switched off in Android's settings, after which the app uninstalls normally. On a phone set up from a factory reset, Defender can additionally be made device owner over ADB, which lets its privacy check actually refuse a permission to another app rather than only report it. While protection is on, a device-owner Defender also makes itself the always-on VPN, stops its own force stop and data clearing, and refuses safe mode, VPN and Private DNS settings, date and time changes, and new users or work profiles; turning protection off lifts all of it. That is a deliberate manual act by whoever sets the phone up. It changes what Defender can do to other apps and to the phone's settings; it collects nothing.

What is stored on your device.

• Your rules — their names, the sites and apps in them, schedules, the Wi-Fi network names you typed, and the phone numbers a rule allows calls with, each with the contact name it was picked under.
• The urge map — one row per blocked attempt, slow-down, or bypass: when it happened, whether it was a site, an app, or a call, which one (for a call, the number; a caller who withheld theirs is written without one), which rule, and the outcome. Kept until you clear it.
• Today's counters — per-app opens, and per-app foreground time where a rule has a daily budget. Yesterday's are deleted at the midnight reset.
• Notification counts, if enabled — package, day, and a number, kept ninety days.
• Charity pledges — the amount and link you set yourself, and whether the link was opened. Defender handles no money.
• What the privacy check remembers — two lists, each replaced whole at the next daily scan: every app on the phone that has a launcher icon, so that a newly installed one can be named, and which apps hold the camera, microphone, or location, so that a change can be pointed out.
• The Wi-Fi network the phone is on — its name and an identifier for that one connection, from the last time Android let Defender read it, so a place rule works with the app closed. Overwritten at the next read.
• Your settings, unencrypted, and — held apart from them in Keystore-backed encrypted storage — your guardian's TOTP secret and your app password's hash.

All of it lives in the app's private storage. Android backup is switched off for the app and everything is excluded from cloud backup and device-to-device transfer, so none of it is copied to a Google account or carried to a new phone, and it is removed when you uninstall the app. Two honest notes: the rules database stays readable at rest so that blocking keeps working while the app is locked — the app password is a gate on the screens, not encryption, and someone with physical access to an unlocked phone and enough patience can read the database; the app says so on its own lock screen. And the fallback blocker, if you use it, records today's foreground time for every app that comes to the front, not only the ones in a rule (the accessibility service records only apps in a rule), until the midnight reset.

Exports. You can export your rules to a file you choose, encrypted with a passphrase you set. After that it is yours; if you put it in a cloud drive it lives there under that provider's terms. We never see it.

Deletion, sharing, and children. We hold nothing about you, so there is nothing for us to delete or export — uninstalling the app removes everything it stored. We share and sell nothing, because nothing is held. Caspian Defender is not directed at children and collects nothing from anyone; when a parent installs it on a young person's phone, the rules and the urge map stay on that phone, readable by whoever can unlock it, and are never sent to us.