Awonder Privacy Policy

1. About this policy and how to contact us

SkyMuse Labs is the independent brand under which Awonder is personally operated from New York, United States. Our initial beta is offered in the United States. This policy explains how we handle information when you use Awonder, its connected services, and skymuselabs.com. “We,” “us,” and “our” refer to Awonder's operator under the SkyMuse Labs brand.

For support, privacy requests, or concerns about your information, email hello@skymuselabs.com. Please do not send passwords or verification codes. We may ask for information reasonably needed to verify a request before disclosing or deleting account information.

2. Information we handle

Account and profile information. We handle your account identifier, email address or phone number used to sign in, authentication-provider information, and the profile details you supply, such as your name, username, and avatar. Apple or Google may supply basic account information when you use their sign-in services. We also save onboarding progress, preferences, consent choices, permission settings, and your confirmation that you meet the beta's minimum age, including its wording version and timestamp.

Photos, creative inputs, and results. We handle photos you select or take, persona and pet reference photos, creative instructions, messages and captions, relevant saved style information, and generated images and analyses. Results may include estimated visible facial characteristics, face-shape resemblance, color recommendations, outfit feedback, and playful animal interpretations. These are creative or styling estimates, not medical findings or identity verification. The current facial-analysis implementation does not create a face-recognition template for identifying or authenticating you.

Social activity. We store friend requests and accepted friendships, blocks, shared posts, participant references, reposts, reactions, comments and replies, game participation and answers, and poll votes. Other people can provide information about you through permitted collaborations, shared content, or reports.

Support and safety information. We handle messages and reports you submit, the content or account reported, limited diagnostic context, and an optional screenshot you choose to attach. In-app feedback can include a contact address when you allow follow-up. Emailing us provides your address and the information in your message.

Technical and usage information. We handle app/build and operating-system versions, feature events, request identifiers, timings, error categories, consent records, and generation-usage/accounting records. These can be linked to your account; they are not necessarily anonymous. Notification delivery also uses push tokens, device-registration information, notification preferences, timezone, read/delivery state, and relevant in-app destination activity. Network and hosting providers process technical connection information, such as IP addresses, to deliver and secure their services.

We use the photos you select; Awonder does not automatically upload your entire photo library. Camera, photo-library, and notification permissions are controlled through your device. Account-specific data and cached images may also be stored on your device to support saved results and reliable operation.

3. How we use information

We use information to authenticate you; maintain and synchronize your account; create, save, and display requested results; provide friend, collaboration, game, and sharing features; deliver eligible notifications; answer support requests; investigate abuse; enforce permissions and generation limits; prevent duplicate requests; diagnose failures; and improve the service.

The current app does not include advertising trackers, cross-app advertising identifiers, or session-replay analytics. Its first-party product telemetry accepts restricted event and diagnostic fields, not photo content, prompts, comment text, access tokens, or full error messages. Support reports are a separate channel and can contain the content you deliberately submit.

4. AI processing and your choices

Awonder uses the OpenAI API to generate personalized images and analyses. With your permission, selected photos, instructions, and relevant saved style information are sent to OpenAI through Awonder's backend to produce results. Some experiences include additional processing, such as preparing a color-season comparison image. No-person card creation does not require or send persona reference photos.

Photos and instructions sent through Awonder's OpenAI API integration are not used to train OpenAI's models. This is different from retention: OpenAI may retain API content for abuse monitoring, generally for up to 30 days, with longer retention where required by law or necessary for safety. Image safety review and some API capabilities have additional retention rules. Awonder does not promise zero provider retention. See OpenAI's API data controls: https://developers.openai.com/api/docs/guides/your-data.

You can decline AI processing or turn it off in Settings → AI privacy. This prevents future AI requests governed by that permission, including new permitted persona collaborations. It does not retract information already transmitted, necessarily stop a request already dispatched, delete saved results, or erase data already retained by OpenAI. Use the separate content or account deletion controls, or contact us, if you also want saved data removed.

Only upload photos you have permission to use. AI results may be inaccurate.

5. Personas, friends, and shared creations

