CogniTab Privacy Policy
How CogniTab processes data and the choices available to protect your privacy.
Updated:
Effective date: November 11, 2026
This policy explains how CogniTab for Android and its related cloud services handle your information. For privacy questions or requests, contact cognitab68@gmail.com.
1. About this policy
CogniTab helps you create and run automation macros. Some features work on your device; others need an account or send information to online services. This policy describes the data involved in those features and the choices available to you.
2. Information we process
2.1 Account and device information
When you sign in with Google, we process your email, account identifier, display name, profile image if available, and account settings. Device registration and subscription information help us manage sign-in, access and device limits.
Technical information may include app and Android versions, device model, language, screen information, notification identifiers, network information, errors and usage activity. We use it to operate the service, diagnose issues and prevent abuse.
2.2 Macros and content you create
Macros may contain instructions, scripts, image templates, recognition models, saved sound samples and related settings. These are processed on your device for automation. When you choose synchronization, cloud backup or publication, the relevant content and settings are uploaded to provide that feature.
If you post or publish content, your chosen public name, content, comments and ratings may be visible to other users according to the feature's access settings. Reports and moderation information are used to handle safety concerns and disputes.
2.3 Screen images and recognition
With your Android permission, CogniTab can read screen content, capture images and recognize text or images to carry out your macros. This is primarily processed on your device.
Some macros include image collection to improve their recognition. After you accept the applicable disclosure, cropped screen images and related labels may be uploaded automatically while such a macro runs. Access is limited to authorized collection owners. Stop the macro if you do not want that collection to continue. Avoid running capture features over private information you do not intend to share.
2.4 Saved audio
If you use internal-audio recognition, CogniTab captures playback from a selected app after you grant the required Android permissions. It does not record the microphone. Live listening is processed on your device.
Saved sound samples and the source-app information needed to use them are uploaded when included in a macro you back up or publish. Deleting a local sample does not delete copies in existing backups or previously downloaded macros.
2.5 Purchases, advertising and diagnostics
Google Play handles purchases. CogniTab processes purchase references, subscription status and reward-verification information to provide access and prevent fraud. Advertising services may process device or advertising identifiers, network information and ad interactions.
Firebase services may process crash reports, performance information and app-usage activity. Analytics may include installation and advertising identifiers, session activity, device information and approximate geographic information. Diagnostic information helps us understand reliability and use of the app. We do not intentionally use your private screen images, recognized text or private macro content to personalize ads.
2.6 Store review and support
When you submit macro content for AI-assisted Store review and accept its disclosure, submitted code, relevant attachments and review feedback may be sent to the AI service to help assess the submission. AI recommendations do not replace the final moderation decision.
When you contact support, we process the message, attachments and technical information you choose to provide. Do not send passwords, one-time codes or payment-card details.
3. Why we use information
We use information to provide sign-in, automation, synchronization, backup, content sharing, purchase access, notifications, support and moderation. Recognition images are used to improve the corresponding macro's recognition. Diagnostics and security information help us fix problems, prevent abuse and meet legal obligations.
Account-based features need account information. Cloud features need the content you choose to upload. Permissions and optional features are explained when you use them; you can decline a permission or avoid a feature that requires processing you do not want.
4. Permissions and consent
- Accessibility access lets the app read relevant screen content and perform macro gestures. You enable it in Android settings.
- Screen capture requires Android's permission and is used for recognition and screen-based automation.
- Internal-audio recognition requires Android audio and screen-capture permissions.
- Display-over-other-apps permission enables floating controls. Notification permission enables relevant notifications.
You can stop a macro or revoke permissions in Android settings. Consent requires an affirmative action; silence or continued use does not give consent to a new processing purpose. The app keeps the accepted policy version and time. Where a feature has its own disclosure, review it before accepting. To request withdrawal or restriction of server-side processing, use the contact in section 9.
5. Who receives information
Information is shared only as needed for the relevant feature or a legal obligation:
- Google and Firebase provide sign-in, notifications, analytics, crash and performance services.
- Google Play provides purchase processing and subscription verification.
- Google Mobile Ads and participating ad networks, including Unity Ads where used, provide advertising and reward verification.
- Cloud hosting and storage providers, including Cloudflare, store uploaded content and recognition images.
- OpenAI provides AI-assisted Store review after the relevant consent. Retention at an external provider follows its applicable data controls; no zero-retention promise is made.
- Other users can access content you publish or share according to its visibility and access settings.
- Authorities or other parties may receive information when required by law or necessary to address fraud, abuse or safety concerns.
CogniTab does not sell personal data.
6. Local and cloud data
Creating or editing a local macro does not itself publish it. Screen recognition and live audio are primarily local. Uploads occur in the cloud features, recognition-image collection and Store-review situations described above.
Local content can be removed in the app or by clearing app storage. Android backup or device-transfer settings may also affect some local data. Removing local data does not automatically remove an existing cloud copy.
7. How long information is kept
Local content remains until you delete it, clear app storage or uninstall. Account and uploaded content are kept for the relevant service while needed, subject to your deletion requests.
Recognition images and review information follow the related collection, content or account deletion process. Some records may be retained for security, fraud prevention, billing, moderation, disputes or legal obligations. Provider-held records follow the provider's retention and deletion controls. Copies already downloaded or shared by other users cannot be recalled from their devices.
8. Security
We use HTTPS for sensitive data in transit and account-based access controls for relevant cloud features. No online system is completely secure. Use permissions carefully and avoid including private information in content you publish or submit.
9. Your choices and privacy requests
You can manage account details, registered devices, permissions and notifications, and delete eligible local or cloud content. To request access, correction, a copy, restriction, withdrawal of consent or deletion, email cognitab68@gmail.com.
Include your sign-in email or username, the request and the data concerned. We may verify account ownership and explain any additional steps. Do not include passwords, verification codes, payment-card details or identity documents in the initial request. Responses use the same email thread.
Requests in Vietnam
Under Article 5 of Decree 356/2025/ND-CP, a request submitted through the applicable procedure receives a response and procedural guidance within two working days. Implementation periods are:
- Withdrawal, restriction or objection: 15 days, or 20 days if a processor or third party must stop processing; one justified extension of up to 15 additional days.
- Access, correction or provision: 10 days, or 15 days if a processor or third party must correct the data; one justified extension of up to 10 additional days.
- Deletion: 20 days, or 30 days when action by a processor or third party is needed; one justified extension of up to 20 additional days.
- Protective measures: 15 days, with one justified extension of up to 15 additional days.
Any extension, refusal or retention exception must be explained with its basis. Only the two-day response period above is expressed as working days. Processing permitted without consent remains subject to applicable law. You may complain to the competent authority. These periods are separate from the seven-day account-deletion waiting period below.
10. Account deletion
Start in Profile > Settings > Account > Delete account, or follow the public instructions at https://cogni-tab.com/legal/account-deletion. If you cannot use the app, email the privacy contact.
An in-app deletion request locks the account and schedules permanent deletion after seven days. During the waiting period, signing in lets you restore the account and cancel deletion.
Deletion removes eligible account records, registered devices, backups, published macros and related interactions under CogniTab's control, subject to the exceptions in section 7. Remove device-only data separately. Uninstalling alone does not delete the cloud account. Account deletion does not cancel a Google Play subscription; manage it in Google Play.
11. International processing
Service providers may process information outside Vietnam or your country. This can apply to account services, cloud storage, advertising, diagnostics and consented Store review. The purposes and recipients remain those described in this policy.
12. Children
CogniTab is not intended for children below the minimum age required by applicable law. If you believe a child's information has been provided inappropriately, contact us.
13. Changes
We update this policy when relevant data practices or public features change. The effective date is shown above. Material changes may be brought to your attention in the app, with renewed consent where required.
14. Contact
CogniTab support and privacy requests: cognitab68@gmail.com.