Privacy Policy

At a glance

• No DriveNest servers, accounts or cloud storage. DriveNest has no backend of its own. The App works on your device and talks directly to Google or Microsoft — and, only if you turn on the AI assistant, to Anthropic or OpenAI (Section 1.7).
• Your data stays on your device. What the App reads from your cloud account — your account details, file and folder metadata, sharing information — and everything it produces from it (scans, reports, preferences, history) is processed and kept on your device, or placed in your own Google account when you deploy a cleanup script. We never receive your scans, your files, your sign-in tokens or your account details.
• What reaches us. Only what you choose to send us: feedback you submit from the App (Section 1.6), a diagnostic log you send to support (Section 1.9), and any email you write to us. In addition, Google Play gives us records of the purchases made in the App (Section 1.5).
• The website is separate from the App and is covered in Section 9.

1. Information the App Handles

Sections 1.1 to 1.5, 1.7 and 1.8 describe information the App handles on your device, or exchanges with your own provider accounts; none of it is sent to us. Sections 1.6 and 1.9 describe the only information from the App that reaches us, and only when you choose to send it.

1.1 Account Information

When you sign in — with a Google account (for Google Drive) or a personal Microsoft account (for OneDrive) — the App receives the following from the provider's authentication service and keeps it on your device:

• Email address — used to identify your account within the App.
• Display name — shown in the user interface for personalization.
• Profile photo — downloaded from your account to show in the App, and cached as an image file in the App’s private storage on your device (refreshed about once a day).
• Sign-in credentials (OAuth tokens) — used to communicate with the provider's API (the Google Drive API or Microsoft Graph) on your behalf, and sent only to the provider that issued them. How they are kept differs by provider:
  • Google — your Google sign-in is kept by Google Play services on your device, not by the App, which is why it comes back after a restart. The App asks Google Play services for a short-lived access token when it needs one and holds that token in memory only.
  • Microsoft — the access token, the refresh token, and your email address, name and profile-photo address are saved in Android’s encrypted secure storage on your device. This keeps you signed in after a restart (the offline_access permission in Section 1.2 exists for this) and lets scheduled scans run while the App is closed (Section 1.8). They are deleted when you sign out of OneDrive in the App, or when you uninstall it.

1.2 Cloud Storage Metadata

DriveNest builds its analysis from metadata only — it never accesses the contents of your files on any provider. What it requests depends on the cloud you connect:

• Google Drive — the App requests the drive.metadata.readonly OAuth scope, which grants read-only access to file and folder metadata. Only if you deploy a cleanup script from the App, or turn on auto-cleanup (Section 1.8), does it also request the script.projects scope. With it, the App creates and updates Google Apps Script projects in your own Google account through the Apps Script API; that is where the cleanup script you then review and run is placed. This scope does not give the App access to the contents of your files.
• OneDrive (supported since DriveNest v2) — the App connects through the Microsoft Graph API. At sign-in it requests three read-level permissions only: Files.Read (your OneDrive item metadata), User.Read (your basic profile), and offline_access (so your session can refresh without repeated sign-ins). The write permission Files.ReadWrite is not requested at sign-in — it is requested separately, through incremental consent, only at the point you first ask the App to carry out an action on your behalf, and only after the App has explained what it is asking for (see Section 2). If you never use in-app execution, the App never holds write access to your OneDrive.

The metadata the App retrieves includes:

• File and folder names, IDs, types, and parent folder relationships.
• File sizes, creation dates, modification dates, and last-viewed dates.
• Content hashes where the provider supplies them (used locally for duplicate detection).
• Sharing status and permissions, including the names and email addresses of the people and groups each item is shared with (used for the security audit features). These identities stay on your device, in your scans, and are never sent to the AI assistant (Section 1.7).
• Whether an item is trashed and whether you are the owner.
• Your storage quota.

1.3 Locally Stored Preferences

The App stores your preferences on your device, including:

• Color theme and dark/light mode selection.
• Dashboard layout and tab order customization.
• Auto-save and auto-load scan settings.
• Whether the guided tour has been completed.

These preferences are stored on your device using the platform's standard local preferences mechanism. Some of them are kept per account and are therefore stored under your account email address — for example which permissions you have granted for which account, and records of where each account’s saved scans are kept. They never leave your device unless you export your settings yourself (Section 5).

1.4 Saved Scan Data