The initial walkthrough saves your selected starter photo to My persona so it can be reused across your account. New personas show “Allow friends to imagine with me” enabled by default for accepted friends, with an opportunity to turn it off. This permission and your AI-processing choice are separate. You can manage persona photos and permissions later in Me. Existing deliberate permission choices are preserved.

When the required permissions allow a friend to create with your persona, its selected reference photos may be processed by OpenAI for that creation. Remix and Join also depend on the applicable permissions for the people pictured. Repost permission does not grant permission to generate new images using someone's persona or to access their private source photos.

Your username and configured discovery/display information help others find and recognize you. Sharing exposes the selected post, creator attribution, and related social interactions to its authorized audience; it does not make all your private saved content available.

New posts' sharing controls currently start with “Allow friends to repost” on, and you can turn it off before sharing. Existing posts retain their saved setting. When enabled, an eligible friend can repost the original post to that friend's current friends, including people who are not your friends. Reactions and comments remain attached to the original post. The beta does not turn friends-only posts into a public community library.

Unsharing or deleting a post, disabling repost permission, undoing a repost, blocking, and changes in friendship can remove access through the affected route. A person may still have a different valid access route. Previously issued temporary media links can remain usable until they expire. Downloaded images, screenshots, external exports, and other people's independently owned collaborative creations are not automatically recalled by changing a permission or deleting your account. Contact us about unwanted content involving you.

6. Notifications

We keep relevant in-app activity separately from push delivery preferences. You can control push categories in Settings: “Friend requests & activity” and “Other app activity.” Turning push off does not erase in-app history. Your operating system separately controls notification permission and Focus/Do Not Disturb.

Expo's push service and the relevant operating-system push service process device tokens and notification delivery information. For new accounts, detailed notification previews are on by default and can show a person’s public display name or username and their action. You can turn on Discreet lock-screen previews in Settings to omit names and details. Existing accounts retain their saved preview preference. Direct social activity and generation-completion alerts do not wait for app-level quiet hours. Occasional discovery pushes are disabled for the initial beta; if enabled later, they are subject to internal local-time quiet hours and frequency limits. Personal-goals daily encouragement remains disabled.

7. Optional integrations

If you connect Awonder to ChatGPT, the authorized integration can retrieve a limited saved personalization summary and save structured information you explicitly choose to send to Awonder, such as style preferences. It does not import any of your conversation history. You can disconnect the integration through the connected service's controls; disconnecting does not itself erase previously saved information.

This optional ChatGPT connection is separate from Awonder's backend OpenAI API processing. Information used inside ChatGPT is subject to your ChatGPT account settings and that service's policies; the API no-training statement above is not a promise about every use of ChatGPT.

Previously saved information from features excluded from beta, including Body Type analysis, wellness integrations, and personal goals, may remain in your account. Hiding a feature does not delete its data. Account deletion still covers account-owned legacy data. We do not describe those features as active beta functionality.

8. Service providers, website, and security

Resend sends authentication emails and private alerts to our support address when feedback or safety reports are submitted. Authentication emails contain the address and sign-in information needed to deliver them. The support alerts contain a report reference and a link to our restricted queue, not your report text, screenshots, contact details, or diagnostic information. Resend documents US storage and 30-day email/log retention for its standard plans, with a separate seven-day backup window. This is separate from retention of the underlying report and the copy in our support mailbox.

We use Supabase for account authentication, database records and file storage; Render for backend processing; OpenAI for AI processing; and Expo and operating-system services for push delivery. Twilio Verify processes phone verification messages. Apple, Google and the other authentication delivery services process the information needed to sign you in. Support email is forwarded directly through Cloudflare to Gmail. These services receive information needed for their role, not blanket access for other app users.

Our website is hosted through Sites on Cloudflare infrastructure. The current site source has no advertising or analytics scripts and uses email links rather than a public data-entry form. Hosting/security services process web requests and may set security cookies; a Cloudflare bot-management cookie is present. Contacting us by email is separate from merely browsing the site.

We use authenticated access checks, account ownership controls, private storage, and transport encryption. No system is completely secure. Authorized operators can access information when needed for support, safety, and service operation. We may disclose information when legally required or necessary to address fraud, abuse, or threats to rights and safety.

