Loading
Loading
Privacy policy
This policy covers the Drip iOS app, website, waitlist, and related services. It explains the data needed to build a private style memory and the controls you have over it.
Account data: display name, email address, authentication provider identifiers, and secure session records. Passwords are stored only as one-way hashes.
Optional profile data: age, height, weight, preferred units, favorite colors, and favorite styles when you choose to provide them.
Closet and Studio content: item names and attributes, photos you select, prompts, style-check results, receipt outcomes, and feedback.
Service data: request identifiers, timestamps, security and rate-limit signals, crash or diagnostic information, and coarse first-party feature events needed to operate and improve Drip. Drip does not use IDFA or cross-app tracking.
Waitlist data: email, selected style problem, submission time, source page, and campaign or referral parameters included in the page URL.
Drip receives only photos you actively choose through the iOS picker or camera flow. Selected drafts, pending uploads, private preferences, and cached receipts may also remain on your device so the app can recover work and support limited offline use.
Uploaded images are stored in private object storage and linked to your account. Drip may create resized, thumbnail, or analysis-ready copies. Signed image links expire and are used to deliver or analyze the selected content.
When model-backed reads are enabled, Drip may send the prompt, selected images, relevant closet descriptions, and style goals to Drip's private style service and its configured model providers. That processing is used to return the requested style result.
Generated output can be wrong. Do not include sensitive information that is unnecessary for a style check. Provider access is limited to what is needed to deliver and secure the service under the applicable provider terms.
Drip does not sell personal information and does not use your wardrobe for targeted advertising. Data may be processed by vendors that provide hosting, database, object storage, email, security, diagnostics, analytics, authentication, and model infrastructure.
If you choose Google, Telegram, or another enabled sign-in provider, that provider processes the authentication request under its own policy. Drip may also disclose data when required by law, to protect users or the service, or as part of a business transaction with appropriate safeguards.
Account, closet, Studio, and uploaded-photo data are retained while your account is active so Drip can provide private memory and receipt history. Security logs, diagnostics, and backups may remain for limited operational or legal periods before expiring.
Anonymous product-interaction analytics are retained for up to 90 days. They do not contain an account identifier, advertising identifier, email address, wardrobe content, prompts, photos, or result text.
This website counts visits without cookies or any stored identifier: which pages are viewed, for how long, how far they are scrolled, the referring site, and a few clicks such as opening a question or the waitlist. A visitor is counted with a code derived from the network address and browser that changes every day, so visits can’t be linked across days, and the network address itself is never stored. Browsers that send Global Privacy Control or Do Not Track are not counted at all. These records are kept for up to 90 days.
You can delete your account from Profile → Account and Privacy → Delete account. The active account record, related database content, sessions, and stored photo objects are removed. The app also clears local credentials, drafts, cached data, preferences, and pending uploads.
Waitlist records are retained while beta access or product updates are active. Every Drip email has a link to stop further emails; you stay on the waitlist unless you ask to be removed. Email [email protected] to request access, correction, deletion, or help with a privacy right available in your region.
Drip uses access controls, hashed credentials, expiring sessions and signed links, transport encryption in production, and account-scoped data access. No system is perfectly secure, so please use a unique password and report suspected misuse.
Service providers may process data in countries other than where you live. Where required, Drip relies on contractual or other lawful transfer safeguards.
Drip is not directed to children under 13, and we do not knowingly collect their personal data. If local law requires a higher minimum age, use Drip only with the authorization required in your region.
We may update this policy as the product or law changes. Material changes will be identified by a new effective date and, when appropriate, an in-app or email notice.
Privacy questions and product support: [email protected].