When you run a scan, the resulting metadata snapshot may be saved as a compressed file on your device's local application storage, in a folder for each account that is named after the account’s email address. Saved scans contain the folder tree structure and file metadata described in Section 1.2 — including the names and email addresses of the people and groups your items are shared with — along with a unique scan identifier and timestamp.

1.5 In-App Purchase Information

The App offers optional in-app purchases (Premium and Ultimate tiers) processed entirely by the Google Play Store. The App receives from Google Play only the purchase status (purchased, pending, or restored) and the product identifier, to unlock the features of your plan.

As the developer, we receive the records of these purchases from Google Play (for example the order number, the product, the price and the country), which we use for refunds, support and accounting. They come from Google, not from the App.

1.6 Voluntary Feedback Data

The App includes an optional feedback form that lets you submit a price proposal or a feature request. Submitting feedback is entirely voluntary. When you choose to submit, the following information is collected and transmitted to a developer-controlled Google Sheet via Google Apps Script:

• Anonymous device fingerprint — a randomly generated UUID created on first launch and stored on your device. It is not linked to your Google account, name, or email address, and is used solely to enforce a per-device daily submission limit. No submitted feedback is ever associated with your Google account or any other account-identifying information.
• Billing country — the country associated with your Google Play account (e.g. “HU”), retrieved from the Play Store billing configuration.
• Device locale — your device’s language and region setting (e.g. “hu_HU”).
• App version — the version of DriveNest installed on your device.
• Subscription tier — your current plan (Free, Premium, or Ultimate).
• Price proposal details (price proposals only) — the plan tier, currency, and suggested price you enter.
• Feature description (feature requests only) — the free-text description you write.

1.7 Optional AI Assistant

From DriveNest 2.1, the Ultimate plan includes an optional AI assistant that explores your latest scan and suggests what to clean up. It is off by default. Nothing in this section happens unless you turn it on in Settings, accept its terms, and add your own API key from Anthropic (Claude) or OpenAI (GPT). When you run an analysis or ask a follow-up question:

• What is sent — the parts of your scan metadata the assistant examines while it works: file and folder names, paths, sizes, types, dates, whether you own an item, its sharing status (whether it is shared, how many permissions it has, whether it has a public link), duplicate groups and version-history overhead. The goal and follow-up messages you type are sent as well.
• What is never sent — the contents of any file, your sign-in tokens, your email address, and the identities of the people you share files with.
• Where it goes — directly from your device to the provider you chose, over HTTPS, using your own API key. DriveNest has no server in between and never receives this data. The provider processes it under its own terms and privacy policy (Anthropic, OpenAI), and usage is billed by the provider to your own account. How long the provider retains API data is governed by its policies; for OpenAI, DriveNest asks the API not to store the conversation.
• Your API keys — kept only in Android’s secure keystore on your device, never in normal app storage, and never included in a DriveNest settings backup. Turning the assistant off, or declining its terms, permanently deletes every saved key.
• Session record — each session is written to Action history on your device: the provider and model, number of runs, tokens used, estimated cost, the messages you sent, and each suggestion with the files it covered. The assistant’s own replies are not logged. This record stays on your device.

1.8 Scheduled Scans and Auto-Cleanup

Both are off by default and run only after you turn them on in Settings.

• Scheduled scans — the App scans your Google Drive or OneDrive in the background at the interval you choose, while the App is closed, using the sign-in described in Section 1.1. A scheduled scan reads the same metadata as a scan you start yourself (Section 1.2) and saves the result on your device (Section 1.4).
• Auto-cleanup (Google Drive) — after each scheduled scan, the App updates the cleanup script in the Apps Script project in your own Google account (Section 1.2). This uploads the IDs and names of the files selected by your cleanup rules into that project. The App only deploys the script; it never runs it. Nothing happens to your files until you run the script yourself.

1.9 Support Diagnostic Log

DriveNest contains a diagnostic log intended solely for troubleshooting with our support team. It is not part of normal use: it is off by default, is not offered among the regular settings, and is meant to be turned on only when you have contacted support and we specifically ask you to, following the steps we give you. While it is on, the App writes a technical log — app and scan events, including the email addresses of your signed-in accounts — to a file named drivenest_diag_….log in your device’s public Downloads folder, so that you can find it and send it to us. Please note:

