AppMato Privacy Policy

1. Who this notice applies to

This Privacy Policy explains how AppMato handles personal data when you visit appmato.com, create or use an AppMato account, use the launcher, use an AppMato application, or place an order through the Shop. An application, vendor, payment processor, or delivery provider may provide an additional privacy notice when it handles data under its own terms.

The operating legal entity is APPMATO TECHNOLOGIES PRIVATE LIMITED.

Principal place of business:
1-4/3-2/A/1,
Road No. 1,
Laxmi Nagar,
Mancherial,
Telangana,
504208,
India.

For privacy questions and requests, contact privacy@appmato.com.

2. AppMato’s role and the legal framework

For the personal data AppMato decides to collect and use for its own account, launcher, support, security, and product purposes, AppMato acts as the Data Fiduciary under India’s Digital Personal Data Protection Act, 2023. A connected application or third-party provider may be a separate Data Fiduciary, or may process data for AppMato under a contract. The applicable role depends on the actual feature and relationship.

This notice is designed for users in India and for other regions where AppMato offers the Services. Additional regional rights or notices may apply. We do not treat this page as a substitute for a feature-specific notice where a product collects materially different data.

3. Personal data we may collect

We collect only the data reasonably needed for the relevant account, feature, security measure, or legal obligation. Depending on how you use AppMato, this may include:

• Account and identity data: name, username, email address, mobile number, country or region, adult-age confirmation, and optional profile or transaction details you choose to provide. AppMato does not require a street address for ordinary account registration.
• Authentication and security data: password hashes, email or mobile verification status, one-time-code records, login and session information, device and security signals, and records of security or support events. AppMato should not store plain-text passwords.
• User content: notes, documents, pages, forms, code, files, folders, images, videos, audio, books, bookmarks, playlists, messages, prompts, generated results, and other content you choose to create, upload, save, or transmit through an application.
• Application activity: settings, preferences, saved items, search and browsing actions, app usage, transaction or order details where Shopping or another paid feature is used, and technical actions needed to provide the application.
• Device and technical data: IP address, browser and operating-system details, device identifiers where available, language, approximate region inferred from network information, error reports, timestamps, and security logs.
• Communications: requests, feedback, support messages, and information needed to resolve a complaint or data-rights request.
• Optional preference data: consent choices, communication preferences, accessibility settings, and cookie or local-storage choices. We do not treat a consent record as permission to collect unrelated data.
• Profile images and likeness data: a profile photograph or avatar you choose to upload, associated file metadata, and moderation or security records. AppMato does not use an ordinary profile picture as biometric identification unless a separate feature expressly explains and lawfully supports that processing.
• Payment and commerce data: order, subscription, vendor, delivery address, contact, refund, tax, and fraud-prevention information when you use a paid feature or Shop. A delivery address is collected only when it is needed to fulfil a physical order. Full card numbers should be handled by the approved payment provider, not stored by AppMato.

4. Where data comes from

• Directly from you when you register, update your profile, use an application, upload content, make a request, or contact us.
• Automatically from your browser, device, application activity, cookies, local storage, and security logs.
• From service providers that help us authenticate accounts, deliver email or SMS verification, host data, process payments, prevent abuse, operate an application, or fulfil and deliver an order.
• From third-party services when you choose to connect them, import content, follow an external link, or use an integrated feature. Those services may provide their own notice and controls.

5. Why we process personal data

We use personal data for the following purposes, as applicable to the feature you use:

• Create, authenticate, maintain, and secure your AppMato account and connected applications.
• Provide, personalise, troubleshoot, improve, and protect the Services, including storage, synchronisation, search, communications, media, AI, speech, phone pairing, and other requested features.
• Process purchases, subscriptions, vendor orders, deliveries, refunds, fraud checks, and customer-service requests where AppMato supports commerce or paid features.
• Send essential service, security, account, and transactional messages. Optional product updates and promotional communications are separate, require the applicable choice, and must include an unsubscribe method. Unsubscribing from marketing does not stop necessary security, account, or transaction messages.
• Measure reliability and improve the product using optional analytics where enabled. Essential browser storage remains necessary for sign-in and core workspace preferences.
• Detect, investigate, and prevent security incidents, abuse, fraud, unauthorised access, and violations of the Terms.
• Comply with applicable law, respond to lawful requests, establish or defend legal claims, and protect the rights and safety of AppMato, our users, and the public.
• Run the privacy, support, security, and account-governance workflows requested by you, including identity verification, request status, audit records, remote session revocation, and abuse investigations.

6. Consent and optional controls

