Effective date: 11 September 2026
1. Who is responsible
This Privacy Policy applies to the Communicatio Secreta Android application (package com.communicatio_secreta), the Communicatio Secreta Windows desktop application, and the companion WordPress service at communicatiosecreta.pterosoftstudio.com. Communicatio Secreta is provided by Pterosoft Studio, referred to below as “we”, “us”, or “the developer”.
Privacy questions and account-deletion requests may be sent to privacy@pterosoftstudio.com.
2. Information handled by the app
| Information | How it is used | Where it is handled |
|---|---|---|
| Google account identity | To sign you in, display your identity, and associate or restore the correct Google Play subscription. This includes your Google account identifier, verified email address, and display name. | Provided by Google Sign-In. The identity details are stored in the app’s private local storage until you sign out, clear the app’s data, or uninstall it. The Google ID token is used to validate sign-in but is not retained by the app. The app does not send this Google identity information to WordPress. |
| Windows desktop licence username and password | To authenticate the WordPress account used to license the Windows desktop application and confirm that it has an active website entitlement. | Sent by the Windows desktop application over HTTPS to our WordPress authentication endpoint. The password is held only as needed to make the request, then cleared and is not intentionally retained by the desktop application. This WordPress login is not used for Android sign-in. |
| Windows desktop WordPress account and membership details | To display the signed-in identity and decide whether a website licence permits access to the Windows desktop application. This may include login name, email address, display name, plan, membership status, and expiry information. | Returned by our WordPress membership service and held by the desktop application for the current running session. The companion website stores the underlying account and membership records. These details are not used for Android sign-in. |
| Google Play purchase and subscription information | To start a purchase, prevent duplicate entitlements, verify and acknowledge purchases, restore access, and respond to cancellations, refunds, grace periods, or account holds. | Google Play processes the purchase and makes information such as product ID, purchase token, order reference, and subscription state available to the app. To associate the purchase with the signed-in account, the app sends Google Play an irreversible hash derived from the Google account identifier as an obfuscated account ID; it does not send the raw identifier for this purpose. The app does not receive your full card number. |
| Companion website membership and payment information | For accounts and memberships used to license the Windows desktop application, as well as website payment processing, fraud prevention, account management, and customer support. | WordPress, Paid Member Subscriptions, and Stripe may process account, transaction, billing, and payment information under their respective policies. The Android app does not embed the website checkout and does not directly receive full card details. |
| Optional encrypted transfer relay data | When you choose the WordPress transfer service: to store and deliver an already encrypted .nspt container through an expiring link, enforce quotas, verify file integrity, and allow the sender to revoke it. | The WordPress service stores the encrypted container and limited metadata, including the sender’s WordPress account ID, original filename, file size, timestamps, token hash, and checksum. It does not receive the container passphrase, one-time pad, or recovered plaintext. The recipient does not need a WordPress account. |
| Network and security data | To deliver requests, limit authentication abuse, diagnose failures, protect accounts, and meet security or legal obligations. | Our server and service providers may process IP address, request time, requested route, response status, and user-agent information in ordinary server and security logs. |
| Cryptographic content and local files | To create, authenticate, encrypt, decrypt, display, play, import, or export content at your direction. | Message text, one-time-pad packages, digit groups, generated audio, passphrases, encrypted containers, and the local pad-use ledger remain on your device unless you explicitly transfer or share a file. |
3. Information we do not collect through the app
The Android app does not request access to your location, contacts, phone, SMS, camera, or microphone. It does not contain an advertising SDK or a third-party analytics SDK. Generated numbers-station audio is synthesized by the app; it is not a microphone recording.
The Android app requests Internet access only for user-initiated Google authentication, Google Play billing, and related online functions. Google Sign-In requests only the basic identity information needed to authenticate you; the app does not request access to Google Contacts, Drive, Gmail, or other sensitive or restricted Google account data. Android cloud backup is disabled for the app.
4. Cookies and the companion website
The Android app does not embed the website checkout and does not use WordPress for Android sign-in. The Windows desktop application’s licence check sends credentials directly to the authentication endpoint and does not create a browser cookie. If you separately visit the companion WordPress website or use its encrypted transfer relay, the website and its providers may use cookies or local storage required for sign-in, account management, security, fraud prevention, payment processing, and transfer-service operation.
5. Why we process information
Depending on your location and interaction with the service, we process information to perform a contract with you, take steps you request before entering a contract, operate and secure the service, comply with legal obligations, and pursue legitimate interests such as fraud prevention and service reliability. Where consent is legally required, you may withdraw it without affecting processing already performed.
6. Service providers and sharing
We do not sell personal information and do not share it for third-party behavioural advertising. Information may be disclosed only as needed to:
- hosting, infrastructure, security, and support providers that operate the companion WordPress website and optional transfer relay;
- Google, for identity authentication, Google Play distribution, billing, subscription management, fraud prevention, and reporting;
- WordPress, Paid Member Subscriptions, and Stripe, for Windows desktop licence authentication, web payments, website membership administration, and customer support;
- professional advisers, authorities, or other parties when required by law or necessary to protect legal rights and service security; or
- a successor organisation in a merger, acquisition, restructuring, or asset transfer, subject to legally required notice and safeguards.
These providers process information under their own terms and privacy policies or under agreements with us. Information may be processed outside your country. Where required, appropriate transfer safeguards must be used.
7. Security
The applications require HTTPS for server communications, reject failed TLS verification, and do not permit clear-text Internet traffic. The Android app does not retain the Google ID token. The Windows desktop app does not intentionally store the WordPress membership password. Google identity details are kept in Android app-private storage, Android backup is disabled, and Google Play purchase state is checked before an Android Play entitlement is granted.
No system is completely secure. Device compromise, malicious keyboards or accessibility services, screenshots, clipboard history, backups made outside the app, server compromise, and user-created copies can expose information despite these safeguards.
8. Retention
- Google identity data on the device: retained in the app’s private storage until you sign out, clear the app’s data, or uninstall it. The Google ID token is not retained.
- Windows desktop WordPress licence session: account and membership information returned to the desktop application is kept for the current running session and cleared when you sign out or the process ends.
- Local cryptographic files: retained on your device until you delete them. The developer cannot remotely delete files that were never uploaded.
- Optional transfer relay: encrypted containers and their associated metadata are retained for the limited period configured for the relay, or until the sender removes them, after which they are deleted through the service’s normal cleanup process.
- Account and entitlement records: retained while needed to provide and secure the account, administer purchases, resolve disputes, and meet legal obligations.
- Transaction and tax records: may be retained for the period required by accounting, tax, payment, anti-fraud, and other applicable laws.
- Server and security logs: retained only as long as reasonably necessary for service operation, abuse prevention, investigation, and legal compliance.
When information is no longer required, we delete or anonymise it where reasonably possible. Backup copies may persist until overwritten through the normal backup cycle.
9. Account deletion and privacy requests
To request deletion of a Communicatio Secreta WordPress account and associated personal data, email privacy@pterosoftstudio.com with the subject “Communicatio Secreta account deletion”. Send the request from the email address associated with the account or provide enough information for us to verify ownership.
Signing out of the Android app removes its locally stored Google identity and credential state. Clearing the app’s data or uninstalling it also removes that local information. These actions do not delete your Google Account, delete a WordPress account used by the Windows desktop application, or cancel a subscription.
Manage or delete your Google Account through Google. Cancel an Android subscription through Google Play. For deletion of a WordPress account used by the Windows desktop application, we process the request without undue delay after identity verification and delete or anonymise associated data unless retention is required for legal obligations, payment records, fraud prevention, dispute resolution, or security. A WordPress account deletion does not automatically cancel a Google Play or Stripe subscription; cancel the subscription through the provider that billed you.
You may also request access, correction, restriction, portability, or deletion of personal information, or object to certain processing, where these rights apply. You may lodge a complaint with your local data-protection authority.
10. Children
Communicatio Secreta is not designed or directed to children. We do not knowingly collect personal information from children. If you believe a child has provided personal information, contact us so that we can investigate and delete it where required.
11. Third-party policies
- Google Privacy Policy
- Google Play Terms of Service
- Google Payments Privacy Notice
- Stripe Privacy Policy
12. Changes to this policy
We may update this policy when the app, service providers, legal requirements, or data practices change. The revised page will show a new effective date. Material changes will be communicated through the app, website, or another appropriate channel where required.
13. Contact
Developer: Pterosoft Studio
Application: Communicatio Secreta
Website: communicatiosecreta.pterosoftstudio.com
Privacy contact: privacy@pterosoftstudio.com