• It stays on, including across restarts, until you turn it off again the way we describe.
• The file is outside the App’s private storage: other apps that can read your Downloads folder can read it.
• It is not deleted when you turn the log off or uninstall the App. Delete it yourself from the Downloads folder once your support case is closed.
• It is never sent anywhere automatically; it reaches us only if you send it to us.

2. How Your Information Is Used

The App uses the information described above on your device, and we use what reaches us (Sections 1.5, 1.6 and 1.9), solely to:

• Authenticate you with your chosen provider (Google or Microsoft) and communicate with its API (the Google Drive API or Microsoft Graph).
• Display your storage breakdown, folder hierarchy, and file statistics.
• Detect duplicate files by comparing content hashes locally on your device.
• Generate cleanup suggestions based on file age, size, and usage patterns.
• Carry out the cleanup, unshare, and version actions you explicitly approve — on Google Drive as a script you review and run yourself, and on OneDrive by executing the approved action in the app on your confirmation. DriveNest never performs these actions automatically or without your explicit approval.
• Perform a security audit of sharing permissions across your storage.
• Produce PDF and CSV reports when you explicitly request an export.
• Save and restore scan snapshots so you can track storage trends over time.
• Remember your display preferences across app sessions.
• If you turn them on, run scheduled scans in the background and keep the cleanup script in your own Google account up to date (Section 1.8).
• If our support team asks you to turn it on, write the diagnostic log you can send us for troubleshooting (Section 1.9).
• Verify your in-app purchase tier to unlock the appropriate features.
• Review voluntary price proposals and feature requests to inform pricing decisions and product development priorities.
• If you turn on the optional AI assistant, send the scan metadata it examines and the messages you type to the AI provider you chose, so it can propose cleanup suggestions for your review (see Section 1.7).

3. Data Storage and Security

3.1 On-Device Storage

Scan data, preferences, and exports are stored locally on your device in the App's private application directory. The one exception is the support diagnostic log, if support has asked you to turn it on, which is written to your public Downloads folder (Section 1.9).

No scan data is transmitted to any external server, with two exceptions, both of which you turn on yourself:

• If you use the optional AI assistant, the scan metadata it examines is sent to the AI provider you chose (Section 1.7).
• When you deploy a cleanup script — yourself, or through auto-cleanup after scheduled scans — the IDs and names of the files it covers are uploaded into an Apps Script project in your own Google account (Sections 1.2 and 1.8). We never receive them.

3.2 Encrypted Backups

When you export a scan backup, the data is bundled into a ZIP archive and encrypted using AES-256 (CBC mode) before being saved. You control where the encrypted backup file is shared or stored via the operating system's share functionality.

3.3 Network Security

All communication with provider APIs (Google and Microsoft) and, if you use the AI assistant, with the Anthropic or OpenAI API is conducted over HTTPS (TLS-encrypted connections). OAuth tokens are transmitted only to the provider that issued them. Google access tokens are held in memory; the Microsoft tokens are kept in Android’s encrypted secure storage so you stay signed in (Section 1.1).

4. Data Sharing and Disclosure

The App communicates exclusively with the following external services:

• Google Drive API — to retrieve your Drive metadata using your OAuth token. Google's use of your data is governed by Google's Privacy Policy.
• Microsoft Graph API — when you connect OneDrive (supported since DriveNest v2), to authenticate you with your Microsoft account, read your OneDrive metadata, and carry out the in-app actions you approve. Microsoft's use of your data is governed by the Microsoft Privacy Statement.
• Google Apps Script API — when you deploy a cleanup script, or auto-cleanup does so after a scheduled scan, to create and update the Apps Script project holding that script in your own Google account (Sections 1.2 and 1.8).
• Google Play Billing — to process in-app purchases. Payment data is handled entirely by Google and is subject to Google's terms.
• Google Play in-app updates and in-app reviews — to offer an update when a new version is available, and occasionally to show Google Play’s rating prompt. Both are provided by Google Play; we do not receive anything you write in a review through the App.
• Google Apps Script / Google Sheets — when you voluntarily submit a price proposal or feature request, the data described in Section 1.6 is transmitted over HTTPS to a Google Apps Script web app and stored in a Google Sheet controlled by the developer. This communication occurs only when you explicitly tap Submit in the feedback form. The data is used solely by the developer and is never shared with third parties.
• Anthropic API or OpenAI API — only if you turn on the optional AI assistant and add an API key for that provider, to send the scan metadata and messages described in Section 1.7. The provider’s use of this data is governed by your agreement with it and by its privacy policy (Anthropic, OpenAI).

