Effective July 15, 2026

Privacy Policy

Yusef Syed operates Tiraz. This policy explains the data Tiraz handles, why it is needed, and the controls available to you.

Data Tiraz handles

Tiraz handles the outfit and closet photos you choose, closet item details, saved outfits, style preferences, outfit context, captions, community comments and likes, an account email and linked Apple or Google identifier when you connect an account, account identifiers, AI allowance records, and purchase-entitlement status.

How data is used

This data is used to provide outfit checks, organize your digital closet, create and save outfits, recover your account, operate included-use limits and paid access, keep the community safe, respond to support requests, and maintain service security.

Service providers and AI

Supabase provides authentication, database, private storage, and server functions. If you choose social sign-in, Apple or Google verifies your login and provides Supabase the provider identifier and account email needed to create, connect, or recover your Tiraz account; Apple can provide a private relay address instead of your personal email. Before each third-party AI feature, Tiraz names the provider, the data being shared, and the purpose, then asks permission. For outfit analysis, the selected outfit photo, occasion, style goals, saved style preferences, and any selected closet-item details are sent through Tiraz and Supabase to OpenAI for the requested rating and explanation. For optional closet suggestions, the selected item photo and current item details are sent to OpenAI for name and tag suggestions. Before community publication, selected outfit images, titles, captions, included item details, or comment text are sent to OpenAI for safety screening. For automatic background removal, the selected closet item photo is sent through Tiraz and Supabase to Replicate to create a cutout. If you decline that required cleanup, the new or replacement closet photo is not saved. RevenueCat and Apple process purchase and subscription status.

AI provider retention

Tiraz sends OpenAI Responses requests with response storage disabled. Under OpenAI's published API defaults, API content is not used to train OpenAI models unless the account opts in. Prompts and responses may remain in abuse-monitoring logs for up to 30 days unless approved shorter-retention controls apply; without Zero Data Retention, Responses prompt caches can retain application state for up to 24 hours, and image inputs can be retained for provider safety review as described by OpenAI. OpenAI's moderation endpoint has no default application-state or abuse-monitoring retention. Replicate states that API prediction inputs, outputs, files, and logs are automatically removed after one hour by default. Provider safety, legal, and account-specific exceptions can apply.

Photo retention

Delete-after-check photos are scheduled for immediate removal from Tiraz storage after processing, including failed checks. To recover a completed outfit result if its network response is lost, Tiraz keeps a private, photo-free operational copy of that result and a one-way digest of the associated storage path for up to 24 hours; a cleanup failure can delay removal until the next cleanup or account deletion. This recovery copy is not customer-visible history. A closet item's private source photo and processed cutout remain until you delete the item or account. Tiraz does not show the uploaded source as closet product imagery while background cleanup is pending or needs a retry. Pro users who choose saved history retain the report and photo until they delete the photo, check, or account. Reports can remain after their photo is deleted.

Community sharing

Closet and outfit data is private by default. When you explicitly publish an outfit, Tiraz creates a separate community copy with short-lived image links. Members with a recoverable Apple, Google, or verified email account may like outfits and publish moderated comments. Public posts and comments use anonymous member labels and do not expose authentication IDs or private closet item IDs. Reports and blocks are private safety actions.

Deletion and privacy choices

Settings lets you delete a retained photo, a saved check, or the full account. Account deletion removes Tiraz account data, private photos, community copies, and active Tiraz sessions. If Sign in with Apple is connected, Tiraz asks for a fresh Apple confirmation and attempts to revoke that sign-in authorization before deleting the account. If Apple cannot confirm revocation, deletion still completes and Tiraz directs you to revoke Tiraz manually in Apple ID settings. You may also contact support about access, correction, or deletion where applicable. Deleting the account does not cancel Apple billing.

Optional product measurement is off

The Tiraz launch build does not transmit onboarding, outfit-check, paywall, purchase, restore, or crash-interaction events for optional product analytics. Necessary account, AI allowance, purchase-entitlement, community-safety, and service-security records are limited to operating the features described in this policy.

No Tiraz training or advertising use

Tiraz does not use customer photos, captions, comments, likes, or reports to train Tiraz models or publish promotional examples without separate, explicit permission. Tiraz does not sell outfit photos or use them for third-party advertising.

Security

Private media uses owner-scoped storage and short-lived signed links. Server credentials are not included in the app. No internet service is risk-free, so crop faces, locations, screens, documents, and other people before upload.

Policy changes

Tiraz may update this policy when its features or data practices change. The effective date shown on this page will be updated, and material changes will be surfaced where appropriate.

Contact

Questions or requests

Email yusefmsyed@gmail.com. Include only the information needed to locate your Tiraz account; never email passwords or full payment-card details.