Our primary app database, authentication and photo storage are hosted in Northern Virginia, and our backend is hosted in Virginia. This does not mean all processing stays in the United States. Providers may process information in other countries for AI, email, delivery, security and support. For example, Supabase documents European log processing and global support and content-delivery services. Those countries' privacy laws may differ from US laws. The initial US-only beta is an audience restriction, not a promise of US-only processing.

9. Retention and deletion

Saved account content generally remains until you remove it or delete your account. Some settings and operational records remain while the account exists so that permissions, completed requests, and limits continue to work.

Product telemetry cleanup is configured to remove events older than 90 days; queued client events expire after seven days. Cleanup depends on maintenance jobs running.

Reports are kept for investigation and follow-up. Reports you submitted are removed with your account; reports submitted by someone else are handled separately. Support email is stored separately in Gmail and is not automatically erased by deleting your Awonder account. Contact us to request removal of report or email information; we will consider the request and any continuing safety or legal need.

Our approved retention targets are 90 days after routine feedback or support cases are resolved and 12 months after safety cases are closed. Cleanup requires review, rather than taking place exactly on the expiry date. Unresolved cases and documented safety or legal holds are not eligible; cases with an unknown closure date need review before a retention period can be established. For in-app reports, an automated worker carries out only specifically reviewed and approved cleanup batches, rechecking eligibility before deletion. It does not automatically select every record that reaches the target age. Mailbox cleanup is a separate manual task, not an app feature. Monthly review procedures have been prepared; their ongoing operation has not yet been established. These targets should not be read as a guarantee that existing records have already been removed.

Start account deletion from Profile → Delete account. After identity verification, the service removes account-owned records and access, cleans up associated stored files, and deletes the authentication account. Cleanup can continue in the background and be retried after interruptions. The app confirms completion rather than treating a failed request as successful, and clears the affected account's local data through the deletion flow. Signing out or uninstalling the app is not a request to delete cloud data.

A minimal permanent deletion record remains: an opaque account identifier, a hashed recovery receipt, status/timestamps, and cleanup metadata. It contains no photos, prompts, name, or email and prevents delayed requests from restoring deleted data. Separate minimal records also prevent deleted or moderated content from being restored by stale requests. Other people's independently owned creations can retain an opaque participant reference needed to keep future permission checks safe, without retaining your display handle in that reference.

Backups and logs are separate from the active app database. Our Supabase service makes daily database backups; its current plan provides a rolling seven-day backup window. These database backups do not contain the stored photo files themselves. Supabase's current plan documents seven days for API/database logs, and Render's current workspace plan documents seven days for service logs. These are provider retention windows, not a promise that every copy of your data is erased within seven days. Provider security records, separately retained copies and legal obligations can differ.

Deleting an account does not automatically remove exported copies or information independently retained by providers. OpenAI's retention is explained above. Authentication-message and push providers have their own delivery and security retention. Deleting support email from Gmail also starts Google's separate deletion process; its published policy allows longer backup retention. We do not promise immediate or simultaneous deletion from all provider systems.

10. Your privacy rights

You can review or edit supported profile fields, manage persona and sharing choices, turn off AI processing, control push notifications, remove supported saved content, and request account deletion. For access, a copy of your information, correction, deletion, or another privacy request, contact hello@skymuselabs.com.

Depending on applicable law, you may also have rights to restrict processing, receive portable data, object to certain processing, withdraw consent, and complain to a privacy regulator. Withdrawing consent does not reverse processing already lawfully performed. We will assess requests under the laws that apply and may verify identity to protect the account.

11. Age eligibility

Our initial beta is open to people aged 18 and older. During onboarding, we ask you to confirm that you are at least 18 years old. We save that confirmation with your account. This is a self-declaration, not independent age verification; this step does not ask for a birth date or identity document.

If you believe a child has provided information inappropriately, contact hello@skymuselabs.com so we can investigate.

12. Changes and contact

We will post updates at https://skymuselabs.com/privacy and update the effective date. If a change needs a new permission or additional notice, we will provide the applicable choice or notice rather than treating this policy alone as consent.

SkyMuse Labs New York, United States Support and privacy requests: hello@skymuselabs.com