Privacy Policy
1.Data Collection Architecture
Consistent with our transparent system architecture, we categorize data collection into explicit buckets required to execute our analytical features:
- Identity & Profile Metadata: User email, name, and lifestyle preferences collected via our Authentication and Profile Services.
- Visual and Biometric Imagery: Face photos, skin surface profiles, and body silhouettes processed by the Photo Upload Service to power Face Type, Skin Tone, and Body Shape AI engines.
- Digital Closet Assets: Uploaded apparel imagery, cataloged descriptors, and style tags stored in our Digital Closet Database.
- Integrated Third-Party API Data: Real-time situational variables, including calendar timelines, geolocation inputs, and climate conditions.
2.Explicit Google API User Data Disclosure
AiStyle interfaces directly with authorized Google API Scopes to ensure seamless context-aware outfit coordination. Our practices strictly satisfy all global vendor integration parameters.
Specific Scope Operations and Justification
-
Google Login API (Profile/Email Scopes): Used solely to authenticate
your login sessions, securely link your unique identity profile to our User Database,
and transmit critical service reports. This allows for a streamlined and secure user
onboarding process, enhancing user experience and account security. The requested
scopes (
profile,email,openid) are the minimum necessary for this functionality. - Google Calendar API (Read-Only Event Scopes): Used specifically by our Calendar Service to fetch upcoming event titles, start/end times, and descriptions. This allows our recommendation engine to know if you are attending a formal business meeting, casual brunch, or wedding, automatically suggesting appropriate attire matching the event context. This read-only access is crucial for providing the core value proposition of AiStyle: context-aware outfit planning. We do not modify, delete, or create any calendar events.
3.Data Processing and AI Model Transmission
To deliver advanced styling insights, your data is processed through well-defined cloud-infrastructure nodes:
- AI/LLM Processing: Images and text parameters are analyzed using cloud-hosted foundational models via enterprise-grade secure API connections. This data is handled in accordance with commercial data confidentiality terms, ensuring user inputs are not utilized to train public foundational models.
- External Integrations: Location coordinates are securely transmitted to Weather and Location APIs to pull local ambient temperatures and weather conditions. Data is strictly processed as an anonymous payload without linking user profiles to external networks.
4.Data Storage, Isolation, and Retention
All data is maintained in isolated environments within our structured Data Stores layer:
- Structured user accounts, calendar caches, and analytical metrics are written to isolated Relational and Document Databases.
- Raw media and apparel photos are archived in secured Object Storage buckets behind strict Identity and Access Management (IAM) firewalls.
- Data is retained only as long as your account remains active. If an account is abandoned or manually deactivated, all underlying records enter a secure 30-day deletion cycle.
5.User Rights, Account Deletion, and Data Revocation
You maintain ultimate sovereignty over your personal data. You may exercise these rights at any time:
- Disconnecting Google Scopes: You can explicitly revoke AiStyle's access permissions to your Google Calendar at any moment via your personal Google Account Security Console. This action will immediately cease AiStyle's ability to access your calendar data.
- Complete Data Erasure: An explicit "Delete Account" button is accessible within your App Profile Settings. Triggering this feature commands our Cloud Infrastructure to permanently wipe all corresponding user database records, profile images, and digital closet historical artifacts from our physical storage disks.
6.Security and Infrastructure Resilience
We enforce strict organizational and electronic security architectures. All communications traversing Client and Backend Services are forced over encrypted HTTPS / JSON channels. Our network architecture employs enterprise Web Application Firewalls (WAF), automated backup and recovery mechanisms, and continuous logging/observability nodes to preemptively intercept unauthorized malicious intrusion attempts.
7.Contact Information
For questions regarding these compliance documents or our internal data handling frameworks, contact our Data Protection Office at: compliance@aistyle-app.internal.
Google OAuth Verification Readiness Statement
This section outlines AiStyle's adherence to Google's OAuth 2.0 Policies and the Google API Services User Data Policy, specifically addressing the requirements for sensitive scope verification.
1. Identity and Intent Representation
AiStyle accurately represents its identity and intent to Google users. Our application
name, support email, home page URI (https://www.theaistyle.com), and
privacy policy URI are clearly displayed on the OAuth consent screen and accurately
reflect our application's identity. We are transparent about the data requested and
the purpose for its use, ensuring users can make informed decisions when granting
authorization.
2. Transparency and Privacy Disclosures
Our Privacy Policy thoroughly discloses how AiStyle accesses, uses, stores, and shares Google user data. This policy is publicly accessible, hosted within the same domain as our application's home page, and linked on the OAuth consent screen. We commit to limiting our use of Google user data to the practices explicitly disclosed in our published Privacy Policy.
3. Minimum Relevant Permissions
AiStyle strictly adheres to the principle of requesting the minimum relevant permissions. We only request access to Google user data that is critical and necessary to implement our application's core features. We do not request access to information that is not essential for our application's functionality.
-
Google Login API (Profile/Email Scopes): We request
profile,email, andopenidscopes for user authentication and profile linking. These are the narrowest scopes available for secure login and personalized user experience. -
Google Calendar API (Read-Only Event Scopes): We request read-only
access to calendar events
(
https://www.googleapis.com/auth/calendar.events.readonly) to provide context-aware outfit recommendations. This scope is essential for our core functionality of integrating with a user's agenda for outfit planning.
4. Data Usage and Limited Use Compliance
AiStyle's use and transfer of information received from Google APIs strictly adheres to the Google API Services User Data Policy, including the Limited Use requirements. We commit to:
- Limiting our use of data to providing or improving user-facing features that are prominent in the AiStyle application's user interface.
- Prohibiting the transfer or sale of user data to third parties like advertising platforms, data brokers, or any other unauthorized entities.
- Ensuring that human access to user data is strictly limited to security purposes (e.g., investigating abuse) or to comply with applicable laws, and only with the user's affirmative agreement for specific data viewing.
5. Secure Operating Environment
AiStyle maintains a secure operating environment to protect all user data in transit and at rest. We implement reasonable and appropriate steps to safeguard applications and systems that utilize Google API Services and derived data against unauthorized access, use, destruction, loss, alteration, or disclosure.
6. Video Demonstration
As part of the verification process for sensitive scopes, AiStyle will provide a video demonstration that fully illustrates:
- How a user initiates and grants access to the requested scopes (Google Login and Google Calendar read-only).
- The OAuth consent flow, including the correct display of the App Name and the OAuth client ID in the browser address bar.
- The detailed usage of the granted sensitive scope (Google Calendar read-only) within the AiStyle application, demonstrating how calendar events are used to generate context-aware outfit suggestions without modifying any user data.