Privacy Policy – EmoApp (Emo Automation)

Last updated: 11 March 2026

EmoApp / Emo Automation ("we", "us", or "our") is a creator-focused automation toolkit that provides functionality such as automatic playlist & timestamp generation, audio splitting, video & audio merging, AI metadata checking and cleaning, YouTube scheduling and upload management, and YouTube Live automation. This Privacy Policy explains what information we collect or access, how we use it, when we share it, how long we retain it, and the choices you have about your data.

1. Scope & General Principles

Where possible, core media processing (for example: audio splitting, timestamp creation, and video merging) is performed locally on your device. Certain advanced features — such as the AI Metadata Check & Cleaner or heavy audio analysis — may require optional server-side processing. Server-side uploads or processing occur only if you explicitly opt in.

2. Information We May Access or Collect

Depending on which features you use, the app may access or collect the following categories of information:

3. How We Use Information

We use the collected information for the following purposes:

4. Server-side Processing & AI Features (Opt-in)

Some advanced features (for example: AI Metadata Check & Cleaner) may require server-side processing. We will only upload data to our servers if you explicitly opt in to those features. When you opt in, the types of data that may be transmitted include:

Retention: Uploaded data for analysis is retained only as long as necessary. Typical retention windows are: audio snippets or full files removed within 30 days after analysis, and analysis results or logs retained up to 90 days for troubleshooting or model improvement unless a different retention period is disclosed at upload time. You may request deletion of uploaded data (see "Your Rights & Controls" below).

5. YouTube API, OAuth & Uploads

To enable YouTube scheduling, uploads, and live automation, the app may request you to connect a Google account via OAuth. We request only the minimum scopes required (for example: upload, manage live streams) and only perform actions with your explicit permission.

6. Advertising & Third-Party Services

EmoApp may display advertisements delivered by third-party ad networks such as Google AdMob. These ad providers may collect device identifiers, IP addresses, and other usage signals to serve and measure ads. We do not control the data collection practices of ad networks; please review their privacy policies for details.

Google privacy reference: https://policies.google.com/privacy

7. Data Safety — Play Store Summary

Summary of data types and sharing for Play Console Data Safety (for developer reference):

Data TypeCollected?Shared with Third Parties?Purpose
Media files (audio/video)Yes — when user selects for processingShared only if user opts-in for server analysisProcessing: split, merge, AI-analysis
Audio metadataYesMay be shared for analysis if opt-inEditing, metadata cleanup, AI detection
Account info / Auth tokensOptional (if user connects)Not shared; stored encryptedUpload & scheduling to third-party platforms
Identifiers (device ID, IP)YesShared with ad networksAd delivery, analytics
Crash & usage logs (anon)YesShared with analytics/crash providersDebugging and product improvement

8. Service Providers & Third Parties

We use trusted third-party providers to operate core services (cloud hosting, analytics, crash reporting, advertising). These providers receive only the minimum data necessary to perform their services and are contractually obligated to protect the data. Examples of service categories:

9. Data Retention

Retention periods depend on the data type:

10. Security

We implement reasonable technical and organizational measures to protect data, including TLS (HTTPS) for data in transit, encryption for stored tokens, access controls, and internal audits. However, no system is perfectly secure; avoid uploading extremely sensitive personal information unless necessary and you understand the risks.

11. Your Rights & Controls

Depending on your jurisdiction (for example: GDPR in the EU, CCPA in California), you may have rights including:

How to submit a request:
Email us at carsaniaksan@gmail.com or aksancarsani@icloud.com with subject line: DATA REQUEST - [Request Type] - [Account / Email]. Include sufficient information for us to verify your identity. We aim to respond to verified requests within 30 business days.

12. Children

EmoApp is not intended for children under 13 years of age (or the relevant minimum age in jurisdictions where different limits apply). We do not knowingly collect personal information from children under the applicable minimum age. If you believe we have collected such information, please contact us to request deletion.

13. International Transfers

Data processed by our service providers may be stored or processed in jurisdictions outside your country of residence (for example, the United States). Where data is transferred across borders, we will implement appropriate safeguards such as contractual protections to help secure your data in accordance with applicable law.

14. Data Breach Notification

In the event of a security breach that creates a risk to your rights and freedoms, we will notify impacted users and the relevant authorities as required by applicable law and will provide information about steps we are taking in response.

15. Changes to This Privacy Policy

We may update this Privacy Policy to reflect changes in features, legal requirements, or our data practices. When substantial changes occur, we will provide notice in the app or by email if you have opted into communications. The "Last updated" date at the top of this policy indicates the effective date.

16. Contact

For questions, data requests, or other privacy concerns, contact:

Support email: carsaniaksan@gmail.com
Alternate email: aksancarsani@icloud.com

17. Additional Notes for Google Play & AdMob

• Ensure that your Play Console Data Safety disclosures accurately reflect the data collection and sharing described in this policy.
• If you use Google APIs (e.g., YouTube Data API), request only the minimum scopes required and comply with Google API Services policies.
• If you target users in the EEA/UK and use personalized ads, implement an appropriate consent mechanism (e.g., CMP/Consent SDK) to obtain lawful consent for ad personalization under GDPR.