Privacy Policy

Ruffle Privacy Policy

Effective date: November 14, 2026

Ruffle provides wardrobe, styling and outfit-feedback features. This policy explains what data we collect, how we use it, how we protect it, and how users can request deletion.

Developer and Contact

Ruffle is operated by Next Pebble. For privacy questions or data requests, contact snggyu.lee@gmail.com.

Data We Collect

City Weather and Daily Styling

You choose a city whose forecast you want to use. Ruffle does not request GPS or calendar access for daily styling. The selected city is saved to your account and sent to Ruffle's backend. Our backend requests shared city-level forecasts from MET Norway without forwarding your Firebase identity or device IP address. Forecasts are estimates and may differ from conditions in your neighborhood. Weather data is attributed to MET Norway under CC BY 4.0. Daily styling settings, caches and wear/skip records are removed when you delete your account.

Optional Service Improvement Measurement

You can choose to help improve Ruffle in your profile. This is off by default. If enabled, we record app visits and actions such as uploads, recommendations, try-ons, saves, and outfits marked as worn, together with account and session identifiers and action times. We use these records to understand use and failures. They do not include photos, full AI inputs, typed text, advertising identifiers, GPS coordinates, or session recordings.

These records are kept for 30 days. Turning the setting off stops collection and deletes the existing optional records. Account deletion removes them too. Routine cleanup may take additional time to remove expired records.

AI Activity and Quality Review

We keep private AI request records, such as processing status, model version, timing, usage, and a reference to the result, to run and troubleshoot AI features. These records are normally kept for 30 days and are separate from optional service improvement measurement. Quality feedback is used to investigate the reported issue. Uploaded photos are not automatically added to Ruffle model training or reusable evaluation datasets.

How We Use Data

Service Providers

We use Google services, including Firebase, Google Cloud Storage, Firestore, Google sign-in, and Vertex AI, for authentication, hosting, storage, clothing analysis, and AI processing. We also use OpenAI for outfit recommendations and image generation.

AI requests include the information needed for the feature. Clothing analysis uses uploaded clothing or outfit photos. Image generation uses selected person, clothing, or reference photos and instructions. Recommendations use clothing details and relevant styling information, such as age, sex, weather, occasion, and saved or worn outfit preferences.

Our primary app database and photo storage are in South Korea. Authentication and AI providers operate internationally, including in the United States, so data may be processed outside your country over encrypted connections when you use these features. Provider handling and retention are described in the OpenAI API data controls and Google Cloud AI data governance. Providers may retain limited data for security and abuse prevention under those policies. We do not sell personal data.

Sharing

We share data only as needed to provide app functionality through our service providers, comply with law, protect users and the service, complete a user-requested support or deletion process, or carry out a sharing action you choose. Your photos and saved looks are private by default.

Look Poll Links

You may choose looks to share through a poll link. Anyone with the link can view those looks until the link expires or you close it; they can forward the link or save a copy that Ruffle cannot recall. Messaging services may fetch the selected images for link previews and retain cached copies. Closing a link stops future access but cannot recall those cached previews. Links expire seven days after creation. A link refers to saved content, so a look may change or become unavailable if the underlying content is changed or removed.

Recipients can view and vote without an account. A random browser identifier lets us record and update a guest choice. Recipients may sign in with Google or email to save participation history to their Ruffle account; the account choice replaces their guest choice. The voting page does not show account names or email addresses. An optional nickname, if supplied, is visible only to the creator. Necessary browser session storage keeps the choice and sign-in session; it is not used for advertising.

Public poll and participation records expire seven days after the link is created and are removed by routine cleanup. Closing a link stops public viewing and voting. The creator can keep private results containing the selected look references, vote totals, and dates until deleting the result or their account. These saved results do not retain voter identifiers or nicknames, and do not create separate copies of the photos. Saved photos and looks remain in their owner's library until deleted.

Mutual Outfit Ratings

If outfit ratings are enabled in your version, you can choose a saved outfit or completed fitting image to show to other signed-in participants. Your wardrobe, profile and fitting inputs are not shared automatically. Before publication, you preview the selected image and confirm that you want to share it. A fitting result can include a face or body; review the entire image and only publish content you have permission to share.

Published entries are available for up to seven days unless withdrawn earlier or made unavailable. Other participants can rate the outfit from one to five. We use account identifiers to prevent self-rating and duplicate ratings; participants are not shown another user's email or account ID. Your rating totals and average are available to you. Withdrawing an entry stops new viewing and ratings. It cannot recall screenshots someone has already taken.

You can report an entry or block its creator in the app. Reports contain the entry reference, reason and reporting account so that the issue can be reviewed. Blocking uses account identifiers to hide entries between the two accounts. These records are private and are not shown in the rating feed. Account deletion also removes associated rating data through the account-erasure process. Limited security or legally required records follow the retention exceptions below.

Security

Data is transmitted over encrypted connections. User images and metadata are stored in access-controlled Firebase and Google Cloud resources. Signed upload and download URLs are time limited where used.

Retention and Deletion

Account, profile, wardrobe, and generated image data is retained while the user keeps an active Ruffle account. Users can delete their account from the app profile screen or request deletion through the account deletion page. Deletion removes the account record and associated app data, including saved looks, images, and the creator's poll results. Cleanup can continue in the background to finish interrupted deletion and remove late uploads. Our photo storage keeps recoverable deleted copies for seven days before permanent removal. Votes and totals in someone else's poll follow the poll retention periods described above. Limited security, deletion, backup, or legally required records may remain for their applicable retention periods; provider records follow the policies linked above.

User Choices

Age Eligibility

Ruffle is currently intended for adults aged 18 and older. Do not upload photos of minors for AI fitting. If you believe a minor has provided personal data, contact us so we can review and delete it.

Changes

We may update this policy as the app changes. The effective date above will be updated when material changes are made.