// PRIVACY_POLICY.md

WERE Privacy Policy

Document Privacy Policy
Last Updated July 3, 2026
Status ● Active
> Initializing privacy documentation...
This document outlines the data processing practices for the Were application and associated services. Please review this policy carefully to understand how we collect, use, and safeguard your information. By accessing or using Were, you acknowledge and consent to the practices described herein.
01

Information Collection Overview

To deliver and maintain the Were service, we process various categories of information. The data we handle falls into three primary classifications, each serving a specific operational purpose.

  • User-Submitted Content: Prompts, images, video files, text, documents, configuration settings, and edits that you provide or generate within the application. This data is processed to produce the outputs you request.
  • Technical Telemetry: We automatically capture technical data points including application version, device specifications, operating system details, language preferences, diagnostic reports, crash logs, and aggregated usage metrics.
  • Support Communications: When you initiate contact with our support team, we may retain your email address, message content, and relevant contextual information to facilitate resolution and maintain service records.
02

Purposes of Data Processing

Information collected through Were is utilized for a range of operational objectives. These include: executing user requests, ensuring service reliability, identifying and resolving technical issues, optimizing performance, maintaining security protocols, detecting and preventing abuse, and facilitating user communications regarding support matters and service updates.

03

Device Permission Framework

Certain features of Were may require access to specific device capabilities. Permissions are requested only when a corresponding feature is activated, and you may manage these preferences through your device settings at any time. The permissions we may request include:

  • Photo and Media Library: Required for importing, editing, and exporting visual content through the application interface.
  • Camera Access: Utilized exclusively when you select camera-based capture features within the application environment.
  • Network Connectivity: Essential for server communication, content processing, application updates, diagnostic operations, and security functions.
  • Push Notifications: If enabled, may be used to deliver generation status alerts, service announcements, and relevant application notifications.
04

Third-Party Service Integrations

Were incorporates services from third-party providers to support various operational functions, including infrastructure hosting, performance analytics, payment processing, advertising services, diagnostic tools, AI computation, and general systems administration. Each third-party provider operates under its own terms of service and privacy policies, which govern their respective data handling practices.

05

Data Retention Protocols

We retain information for periods commensurate with the purposes for which it was collected. Retention durations are determined by operational requirements, security considerations, support needs, dispute resolution processes, legal obligations, and standard business record-keeping practices. Certain technical and generation-related datasets may be retained on a temporary basis only.

06

Security Implementation

We employ industry-standard administrative, technical, and physical security measures designed to protect information against unauthorized access, modification, disclosure, or destruction. Despite these safeguards, no digital service can guarantee absolute security. Electronic storage and internet transmission methods carry inherent risks, and we cannot ensure complete data protection.

07

Children's Data Protection

Were is not directed toward individuals under the age of 13, and we do not knowingly collect personal information from children in this age group. If you become aware that a child under 13 has provided us with personal information, please contact us immediately and we will take appropriate steps to remove such data from our systems.

08

User Controls and Options

You maintain certain controls over your information. You may discontinue use of Were, adjust device permission settings, remove local application data from your device, or submit privacy-related inquiries through our contact channels. Please be aware that exercising certain options may impact the functionality or availability of specific application features.

09

Cross-Border Data Transfers

Information processed in connection with Were may be transferred to and processed in jurisdictions outside your country of residence. Data protection regulations and privacy frameworks vary across regions. By using Were, you acknowledge that your data may be subject to the legal frameworks of jurisdictions where processing occurs.

10

Policy Revision Procedures

We may update this Privacy Policy periodically to reflect changes in our operational practices, service features, or applicable regulatory requirements. Material revisions will be communicated through appropriate channels. Continued use of Were following the effective date of a revised policy constitutes acceptance of the updated terms.

11

Contact and Inquiries

For questions, concerns, or requests regarding this Privacy Policy or our data handling practices, please direct correspondence to austinileric783@gmail.com. We will respond to legitimate inquiries as promptly as circumstances permit.