Where consent is required, AppMato will ask for it in clear and plain language, identify the data and specific purpose, and keep optional analytics, advertising, and product-communication choices separate from acceptance of the Terms. You may withdraw consent through the same or an equally accessible control used to give it. Withdrawal does not affect processing that occurred before withdrawal and may mean that a feature can no longer operate.

AppMato records the notices and consent choices needed to respect your preferences and meet applicable legal requirements. Essential storage needed for sign-in, security, and core workspace functions is separate from optional choices.

7. When we share data

We may disclose the minimum data needed to the following categories of recipients:

• Hosting, database, backup, storage, security, monitoring, and infrastructure providers.
• Email, SMS, authentication, identity-verification, customer-support, and communication providers.
• Application partners and third-party services that you choose to connect or that are required to deliver a requested feature.
• Payment processors, Shop vendors, independent logistics and delivery providers, or other service partners when you place an order or use another transaction feature.
• Professional advisers, auditors, insurers, or potential transaction partners where a legitimate business need and appropriate confidentiality protections apply.
• Courts, regulators, law-enforcement bodies, or other recipients where disclosure is required by law or reasonably necessary to protect people, property, or the Services.

8. International processing and third-party links

AppMato or its providers may process data in countries other than the country where you live. We will use the safeguards required by applicable law and will not make a blanket promise that all data remains in India unless the relevant service has been designed and verified that way. Transfers are subject to any restrictions or government directions that apply to AppMato.

An AppMato application may open an external service, embed third-party content, or send data to a provider selected by you. Once data is received by that third party, its own notice and terms apply.

9. Retention and deletion

We keep personal data for as long as needed to provide the account or feature, maintain security and business records, resolve disputes, comply with legal obligations, and enforce our agreements. Retention differs by application and data type. User content may remain until you delete it, close the account, or the relevant application removes it under its own retention rules.

When data is no longer needed, we will delete it, anonymise it, or isolate it for a limited period where required for backups, security, legal claims, or compliance. Where applicable, processing logs and associated personal data will be retained for at least the period required by the DPDP Rules and CERT-In directions, then deleted unless another law requires longer retention.

Account deletion is not an instant erasure of every record. We may retain limited information needed for fraud prevention, security logs, financial or tax records, dispute handling, legal claims, or regulatory compliance. Deleted content may remain briefly in encrypted backups until the normal backup rotation completes, but it will not be restored for ordinary use.

10. Your choices and rights

Subject to applicable law, reasonable identity verification, and the rights of others, you may request:

• Information about the personal data and processing associated with your AppMato account.
• Correction or updating of inaccurate or incomplete profile data.
• Deletion or erasure of data that is no longer needed or that may lawfully be deleted.
• Withdrawal of optional consent and changes to optional product-update or analytics preferences.
• A copy or export of data that can reasonably be provided in a portable format.
• A review of a privacy complaint or grievance and information about how to escalate it under applicable law.
• Nomination of another individual to exercise your rights in the event of your death or incapacity, where the applicable law and our verification process allow it.

11. Security and incident response

We use reasonable technical and organisational measures appropriate to the data and risk, including access controls, authentication, password hashing, secure transmission, logging, backups, provider contracts, monitoring, and incident response practices. Access to personal data should be limited to people and systems that need it, and sensitive access should be reviewable through logs. No online service can guarantee absolute security.

If a personal-data breach occurs, AppMato will make the notifications required by applicable law, including clear information for affected users and the Data Protection Board where the DPDP Rules require it. AppMato will assess whether CERT-In reporting or another regulator notification is required. Keep your credentials private and tell us promptly if you suspect unauthorised access.

12. Children and parental consent

For India, a child is under eighteen. AppMato’s default account design is adult-oriented. Before processing a child’s personal data, the applicable service must obtain verifiable consent from an identifiable adult parent or lawful guardian and apply due diligence. AppMato will not knowingly undertake processing likely to harm a child’s well-being, track or behaviourally monitor children, or direct targeted advertising at children, except only where a notified legal exception applies.

If you are a parent or lawful guardian and believe a child has provided data improperly, contact privacy@appmato.com. We may ask for information needed to verify the request and will delete or restrict the data where appropriate, subject to legal retention and safety obligations.

13. Grievance, escalation, and contact

We may update this Privacy Policy when our Services, providers, data practices, or legal obligations change. We will publish the updated version with a new “Last updated” date and provide additional notice where required.

For access, correction, deletion, consent, security, or grievance requests, sign in and use Settings → Data & Privacy where available, or email privacy@appmato.com. Under the DPDP Rules, the grievance process must provide a response period not exceeding ninety days once the applicable provisions commence.

Include your AppMato username or account email and a clear description of the request. We may verify identity before disclosing or changing data. Never send a password, OTP, payment-card number, identity document, or other secret through an unrequested email.