The App does not include any third-party analytics, advertising, crash reporting, or tracking SDKs. Nothing is collected in the background unless you turn on scheduled scans (Section 1.8), and no data is shared with any party other than as described above.

5. User-Initiated Exports and Sharing

You may choose to export data from the App in the following formats:

• CSV files — containing file metadata (names, paths, sizes, dates, sharing status) for specific views such as duplicates, cleanup targets, or security findings.
• PDF reports — containing charts, statistics, and summaries of your storage analysis.
• Encrypted scan backups (.dnbak files) — containing your full scan snapshot, AES-256 encrypted.
• Settings export (a .json file) — your App settings, so you can import them again on this or another device. It is not encrypted, and settings kept per account can include your account email addresses. It never contains your sign-in tokens or AI API keys, which are kept in secure storage.

The support diagnostic log (Section 1.9), if you turned it on for a support case, is a separate file in your Downloads folder that you send us yourself.

Exports are shared via the operating system's share sheet. You are responsible for choosing where exported files are stored or sent. The App does not automatically upload exports to any service.

6. Data Retention and Deletion

• In-memory session data (including Google access tokens) is discarded when you close the App.
• Sign-in — your Google sign-in is kept by Google Play services until you sign out; the Microsoft tokens and profile details in secure storage are kept until you sign out of OneDrive in the App or uninstall it.
• Cleanup scripts deployed to your Google account stay in your Apps Script projects until you delete them there (at script.google.com).
• The support diagnostic log, if you turned it on for a support case, stays in your Downloads folder until you delete it, including after you uninstall the App.
• Saved scans are retained on your device until you manually delete them via the Saved Scans manager in Settings, or until you uninstall the App.
• Preferences are retained until you reset them in Settings or uninstall the App.
• AI API keys are retained until you remove them, turn the AI assistant off, decline its terms, or uninstall the App.
• Action history, including AI assistant session records, is kept on your device for up to one year and then removed automatically, or earlier if you uninstall the App.
• Data sent to an AI provider is retained by that provider according to its own policies, not by DriveNest.
• Signing out clears your authentication state immediately. Saved scans and preferences remain on-device for your convenience but can be deleted at any time.
• Uninstalling the App removes everything it keeps in its private storage, including saved scans, preferences, the cached profile photo, secure-storage entries, and any temporary export files. It does not remove the diagnostic log in your Downloads folder, files you exported or shared elsewhere, or cleanup scripts in your Google account.

7. Children's Privacy

DriveNest is not directed at children under 13. We do not knowingly collect personal information from children. The App requires a Google or Microsoft account to function, and account creation is subject to the age requirements of Google or Microsoft respectively. Users must meet the minimum age requirement in their country to create and use such an account.

8. Your Rights and Choices

• Access: All data the App holds is visible to you within the App itself (scan results, saved scans, preferences).
• Information you sent us: For feedback, a diagnostic log or an email you sent us (Sections 1.6 and 1.9), contact us at drivenestapp@gmail.com for access or erasure. Feedback is not linked to your account, so we can help only where we are able to locate it.
• Deletion: You can delete saved scans, reset preferences, and sign out at any time. Uninstalling the App removes all data in its private storage; delete a diagnostic log from your Downloads folder, and cleanup scripts from your Google account, yourself (Section 6).
• Revoke access: You can revoke DriveNest's access at any time — for Google via your Google Account permissions page, and for Microsoft via your Microsoft account app permissions page.
• AI assistant: The assistant stays off unless you turn it on. You can turn it off, remove a saved API key, or decline its terms at any time in Settings; turning it off or declining deletes every saved key. For data already sent to Anthropic or OpenAI, use that provider’s own privacy controls.
• Portability: You can export your scan data as CSV, PDF, or encrypted backup files, and your settings as a JSON file, at any time.
• Background activity: Scheduled scans and auto-cleanup stay off unless you turn them on, and you can turn each off again in Settings. The support diagnostic log stays off unless support asks you to turn it on (Section 1.9).

9. Website

This section covers the website at drivenest.falcondrivelabs.com (the pages served under falcondrivelabs.com) and is separate from the in-app data practices described in the preceding sections.

9.1 No cookies, no tracking

