Last updated: November 12, 2026 · Describes AstraVault 1.2.3, the version on Google Play. Where 1.2.1 or 1.2.2 behaved differently, and many phones are still running them until their owners update, this page says so
AstraVault is a product of AstraSoft, registered in India. AstraSoft is responsible for processing your personal data in accordance with applicable privacy laws.
This page describes AstraVault 1.2.3, the version published on Google Play today. It is the only version Google Play now distributes; 1.2.1 and 1.2.2 are still installed on phones that have not taken the update, and an app only changes on your phone once you update. Section 14 records what changed in 1.2.2 and 1.2.3 and what the older versions still do.
AstraSoft never receives your documents and cannot read them. Every document is encrypted on your phone with AES-256-GCM before it is uploaded, and it is uploaded to your own Google Drive, not to our servers. The key that decrypts it never leaves your device, so we could not produce your documents in readable form even if we were compelled to.
That key is derived from your vault passphrase using PBKDF2-HMAC-SHA256 with 300,000 iterations, and your passphrase itself is verified against a separate 600,000-iteration hash. Both are computed on your device. The key is then stored on your device in Android's encrypted app storage, protected by a key held in the Android Keystore. Because the key is designed to still work after you reinstall the app, a random value used to rebuild it is kept in your own Google Drive — it is not permanently locked to one handset.
AstraVault is not a server-free app. Your documents and their metadata stay on your device and in your Drive, but we do run a Firebase backend for sign-in, licensing, consent records, push notifications and the security and sync records described in section 3. No document content and no encryption key is ever sent there.
One limit worth knowing. If AstraVault cannot reach your Google Drive while you are first setting up your vault, it generates a random encryption key instead of deriving one from your passphrase. Documents encrypted under such a key cannot be recovered after you reinstall the app or move to a new phone — not by you and not by us, even if you still know your passphrase. AstraVault has no recovery-phrase feature, so there is nothing you can write down to guard against this; make sure you are signed in to Google Drive while you set up your vault.
| Data | Purpose | Where it goes | Status |
|---|---|---|---|
| Google account email | Sign-in, Drive access, account identification, account emails | Your profile on our Firebase backend; a separate internal lookup record that stores your address in full alongside your account id and the time of each sign-in; and Google's email service when we send you an account email such as the welcome message | Required |
| Google Drive access | Store your encrypted documents, and the app's own working files | Your personal Google Drive — a visible AstraVault folder, plus a hidden app folder (see section 6) |
Required |
| Document metadata | Finding, sorting and displaying your documents | Name, category, dates, tags, remarks, a quality score, a small thumbnail image, an OCR text snippet (up to 500 characters) and detected details — which include any identifier numbers and any monetary amounts the text recognition picked out. All of it is held in the encrypted database on your device, and backed up encrypted to your own Google Drive so you can restore after a reinstall | Required |
| Subscription status | Free or Pro tier access | An encrypted file in your own Google Drive, and on your device | Required |
| Security event log | Device-security diagnostics and theft response | Kept on your device, and copied to our Firebase backend during background sync — up to 100 entries per sweep, exactly as written and not filtered. An entry's text can include a document's name, and its details can include document identifiers, your device model and the list of accessibility services active on your phone. An authorised AstraSoft administrator can read these records | No opt-out |
| Sync diagnostics | Diagnosing failed uploads | Our Firebase backend: a one-way hash of your account id, the app version, an error code, a retry count, how many items are waiting to sync, and whether Drive is connected. No document names or content | No opt-out |
| Sync summary | Support and account overview | Our Firebase backend: how many documents you hold, their total encrypted size, the pending queue size, the app version and when you were last active, against your account id | No opt-out |
| Consent record and change history | Proof of the choices you made | Our Firebase backend, as a write-once record plus an append-only log of changes | Required |
| Account deletion request | Recording that you asked us to delete your account | Our Firebase backend, admin-readable, written once when you confirm deletion in the app from 1.2.2 onward: your account id, a one-way hash of your account email, the time you asked, which confirmation steps actually ran, and a status of PENDING. Nothing automated reads it; we process it by hand — see section 9. In 1.2.1 confirming deletion in the app recorded nothing at all. The app still has no screen that files a data-rights request or a grievance, so nothing is stored on our backend for those unless you email us | Required (only if you file one) |
| Push notification token | Security alerts, sync status, update notices, and reminders if you have not saved a document yet — for which our backend counts how many reminders you have been sent and when. There is no separate switch for the reminders | Firebase Cloud Messaging, and stored in your profile on our Firebase backend | Required |
| Device identifier | Recognising which device your vault is active on, for theft response and remote lock | A random identifier created once for your installation — not your phone's serial number or advertising ID — written to your profile on our Firebase backend every time the app starts and every time you unlock the vault | No opt-out |
| Crash reports | Identifying and fixing crashes | Firebase Crashlytics (Google) and Sentry (our error-monitoring provider, servers in the European Union), and, from 1.2.2 onward, a server AstraSoft runs itself at opt.astrasoft.info, which receives a copy of the same error reports — all three governed by the crash-reporting switch. Separately, AstraVault writes crash files into its own private storage on your device; from 1.2.2 the error text in them is scrubbed of email addresses and account identifiers as they are written, and they are copied to the hidden app folder in your own Google Drive only if you turned crash reporting on — otherwise they stay on your phone, where clearing the app's data removes them. In 1.2.1 they were written unscrubbed and copied to your Drive whatever you chose |
Off by default in 1.2.3 On by default in 1.2.1 |
| Usage analytics | Understanding how features are used | Firebase Analytics and Firebase Performance Monitoring (Google): event names and their parameters such as screen name, document category, counts and timings, plus the pseudonymous installation identifier Firebase assigns to your copy of the app | Off by default in 1.2.3 On by default in 1.2.1 |
| Install referrer | Understanding how people find the app | Read once from the Play Store and sent to Firebase Analytics: the campaign source and the first 100 characters of the raw referral string | On by default in 1.2.1 |
| Advertising ID | Serving banner and rewarded ads | Shared with Google AdMob. In 1.2.3 your advertising ID is read only after Google's consent platform has allowed it, and only from the Free-tier home-screen banner — so a Pro device normally never starts the ads SDK and never reads the ID, and a refusal, or a consent form that cannot be shown, means no ad is requested at all. In 1.2.1 the ads SDK started on the first screen of every launch and requested an ad, so your advertising ID was read on every launch — whatever your tier, Pro included, and before you had made any consent choice. In 1.2.2 it started from the banner screen, but asked you nothing first. AstraSoft does not store the advertising ID | Consent required in the EEA, the UK and Switzerland in 1.2.3 No opt-out in 1.2.1 and 1.2.2 |
| Device model, OS and app version | Crash context and security diagnostics | Sent with crash and error reports, and recorded in the security log and the compliance records, which have no opt-out | No opt-out |
| Document content (photos, PDFs) | — | Never sent to AstraSoft. Encrypted on your phone, stored in your own Google Drive | Never collected |
| Passphrase or encryption keys | — | Never leave your device | Never collected |
| Biometric data (fingerprint or face templates) | — | Never received or stored by AstraVault — see section 4 | Never collected |
Consent in 1.2.3. Crash reporting and usage analytics both start off. The switches start unticked, Google's crash, analytics and performance collection is disabled in the app itself until you choose, and Sentry error monitoring is not started at all until you have agreed to it. You can change either choice at any time in Settings → Consent Manager, the change applies without restarting the app, and performance monitoring follows the analytics choice. In 1.2.1 both switches started already on, Google's and Sentry's collection all began when the app first launched, before the consent screen appeared, and performance monitoring sat outside the switch entirely, measuring startup, screen, database and network timings whatever you chose. If you are still on 1.2.1, that is still what your copy does.
One further note for completeness: whenever the launch-time integrity check fails for any reason — a signature mismatch, a rooted or emulated device, or an install that did not come from Google Play — the app attempts to file a security alert containing your email address, your account id, your device model and your device's local network address. Our security rules reject that write, so no such record is stored. The attempt is still in the app, 1.2.3 included; we will say so here once it is removed.
AstraVault is built so that document content is encrypted before it travels, and the unencrypted bytes are overwritten in memory as soon as the encryption step finishes. There are, however, places where an unencrypted copy exists on your phone, and you should know about them. None of these are shared or external storage — they are inside AstraVault's own private app storage, which other apps cannot read.
Your device uploads straight to your own Google Drive using your Google sign-in. AstraSoft's servers are not in the path and we have no standing access to your Drive. AstraVault asks for two Drive permissions: drive.file, which lets it touch only files it created itself, and drive.appdata, a hidden folder that Drive does not show you. Signing in with Google also grants AstraVault your basic Google profile and email address, which is how the sign-in itself works; AstraVault reads your email address and does not read your profile name or picture.
What lands where:
AstraVault holds your encrypted documents, as files named with random identifiers. They are grouped into subfolders named after your categories — and those folder names are not encrypted, so anything with access to your Drive can see your category names and how many documents are in each.Your documents and the encrypted index are ciphertext that AstraSoft cannot decrypt. The category folder names, file identifiers, the deleted-document list and the crash files are not encrypted.
When text recognition finds a number laid out like a 12-digit national ID, AstraVault replaces the first 8 digits with X characters and keeps only the last 4. The masked version is what gets saved — in the database on your device, in the stored text snippet and in the search index. The masking cannot be undone, because the hidden digits are discarded rather than encoded.
Please understand its limits, because they are real:
Where you live changes some of these rights. The rights above are the ones we give every user. The law where you live may give you more, and the paragraphs below say what that means in practice. One version is on Google Play — 1.2.3 — but 1.2.1 and 1.2.2 are still running on phones that have not taken the update, and where the three behave differently, this page says which is which.
United States. Under the California Consumer Privacy Act and the comparable laws of Virginia, Colorado, Connecticut, Texas, Utah and other states, you may ask what personal information we hold about you, receive a copy, have it corrected or deleted, and you may not be treated worse for asking. Use Access my data for the copy and write to admin@astrasoft.info for the rest. The categories we hold are identifiers — your account email in full, your account id, a one-way hash of it, an installation id and your device advertising ID — and device and app activity: the security event log, sync failure reports, install attribution, and crash, error, performance and usage diagnostics. We do not sell your personal information and never have. We do send your device advertising ID to Google for ad delivery and measurement, which several of these laws treat as sharing or as targeted advertising. In 1.2.3 no ad is requested until Google's consent platform has answered, and the ads SDK is not started before that — but outside the European Economic Area, the United Kingdom and Switzerland that platform requires no form and records no choice, so there is still no in-app way to stop the sharing and no Ad privacy choices control appears. The control you have is in Android itself — Settings → Privacy → Ads, where you can delete or reset the advertising ID — and Pro removes the banner. On 1.2.1 the ads SDK started on every launch, before any consent choice and for Pro users too; on 1.2.2 it started from the banner screen but asked nothing.
Canada. Under PIPEDA you may ask for access to your personal information, ask us to correct it, and complain to the Office of the Privacy Commissioner of Canada. In Québec, Law 25 adds the right to receive the information you gave us in a structured, commonly used technical format — Access my data produces exactly that, as JSON — and the right to be told when a decision about you is made by automated means, which this app never does. Law 25 also requires us to say who is responsible for protecting your personal information: that is the owner of AstraSoft Labs, reachable at admin@astrasoft.info, which is also where privacy complaints go. We answer within 7 days.
Australia. Under the Australian Privacy Principles you may ask for access to the personal information we hold about you (APP 12) and ask us to correct it (APP 13). APP 8 requires us to tell you that information goes to recipients outside Australia: those recipients are Google, Sentry in the European Union, and a server AstraSoft runs itself; section 10 lists each of them and what it receives. If an eligible data breach occurs we will notify you and the Office of the Australian Information Commissioner under the Notifiable Data Breaches scheme. Complain to us first; if you are not satisfied, to the OAIC.
New Zealand. Under the Privacy Act 2020 you may ask for access to your personal information (IPP 6) and ask us to correct it (IPP 7). IPP 12 allows us to send your information overseas only where comparable safeguards apply; the recipients and what each one receives are in section 10. A privacy breach likely to cause serious harm will be notified to you and to the Office of the Privacy Commissioner. You may complain to us, or to the Privacy Commissioner at privacy.org.nz.
European Economic Area, United Kingdom and Switzerland. AstraVault is available in all 30 EEA states, the UK and Switzerland, so the GDPR and the UK GDPR apply to it. The controller is AstraSoft Labs, reachable for anything on this page at admin@astrasoft.info.
What we do with your data, and what allows us to: running your vault and your account is performance of our contract with you. The security event log, the device-integrity checks and the records we keep to stop abuse rest on our legitimate interest in keeping other people's documents safe; you can object to that, and section 8 says how. Crash reports, error reports, performance traces and usage analytics rest on your consent, which you give or withdraw at any time in Settings → Consent Manager — with one exception stated plainly below. Your advertising ID also rests on your consent.
Ads and your consent choice. AstraVault 1.2.3, the version on Google Play, asks before any ad. Before an ad request can leave your device we put the question to Google's User Messaging Platform — Google's own certified consent platform — and in the European Economic Area, the United Kingdom and Switzerland that means a form you are shown and must answer. Google's Mobile Ads SDK is not started by this app, and no ad is requested, until that answer allows it: if you refuse, if the form cannot be shown, or if the request to Google fails, nothing is requested and the banner space stays blank. Where a form was shown you can change or withdraw your answer under Settings → Ad privacy choices; that row appears only in those regions, because only there is there a recorded choice to change, and withdrawing stops the next ad request rather than removing a banner already on your screen. Outside those regions no form is required, so the consent platform settles without showing you anything, and there is then no in-app ads control — only Android's own. One thing we do not control: a component Google ships inside the ads library starts with the app process, before any of our own code runs, and we have not confirmed what it reads. Versions 1.2.1 and 1.2.2 asked for nothing. On those builds your advertising ID went to Google with no consent behind it — in 1.2.1 on every launch, before any consent screen and whatever your tier, Pro included; in 1.2.2 when the home screen's banner appeared, and on a Pro device too whenever confirming your licence took more than about three and a half seconds, which left the banner in place long enough to start the ads SDK once. That is not what the rules in your region require of us, and we are not going to describe it as anything else. Both builds are still on people's phones until they update, and on them the only control you have is in Android itself: Settings → Privacy → Ads, where you can delete or reset the advertising ID. Pro removes the banner entirely.
Who receives your data, and where. Section 10 lists every recipient and what each one gets. In short: Google (Firebase, Google Play, Google's consent platform for ads and, on the free tier, AdMob), which processes outside the EEA under its own published transfer terms; Sentry, whose servers for this project are inside the European Union; and a server AstraSoft runs itself, opt.astrasoft.info, named in section 10 and in the retention table. Your documents are not in that list — they are encrypted on your phone and stored in your own Google Drive, and we never receive them or the key.
Your rights. You may ask us for a copy of your personal data, have it corrected, have it erased, have our use of it restricted, object to the processing we base on legitimate interests, and receive the data you gave us in a portable form — Access my data produces exactly that, as JSON. Withdrawing consent is as easy as giving it and does not affect what we did before. Nothing about you is decided by automated means. The app is for adults; we do not knowingly process children's data. And you may complain to your own supervisory authority — the ICO in the UK, the FDPIC in Switzerland, or the authority for the country you live in — without going through us first.
Three things differ by version, and if you have not updated they still apply to you. The exception mentioned above is one of them: on 1.2.1, when the app crashes, a record of where it crashed reaches our backend even if you have turned crash reporting off, and it is not redacted — it carries the first 50 characters of the error message as written, so if that text contains your email address or account id, it goes with it. From 1.2.2 that write follows your choice, a choice we cannot read counts as off, and a crash counted before you declined is discarded rather than uploaded on the next launch. The in-app Delete My Account button recorded nothing on 1.2.1 — from 1.2.2 it files a real request. And performance monitoring ignored the analytics switch on 1.2.1; from 1.2.2 it follows it. Whichever version you are on, emailing admin@astrasoft.info works: requests are handled by hand, within 7 days, in any country.
You can ask us to delete your account from Settings → Privacy & Account → Delete My Account, or by emailing admin@astrasoft.info. There is also a web page explaining deletion.
From version 1.2.2 onward the in-app button files a real request. It records your account id, a one-way hash of your account email, the time you asked and a status of PENDING on our backend, and the screen tells you only that: that we review requests by hand, reply to your account email within 7 days, and that nothing has been deleted yet. In version 1.2.1 it did not. That screen announced that a deletion had been scheduled and that your account would be permanently deleted in 30 days, while nothing was recorded and nothing reached us — so if you confirmed deletion on 1.2.1, we never received it. Version 1.2.1 is no longer on Google Play: if you are still running it, update the app and submit again, or email admin@astrasoft.info from your account address.
However you reach us, submitting a request does not delete anything by itself. We review and process deletions by hand and reply to your account email within 7 days. Nothing is removed automatically, nothing happens at the moment you confirm, and there is no automatic countdown. To cancel a request, email us.
Until we process it, your vault stays on your phone, your keys stay on your phone, and your account records stay on our backend. Your encrypted documents are in your own Google Drive and remain there until you delete them or ask your Google Account to remove AstraVault's access — the app's own deletion flow does not touch your Drive. Section 6 and the deletion page explain how to remove both the visible folder and the hidden app folder.
Up to version 1.2.1 the app's own text described a 30-day automatic deletion with a cancellation window. That was wrong in every part — there is no countdown, no cancellation window and no automatic deletion. The wording and the missing record were both fixed in 1.2.2: the screen now says only that your request has been recorded, that we review requests by hand and reply within 7 days, and that nothing has been deleted yet. This page remains the authority if your copy says otherwise.
AstraVault uses the services below, and this list covers every service that receives data in version 1.2.3, the version now on Google Play. It is complete for 1.2.2 as well. Version 1.2.1, which some phones are still running, sends nothing to the AstraSoft server listed below Sentry; the rest of the list applies to it too. Where a row describes behaviour that a later version changed, the row names the version it is describing. Each provider's own privacy policy governs its handling of the data it receives.
| Service | Purpose | Data it receives |
|---|---|---|
| Google Firebase Auth | Sign-in with your Google account | Your Google account email and account id |
| Google Firestore | Profile, consent, security and sync records, compliance records | Everything marked "our Firebase backend" in section 3 |
| Firebase Crashlytics | Crash reporting | Stack traces, device model, OS and app version, recent app log lines and a few technical flags such as whether the vault was unlocked. Your documents' contents are never included — no file, no page image, no text from inside a document. We do not deliberately send document names either, but we will not promise they never appear: if something goes wrong while the app is preparing a document to share or export, the error carries the name of the working file, which is made from the document's name, and crash reports sent to Crashlytics are not scrubbed |
| Sentry (servers in the European Union) | Error and crash monitoring, and a 5% sample of performance traces | Stack traces, error messages, breadcrumb trails, device and app details, and a one-way hash of your account id. In 1.2.1 only the user record attached to a report was stripped of your email address — the error messages and breadcrumb trails themselves were not filtered, so a log line containing your email address could reach Sentry. In 1.2.2 and 1.2.3 the report's message, every breadcrumb and every exception message are scrubbed of email addresses and account identifiers before anything leaves your phone, and the user record carries no email address or username. Nothing is sent unless you have turned crash and error reporting on; if you turn it off, reports already waiting to be sent are still sent as the monitoring SDK shuts down. One limit we will not dress up: the scrubbing matches patterns, so a document name that appears inside an error message — for example in the path of a failure while preparing a document to share — is not removed. Performance samples are not scrubbed and contain screen and operation names only |
AstraSoft's own error server (opt.astrasoft.info) |
A second copy of the same monitoring data Sentry receives, on a server we run ourselves rather than rent from a monitoring company | A copy of the reports the app sends to Sentry: crash and error reports (stack traces, exception text, breadcrumb trails, device and app details, and the same one-way hash of your account id), the app-start and app-close records used to count crash-free launches, and the same 5% sample of performance traces. The same scrubbing is applied before anything leaves your phone — error messages, breadcrumbs and exception text have email addresses and account identifiers blanked out; performance traces are not scrubbed. No document file is ever attached, and screenshots and screen contents are switched off. Nothing is sent unless you have turned crash and error reporting on: with it off the monitoring SDK is never started, and this server receives nothing at all. The short crash record described in sections 8 and 14, which on 1.2.1 reached our Firebase backend whether or not you agreed to crash reporting, is a different thing and does not go here. There is no retry and nothing is saved to disk to wait for a connection, so a copy that cannot be sent at that moment is dropped and never arrives — that includes a device that is offline, several crashes arriving at once, and an unusually large report. Not in version 1.2.1, which sends nothing here. The server runs on infrastructure AstraSoft rents; Sentry has no part in it |
| Firebase Analytics | Feature usage | Event names and parameters, the install referrer, and the pseudonymous installation identifier. No email address, no document names or content |
| Firebase Performance Monitoring | App speed and startup measurement | Screen, database and network timings, not filtered for personal information. From 1.2.2 it follows your usage-analytics choice: collection is switched off in the app until you turn analytics on, and turning analytics off stops it again within the same session. In 1.2.1 it kept collecting whatever you chose |
| Firebase Remote Config | Feature settings and pricing, fetched each time the app starts | Installation identifier and device details. This runs on launch, before you make any consent choice |
| Firebase Cloud Messaging | Push notifications | Your notification token |
| Firebase email delivery | Sending you account emails | Your email address and the message body |
| Google Play Integrity (App Check) | Letting our backend reject requests that do not come from the genuine app | A device attestation token |
| Google Drive API | Document and working-file storage in your own Drive | Encrypted documents and backups; unencrypted category folder names, file identifiers, the deleted-document list and crash files. AstraSoft cannot decrypt your documents |
| Google ML Kit — text recognition and document scanner | On-device text recognition (English and Hindi), and the camera scanning flow | The document scanner is a Google Play services component that receives the live camera view and writes the finished scan to your device. Text recognition runs on-device; nothing is sent to Google |
| Google Play Install Referrer | How you found the app | The Play Store referral text, passed on to Firebase Analytics |
| Google Play Billing | Pro upgrade purchase | Handled by Google Play; AstraSoft receives only a purchase confirmation |
| Google Play In-App Review | Asking you to rate the app | Your rating, sent to Google Play |
| Google Play In-App Update | Offering you a newer version | Asks Google Play whether a newer version of the app exists |
| Google User Messaging Platform (Google's own consent platform) | Asking for your choice about personalised ads, recording it, and giving you a way back in to change it | Google is contacted to find out whether a consent form has to be shown to you — it works that out from your internet address — and your answer is stored by Google, not by us. This happens before the first ad is requested on the home screen, and again each time you open Settings, so the "Ad privacy choices" entry can be shown wherever it is required. This step reads no advertising ID and starts no ads SDK. It is in 1.2.3 only; 1.2.1 and 1.2.2 contacted no consent platform |
| Google Mobile Ads (AdMob) | Banner ads on the Free tier and optional rewarded ads | Your device's advertising ID, once an ad is actually requested. In 1.2.3 Google's ads SDK is not started, and no ad is requested, until Google's consent platform has answered: in the European Economic Area, the United Kingdom and Switzerland that means a form you are shown and must answer, and if you refuse — or if the form cannot be shown at all — nothing is requested. Everywhere else the answer settles without showing you anything. The only place the SDK starts is the Free-tier home-screen banner, so a Pro device normally never starts it and never reads the advertising ID. Where the form applies you can change or withdraw your answer under Settings → Ad privacy choices. The Free tier banner itself cannot be switched off except by upgrading to Pro; rewarded ads are always your choice. In 1.2.1 the ads SDK started on every launch, before any consent choice and whatever your tier, Pro included; in 1.2.2 it started from the banner screen but asked nothing first |
SQLCipher, PDFBox, Tink and the other libraries AstraVault is built from run only on your device and send nothing anywhere. AstraVault does not ask for a location permission, so no part of it can read your precise location. Google's ads SDK still sees your device's internet address when it fetches an ad, which gives it a rough idea of your area.
Google Privacy Policy · Firebase Privacy · Sentry Privacy Policy
| Data | How long it is kept |
|---|---|
| Encrypted documents in your Drive | Until you delete them, with one exception: AstraVault can permanently delete a file from your Drive when that file has no matching record in the vault on your phone. That sweep can be started remotely by an AstraSoft administrator during a background sync, without asking you. If your local vault has just been rebuilt and your documents have not been restored yet, they can be caught by it |
| The encrypted database on your device | Until you uninstall AstraVault or clear its data in Android settings. It is also rebuilt from scratch, losing the local copy, if the vault cannot be unlocked, if an app update changes the database format, or if you trigger a remote wipe after losing your phone. Your documents stay in your Drive and are re-synced when you sign in again |
| Your profile, email lookup record, security log, sync diagnostics, sync summary and compliance records on our backend | Until we process a deletion request from you |
| Consent records | We aim to keep these for 5 years to meet our compliance obligations. They are written once and removed only when we act on a deletion request, so they may remain longer than that until we do |
| Firebase Crashlytics data | 90 days, under Google's Crashlytics retention policy — set by Google, not by us |
| Firebase Analytics data | The period set in our Google Analytics configuration. Write to us and we will tell you the figure currently in force |
| Error reports held by Sentry | Sentry's retention for our plan. We are confirming the exact period and will state it here; write to us in the meantime |
The copy of error reports on AstraSoft's own server (opt.astrasoft.info) | That server is set up to delete crash and error reports, and the app-start records that go with them, no more than 90 days after the event they describe, and performance traces no more than 30 days after; they can go sooner if the server is short of space. Counts of how often a given fault happened — a fault signature, the app version and a number, with no report text, no device and nothing about you — are kept for up to 13 months. One summary record of each fault is kept indefinitely, in a separate database the deletion job cannot reach: the fault's signature, the place in our code it came from, when it was first and last seen, and which app versions it appeared in. That record holds no report text, no device details and nothing that identifies you. We are telling you how the server is set up, not certifying it: this has not been independently audited, and if you need it confirmed in writing, write to us |
| Crash files in your own Drive app folder | Until you delete the app folder or remove AstraVault's access from your Google Account |
AstraVault is for adults. Before you can use it you must confirm on screen that you are 18 or older, and we record that confirmation. We do not verify age and we do not collect parental consent, so we rely on what you confirm. If you believe someone under 18 is using an account, contact us at admin@astrasoft.info and we will delete it.
This list has now shipped in full. The earlier items arrived in 1.2.2 and the last one — the consent form for ads — in 1.2.3, which is the only version on Google Play today; 1.2.1 and 1.2.2 are no longer published, and a device keeps the version it has until you update, so the app on your phone may still behave as the rest of this page describes rather than as this list does. We keep the list here so you can see the difference between the app you have and the app you will get.
opt.astrasoft.info), alongside Sentry, under the same crash-reporting choice. This has been true since 1.2.2; section 10 lists what that server receives and section 11 how long it keeps it.Two things these changes do not fix, and we are not going to imply otherwise: the security event log still has no opt-out, and deletion is still processed by hand.
If we change this policy we will publish the new version on this page with a new "Last updated" date, and update the policy text inside the app in its next release. AstraVault does not currently send a push notification or show a message in the app when the policy changes, so please check this page if you want to know whether anything has changed. Your continued use of AstraVault after a change takes effect constitutes acceptance of the revised policy.
To exercise your data rights, request deletion, raise a grievance or ask any privacy question: