Privacy Policy — Secure Recorder

Last updated: October 3, 2026

1. Data Controller

Secure Recorder is an Android application provided by Damian Nass under the nas4.tech brand, with package identifier com.nas4tech.securerecorder. Damian Nass is the data controller for personal data processed under the developer's responsibility. For privacy enquiries, contact contact@nas4.tech.

This policy covers the application, its optional cloud connections, model downloads, sharing features and advertising. Connected services and apps may also process data under their own privacy policies. This policy describes the app; the privacy policy for the nas4.tech website applies separately to visits to this website.

2. Core Principle

Secure Recorder processes recordings and transcription locally on your device. The recording and transcription features do not send your audio or transcripts to the developer's servers. This does not mean that the app never connects to the internet: advertising, consent management, model downloads and cloud connections involve external services.

You control whether to connect a cloud destination and which recordings or text to share. Once you enable a cloud destination and automatic upload options, uploads can occur without a separate confirmation for every file or periodic copy.

3. What Data Is Processed

3.1 Audio Recordings and Background Operation

The app uses microphone access to record audio following your action or activation of a configured recording or listening mode. Supported external microphones may include Bluetooth, wired and USB devices, depending on your device and Android version.

Recording can continue in the background, including while you use another app or lock your device, with an ongoing foreground-service notification. Enabled voice or sound triggers can require microphone listening to detect the configured trigger. Disable the corresponding mode or stop the active recording when you no longer want that microphone use.

Optional system audio capture uses Android's MediaProjection and audio playback capture mechanisms. It requires permission through the Android capture dialog and support from the source application. This feature captures audio; it does not record screen video.

Recordings are saved on your device. Local recordings are not encrypted by the app's optional AES upload feature. Record only when you have the necessary permissions and consent from the people concerned.

3.2 Offline Transcription and Model Downloads

Whisper converts recorded speech to text on your device after you download or import a suitable model. This transcription workflow does not send your audio to the developer or to a remote transcription service. Transcripts are stored locally unless you choose to export or share them.

Downloading a model requires an internet connection and storage space. Whisper model download sources include Hugging Face and hf-mirror.com. Vosk models used for voice-command or voice-trigger features are downloaded from alphacephei.com. The relevant hosting service receives your IP address and ordinary request information when you download files. A local import does not require downloading that model through the app.

Transcription may create temporary audio files. If processing is interrupted, for example by an app crash, temporary copies may remain on the device. Processing speed and accuracy depend on the device, model, language and recording quality.

3.3 Optional Cloud Backup and Backup During Recording

You may connect Google Drive, Microsoft OneDrive, Dropbox or a WebDAV server. These integrations send authentication and API requests, recordings and the file information needed to operate the integration to the selected provider. Authentication tokens and connection credentials are stored using the platform's secure storage mechanism.

The permissions differ between providers. Google Drive uses the drive.file scope for files used with the app. OneDrive uses Files.ReadWrite and offline_access; this is not limited to an app-only folder. Dropbox access depends on the app's configured permissions and the authorisation granted. Review the provider's authorisation screen before connecting an account. We do not describe all integrations as having “app files only” access.

The selected provider handles account information during sign-in and may record your IP address and request details. Secure Recorder makes account or drive-information requests to check that the connection works; the audited code does not persist the profile fields returned by those checks. Authentication tokens, file identifiers and metadata needed for synchronisation are handled separately. The provider's policies govern its own processing and storage. Secure Recorder does not create a separate app account; cloud sign-in uses your existing provider account.

A cloud connection is optional. Once a destination is connected and enabled, configured uploads may run automatically. The backup-during-recording option periodically uploads copies of the current audio file, approximately every 20 seconds in the audited version. It is not a continuous stream and does not guarantee protection against data loss. Network failures, destination errors and interruption of the app can leave incomplete remote copies.

Backup-during-recording and cellular-upload options can already be enabled in the app's settings. Review those settings before enabling a cloud destination; cloud backup is not universally disabled by default. Cellular uploads may consume your mobile data allowance.

Disconnecting a cloud destination removes its locally stored connection credentials but does not delete files already uploaded there. An upload or transcription task may be interrupted if Android terminates the app process; completion after process termination is not guaranteed.

3.4 PIN, Encryption and Connection Security

An optional PIN restricts access to the app interface. It does not encrypt local recordings or transcripts.

Optional AES-256-GCM encryption is disabled by default and applies to completed recordings sent through the final upload workflow when you enable it. It does not encrypt local recordings, transcripts, public copies or periodic copies uploaded during recording. Keep your encryption key safe. Losing it can make encrypted recordings inaccessible.

Google Drive, OneDrive and Dropbox integrations use HTTPS. In this release, WebDAV connections require HTTPS and normal certificate validation. HTTP connections and connections configured to bypass certificate validation are not allowed. Transfers for older incompatible configurations are blocked until you update the configuration; stored settings are not automatically deleted. The WebDAV client does not follow redirects and rejects remote file addresses pointing to a different server. Transport protection does not encrypt files after they arrive at the destination.

3.5 Advertising and Privacy Choices

The app displays advertisements using Google AdMob and uses Google's User Messaging Platform (UMP) to manage applicable privacy choices. Depending on the SDK version, settings and your choices, advertising services process data such as your IP address, approximate location inferred from that address, Advertising ID and other device or account identifiers, interactions with the app or ads, and diagnostic information. Purposes include delivering and measuring advertising, analytics, security and fraud prevention.

For users in the European Economic Area, the United Kingdom and Switzerland, the app uses Google's consent flow where required. Other privacy messages and choices depend on the applicable region and the configured advertising services. When the app makes advertising privacy options available in its settings, you can reopen them to review or change your choices.

Declining personalised advertising does not necessarily stop every form of advertising-related processing. You can also use Android's settings to reset or delete your Advertising ID; this does not necessarily disable other identifiers or technical data processing.

Secure Recorder uses Google AdMob only as its advertising platform. The developer has not integrated additional advertising networks through AdMob Mediation. Google's advertising ecosystem and its processing are described in the Google privacy links below and, where applicable, in the consent message.

For Google's practices, see Google's Privacy Policy and Google's advertising privacy information. Advertising processing is separate from local audio transcription.

3.6 Location

The app does not request Android location permissions or use GPS to obtain your precise location. However, advertising and other internet services can infer an approximate location from your IP address. The absence of a location permission does not mean that no location-related information is processed.

3.7 Sharing, Exports and Contact Data

If you use Android's sharing tools or export a file, the selected app, storage destination or recipient receives the recording, transcript or other content you choose. Copies outside Secure Recorder are subject to that recipient's settings and privacy practices and are not protected by the app's PIN.

The “Contact Developer” feature opens your email client with contact@nas4.tech as the recipient. We receive the email address, message, attachments and other information you send. This information is used to respond to your enquiry and handle related support or privacy requests. Do not send recordings or other sensitive information unless needed for your request.

3.8 System Permissions and Controls

Microphone: recording audio and listening for enabled voice or sound triggers.
Foreground services: maintaining active microphone or system-audio capture while the app is in the background.
Notifications: displaying recording status and controls. Notification behaviour depends on Android version and your notification settings; a foreground service still has notification obligations when notification permission is denied.
MediaProjection authorisation: capturing supported system audio after approval through Android's capture dialog.
NFC: using a configured NFC tag as an optional recording trigger.
Internet access: cloud authentication and uploads, model downloads, advertising and consent services.
Advertising identifiers: advertising-related processing as described above.
Files: storing app files and reading or exporting files you select through Android's available file and sharing interfaces. This does not imply unrestricted access to all files on the device.

You can manage runtime permissions in Android's app settings. Revoking a permission can prevent the corresponding feature from working.

4. Recipients and Third-Party Services

Depending on the features you use, recipients include:

Google's AdMob advertising and UMP consent services, as described in section 3.5.
Google Drive, Microsoft OneDrive, Dropbox or the WebDAV server you connect.
Model hosting services contacted when downloading a model: Hugging Face, hf-mirror.com and alphacephei.com, depending on the feature and selected model source.
Apps and recipients selected when sharing or exporting content.
The developer and email service providers handling messages you send to our contact address.

We do not sell recordings or transcripts to third parties. Sending a file to a destination you selected, or advertising-related processing by external services, remains subject to the relevant service's policies.

External providers may process information outside your country, including outside the EEA. Their privacy notices describe their processing locations and applicable transfer safeguards. For information about transfers relating to support correspondence under our responsibility, contact us.

5. Purposes and Legal Bases

The features process data to provide recording, local transcription, user-selected backup and sharing. Optional device permissions and cloud authorisations control whether those features can operate.

Where we act as a controller and the GDPR applies, processing necessary to provide a service you request relies on Article 6(1)(b). Support correspondence is processed under Article 6(1)(f) for our legitimate interests in answering enquiries, resolving issues and retaining a limited record of their resolution. Security and the establishment, exercise or defence of legal claims may also rely on legitimate interests, subject to your rights. Processing necessary to comply with legal obligations relies on Article 6(1)(c). Where consent is required for advertising-related processing or access to information on your device, consent is requested and can be withdrawn through the applicable controls.

External providers determine their own legal bases for processing under their responsibility. Granting an Android permission is not a blanket consent to every form of processing. Withdrawing consent does not affect the lawfulness of processing carried out before withdrawal.

6. Retention and Deletion

Local recordings, transcripts and downloaded models remain on the device until deleted or the relevant app storage is removed. Temporary processing files may remain after an interruption. Exports and public copies can remain outside the app's private storage even after uninstalling the app.

Deleting a recording from the app's library does not guarantee deletion of remote copies. A deletion action that attempts to remove a remote file can fail, and separate or earlier copies may remain. Check each connected cloud destination and delete unwanted files there. Disconnecting the integration or deleting local app data does not delete a provider account or its stored files.

Cloud, advertising and model hosting services retain their own information according to their policies. The developer cannot directly delete all information held by these services. Use their privacy controls or contact them for provider-held data.

Support and privacy-request correspondence is deleted no later than 12 months after the matter is closed, unless a longer period is required by law or is necessary for the establishment, exercise or defence of a specific legal claim. In those exceptional cases, only the information necessary for that purpose is retained for the applicable period.

To request access to or deletion of personal data held by the developer, email contact@nas4.tech and describe your request. We may ask for information reasonably needed to verify the request. We do not have a separate Secure Recorder user account to delete, and we cannot remotely erase recordings stored only on your device.

7. Your Rights

Depending on the applicable law and the circumstances, you may have rights to access, correct or erase your personal data, restrict processing, receive a portable copy, object to processing and withdraw consent. These rights are subject to the conditions and exceptions in the applicable law.

For processing under our responsibility, contact contact@nas4.tech. For data held by an external provider, use that provider's privacy controls or contact them directly. You may also lodge a complaint with your competent data protection supervisory authority.

8. Children

Secure Recorder is intended for users aged 13 and older and is not directed to children under 13. This intended audience does not mean that every user aged 13 or older can independently consent to all advertising-related processing. Applicable consent requirements depend on the user's age and country. Advertising and connected cloud services also have their own age requirements and privacy terms.

If you believe that a child under 13 has sent personal information directly to us, contact us so that we can review the situation and take appropriate action.

9. Changes to This Privacy Policy

We may update this policy when the app's features or data practices change. The current policy is available on this page, with the last updated date shown above. Where required, we will provide additional notice or request renewed consent.

10. Contact

For privacy-related questions and requests, email contact@nas4.tech.