The one script not written by us is a small performance-measurement script that our hosting provider, Netlify, adds to each page. It measures how quickly the page loads and responds, and sends those timings to Netlify together with the page address, your device’s operating-system family and screen size. It uses no cookies, stores nothing in your browser, and uses no identifier that links one page view or visit to another. (A private, password-protected page used only by the site owner keeps its sign-in and display settings in that browser; no visitor uses it. The owner’s own browsers also carry a marker set by that page, so that the owner’s visits to the website can be reported and left out of the visit statistics. Visitors’ browsers carry no such marker and send nothing.)

9.2 Hosting logs and visit statistics

Our hosting provider, Netlify, processes standard server-log information — such as your IP address, the page requested, the referring site and the time of the request — as a normal part of operating and securing the website. From these logs Netlify provides us with aggregated visit statistics: numbers of page views and unique visitors, page-load timings (from the script described in 9.1), and counts per page, per referring site and per country. We keep these aggregated statistics to understand how the website is used and to improve it. To tell visits by people from automated traffic, we also keep Netlify’s log of individual requests — time, address requested, response status and speed — for up to two days before condensing it into the same kind of aggregated statistics. Neither contains IP addresses or anything else that identifies an individual visitor. The legal basis is our legitimate interest (Article 6(1)(f) GDPR) in operating and improving the website. Netlify’s processing is governed by the Netlify Privacy Statement.

9.3 Google Play link clicks

Links to DriveNest on Google Play pass through the website, which adds one to a daily count for that link before forwarding you to the store. Only the count is stored — no IP address, cookie, or other information about you. The link to Google Play carries a label naming the website and the page you came from, so that Google Play can report how many store visits and installs came from the website. Your visit to Google Play is governed by Google’s Privacy Policy.

9.4 Videos and links to other services

Some pages of the website show demonstration videos hosted on YouTube. Until you press play, the page shows only a preview image served from our own website, and nothing is loaded from YouTube. When you press play, the video is loaded from YouTube (Google) in its privacy-enhanced mode (youtube-nocookie.com). From that moment YouTube receives your IP address and information about your device and viewing, and may store data in your browser; this is governed by Google’s Privacy Policy. Each video can also be opened on YouTube itself instead.

The website also links to other services, such as Google Play and YouTube. When you follow such a link, that service’s own privacy policy applies.

9.5 Past promotional campaign

Until 30 June 2026 we ran a limited promotional campaign on the website through which a one-time promotional code could be issued to you. When a code was issued, we recorded an approximate geographic location — country, and where available region and city — derived from your IP address by our hosting provider at that moment, together with a randomly generated visit identifier and the code issued. We did not store your IP address, name, email address, or any Google account information in connection with the code.

This data is used solely for internal, aggregate statistics on the campaign’s geographic reach, on the basis of our legitimate interest (Article 6(1)(f) GDPR) in measuring our promotional activities. It is never used to build a profile of you, to make any automated decision about you, or for advertising. It never leaves our own hosting backend, is not shared with any third party, and is accessible only to the developer over an authenticated connection.

Promotional-code records are retained only for as long as needed to evaluate the campaign, after which they are deleted. The location is linked only to a random visit identifier, not to your name, email, or account, so we generally cannot single you out from it. You may nonetheless contact us at drivenestapp@gmail.com with any question or request regarding this data — including access or erasure — and we will assist wherever we are reasonably able to locate the relevant record. Under the GDPR you also have the right to object to processing carried out on the basis of legitimate interest.

9.6 Halloween promotion (1–7 November 2026)

Until 7 November 2026, small animated Halloween characters fly across the website’s pages. When you click one, the website asks our server whether the click wins a Google Play promotional code for DriveNest Ultimate. If it does, the code is shown to you, and it is also kept in your browser’s local storage until 7 November so you can find it again; nothing else is stored in your browser.

So that each person can win only one code, our server keeps a one-way, keyed fingerprint of the IP address that received a code. The IP address itself is not stored and cannot be recovered from the fingerprint. We also record which codes were handed out and when, and count clicks per day, without linking either to you. The fingerprints are deleted automatically one week after the promotion ends. The legal basis is our legitimate interest (Article 6(1)(f) GDPR) in running the promotion fairly. Redeeming a code happens on Google Play and is governed by Google’s Privacy Policy and Google Play’s terms. The characters do not appear if your device is set to reduce motion.

10. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be reflected by an updated effective date at the top of this document. We encourage you to review this policy periodically. Continued use of the App after changes constitutes acceptance of the revised policy.