LooksHive Privacy Policy

Effective date: September 21, 2026
Last updated: October 1, 2026

This Privacy Policy describes how HiveApp Technologies LLC, a Texas limited liability company (“LooksHive,” “we,” “us,” or “our”) collects, uses, discloses, and otherwise processes personal information in connection with LooksHive’s websites, mobile applications, and related services (collectively, the “Service”). We aim to use clear, plain language suited to the people who use LooksHive.

It applies where LooksHive acts as a controller or business (as those terms are defined in applicable privacy laws) of personal information. Where we process personal information on behalf of another party, additional terms may apply.

This Policy should be read together with our Terms of Service.

1. Who we are and contact details

Controller / business name: HiveApp Technologies LLC
State of formation: Texas, United States
Mailing address: 11639 Creek Point Drive, Frisco, TX 75035, United States

General inquiries, support, and privacy requests: [email protected]
Abuse reporting (trust and safety): [email protected]
Copyright / DMCA (U.S.): Use the designated agent and contact details in the Terms of Service — §10.3 ([email protected]).
Transactional mail From address: [email protected] (automated notices only; that mailbox is not monitored for replies).

2. Personal information we collect

The categories below depend on how you use the Service. Not every user will provide every category.

Data minimization. We limit collection of personal information to what is reasonably necessary for the purposes described in this Policy—including providing and securing the Service, meeting legal obligations, and the legitimate uses in later sections—and we retain information only as described in §7.

2.1 Account, Hive identity, and sign-in

LooksHive is part of the Hive network operated by HiveApp Technologies LLC. AlbumHive, VaultsHive, and LooksHive share one Hive identity (the same email and credentials). Signing in to any of those three apps authenticates that identity. SlamHive is a separate product with its own accounts and is not part of this Hive identity, Hive storage meter, or Hive-wide deletion.

Creating an AlbumHive or VaultsHive account does not automatically create LooksHive product data. The first time you sign in to LooksHive with that Hive identity, LooksHive provisions its own wardrobe, credits, and folders. Albums, vaults, and Looks libraries stay in the app where you created them in the current product (no AlbumHive hub of LooksHive Looks).

Shared Hive storage and links. Billable files in AlbumHive, VaultsHive, and LooksHive count against one Hive storage quota, purchased and managed in AlbumHive. LooksHive share-link counts and durations follow that same Hive / AlbumHive entitlement. LooksHive paid packs are try-on / Generate credits and features, not a second storage plan. LooksHive typically meters thumbnails, cutouts, and saved Looks / AI images; full wardrobe and avatar originals are not guaranteed to be retained (see §2.2).

We may collect:

• Identifiers: name, email address, account identifiers, and Buzz Profile fields you choose to provide
• Date of birth — required to finish registration (entered as MM/DD/YYYY and stored as YYYY-MM-DD) to verify that you meet the minimum age and eligibility requirements in our Terms of Service.
• Phone number — optional. Registration (including after Sign in with Google or Sign in with Apple) does not require a phone number. If you add one, it lets people who already have you in their contacts find you, invite you to their Fashion Circles, and share Looks with you. It may also be used for verification (e.g., SMS via Twilio), security, and account-related communications. You can add, change, or remove it in your profile settings.
• OAuth identifiers when you use Sign in with Google or Sign in with Apple: the email and name the provider shares, the provider’s subject / user ID, and short-lived identity or access tokens used only to complete sign-in. We do not receive your Google or Apple password.
• Billing country and related eligibility fields for paid credit packs
• Authentication data: passwords or credentials managed by our authentication flows (we do not store passwords in plain text); OAuth accounts may have no LooksHive / Hive password
• Device and session identifiers (for example, a device ID supplied by the client; LooksHive device slots are independent of AlbumHive and VaultsHive and typically start at five)
• On Android and iOS, device identifiers (for example the Android Advertising ID) may be received by our ad provider as described in §2.8 when ads are shown (non-personalized ads only)
• Profile information you choose to add (such as display name or optional profile photo). Optional registration / profile photos, where offered, may be stored on the shared Hive identity path rather than as wardrobe artifacts

2.2 Photos, Looks, and related media (“User Content”)

• Images you upload (Avatars, wardrobe garments, Scenes) and Looks you generate
• Seed / starter wardrobe images we provide (those are our content, not yours)
• Derived files created to operate the Service, such as thumbnails, cutouts, preview assets, and similar
• Metadata associated with media (for example filenames, timestamps, folder structure, contributor attribution)
• Comments you post on Wardrobe items shared with you or by you (text, your display name, and time). They are visible to people who can see that item, the item owner is notified with a preview, and they are kept until you, the item owner, or a moderator deletes them, or the account is deleted

Originals. LooksHive is designed so that wardrobe and avatar originals are not kept as a durable archive. We typically keep HOT thumbnails, cutouts, and full saved Looks / AI images. LooksHive is not a backup service. Keep your own originals.

2.3 Hive Help, Generate, Trends, Lens, safety, and public LLMs

Sensitive / personal data and public LLMs. Several LooksHive features use a third-party / public large language model or other third-party AI (for example OpenAI for Hive Help, safety thumbs, folder Classify, and Trends structuring; FASHN or a successor for fashion Generate). You control what is sent for generative / analysis AI (Generate, Hive Help prompts, Trends, Lens / shopping searches). LooksHive does not send your wardrobe or Looks to those generative features on its own.

LooksHive is not PCI, HIPAA, or similarly certified. Do not use the Service as a system of record for payment-card, protected-health, or other regulated data. Do not upload photos you are not allowed to process, and do not enter sensitive personal information in Hive Help or Trends prompts.

• Wardrobe search: search queries you enter and indexing outputs used to power search — such as embeddings or similar vectors, labels, and related technical representations — processed in LooksHive’s infrastructure unless we tell you otherwise in-product. LooksHive search is not face or people search
• Generate / Try On / Live Look / Scene It (FASHN or successor): When you start a generate job, we send the images you selected (avatar, garments, scenes, looks) to the fashion AI provider to produce a Look. Vendor safety filters may refuse a job before it finishes
• Hive Help (how-to chat): answers LooksHive product questions. As of the Last updated date, LooksHive does not send your wardrobe photos or other stored User Content to OpenAI for Hive Help. We do not intend to attach account personal information to Hive Help API requests. Only what is strictly necessary is transmitted (for example, user-typed prompt text). Your prompts are processed by OpenAI; do not enter sensitive personal information in Hive Help prompts. The app displays this notice on the Hive Help screen
• Trends: When you open or query Trends, we may send region / query text you chose to SerpAPI (Google Trends / shopping / images) and, where implemented, to OpenAI to structure fashion cards. We do not intend to attach account personal information to those requests
• Lens / visual and nearby shopping: When you run a Lens or shopping search, we may send the image or query you chose to SerpAPI. For nearby results, if you allow the device location permission, the app sends your precise device location (latitude/longitude, plus the city/region label your phone derives from it) with that search to SerpAPI; we use it only for that search and do not store it. You can deny location; nearby results are then unavailable and other shopping still works. Merchant URLs may be wrapped through Sovrn (affiliate redirect) before we show a purchase link
• LooksHive image safety (OpenAI Moderation API): When you save a new Avatar, wardrobe item, Scene, or generated Look, LooksHive may send a downscaled thumbnail (not the full original) to OpenAI’s Moderation API so we can refuse pornographic or explicit images before durable store. We do not attach account identifiers to that request. Fashion, swimwear, and lingerie are in-product; a private refuse is not a compliance strike. This safety gate is not optional “AI analysis” of your wardrobe
• Folder Classify (cloud environments): On Google Cloud hosted environments, ad-hoc Try On garment photos may be sent as a thumbnail to gpt-4o-mini only to suggest a clothes folder. Linux-box environments may use an on-box vision model for the same folder-id task. Classify is not the safety gate
• Model training (vendor): We do not permit the AI vendor to use submitted data for model training where such controls are available through the API and our account configuration. The vendor’s own terms describe how they may process, cache, or retain API traffic
• AI application logs: We do not design the Service to retain a long-lived LooksHive chat transcript of every Hive Help call for marketing analytics. We may store Looks, folder labels, Trends session fields, and product-operation records. Incidental debug, infrastructure, or security telemetry, and processing/retention by vendors under their terms, may still occur

2.4 Communications

• Transactional emails (welcome, security alerts, billing notices, share notifications, account and deletion notices) sent via providers such as Zoho Mail from [email protected]. That address is a send-only From line; replies are not read. Write [email protected], [email protected], or [email protected] as appropriate
• SMS or voice messages sent via Twilio (or similar) for phone verification
• Support messages when you contact us
• Push notifications on iOS and Android when you grant permission: a device push token (via Expo Push, Apple Push Notification service (APNs), and/or Firebase Cloud Messaging (FCM)) so we can deliver social, share, billing, security, and similar alerts while the app is in the background or not running. Web does not use the same OS push path. You can refuse or later disable notification permission in system settings; we then stop using that token

2.5 Payment information

LooksHive may use Stripe, Apple, and/or Google Play for one-time analysis / try-on credit packs, depending on how and where you purchase.

Stripe (web). Card and bank data are generally collected and processed directly by Stripe subject to Stripe’s privacy policy. LooksHive typically receives limited billing metadata (such as payment status, partial card details, billing address fragments, and transaction references).

Web and mobile apps. Paid items may be purchased and managed:

(a) on the web through Stripe (for example at https://app.lookshive.com); and/or
(b) in the iOS and/or Android apps through Apple App Store and/or Google Play in-app purchases, where that option is offered in-product.

• Stripe: Card and bank data are generally collected by Stripe; LooksHive receives limited billing metadata.
• Apple / Google: Payment is processed by Apple or Google under their terms and privacy policies. LooksHive receives purchase status and related entitlements (for example product identifiers, transaction references, and credit-grant signals), not full payment card numbers.

Which store or processor applies depends on how and where you purchase. Managing or requesting a store refund may require using Apple or Google tools as well as (or instead of) LooksHive.

Hive storage upgrades purchased through AlbumHive are processed under AlbumHive’s billing surfaces and privacy disclosures; LooksHive may receive entitlement / meter signals needed to enforce shared Hive storage.

2.6 Technical and usage data

• IP address and derived approximate location (for example, country via GeoIP for security notifications and fraud prevention)
• Precise device location — only when you allow it for nearby shopping (see §2.3); sent with that search and not stored
• User agent, browser or app version, operating system, language preferences
• Logs and diagnostics: timestamps, request paths, error reports, performance metrics
• Cookies and similar technologies on web surfaces, where used (see Section 8)

2.7 Abuse reports and safety

When you use Report or similar flows on shared links, we may collect:

• Report content (description, category, and related fields)
• Optional file attachments you choose to upload
• Identifiers tying the report to the Look, collage, share link, media item, or comment
• Reporter technical data such as hashed IP, user-agent, and optional contact email you provide
• CAPTCHA signals (for example, Cloudflare Turnstile tokens) to reduce automated abuse

Routing. In-product Report submissions are routed by issue type: Abuse to [email protected]; Copyright / IP to [email protected]. For other communications, use [email protected].

We generally do not notify the content owner that a report was filed only because a report was submitted, unless required by law or in specific enforcement situations.

2.8 Advertising (AdMob) and device advertising identifiers

Free LooksHive (and leftover free/trial credits before any paid ads window) may show third-party ads (currently Google AdMob inline banners in the iOS and Android apps). Web may show Google AdSense in the same page slots when that surface is enabled. We do not use your wardrobe photos as an advertising product.

Who sees ads. Ads are per app. A paid LooksHive credit pack can hide ads in LooksHive only, and only while both are true: (1) the ads-free date (lk_ads_free_until) is still in the future, and (2) your credit balance is greater than zero. Ads-free windows are 2 months (Starter), 4 months (Plus), or 6 months (Value) from that paid purchase. A later paid pack extends the date using max(existing date, new purchase + window) — it never shortens an existing date. Ads return on whichever happens first: that date, or your credit balance reaching zero. AlbumHive storage plans do not remove LooksHive ads. VaultsHive packs do not remove LooksHive ads. Free / admin / promo grants do not start an ads-free window.

Data used for ads. LooksHive shows non-personalized ads only. When ads are shown, Google AdMob (and AdSense on web, if enabled) may receive device identifiers (for example the Android Advertising ID or an app-level identifier on iOS), IP address, user agent, approximate location (for example country), app and placement identifiers, and ad performance signals, which Google uses to serve and measure ads and to prevent fraud. We do not request App Tracking Transparency permission on iOS and do not use your data for personalized or cross-app targeted advertising. Users known to be under 18 are not treated as an audience for targeted advertising (see §11).

Sale / sharing. We do not sell personal information for money. Because LooksHive shows non-personalized ads only, we do not share personal information for cross-context behavioral advertising under the CCPA/CPRA. See §8.1 and §10.2. We do not sell your private User Content.

Android AD_ID. The Android app includes the Advertising ID permission both for AdMob and because Google Play Billing and related Play libraries may declare it.

2.9 Trust and safety processing (automated and manual)

LooksHive may use automated analysis of User Content and derived metadata to detect abuse, enforce policies, and prioritize human review, including:

• OpenAI Moderation on new LooksHive images before durable store (wardrobe, avatar, scenes, generated Looks), as described in §2.3. A private refuse does not create a compliance strike
• CLIP-style embeddings or similar signals for search and internal triage
• Manual review by authorized personnel when investigating reports

Automated signals may not be the sole basis for account-level enforcement; human review may apply depending on the product workflow.

2.10 Legal and compliance

• Records required for tax, accounting, billing disputes, or regulatory obligations
• Preservation of information subject to legal holds or lawful requests

2.11 Device contacts (optional)

If you allow Contacts permission on iOS or Android, LooksHive uses it only when you choose to search your contacts to add people to a Collaboration Group. The app searches your device contacts on your phone and sends only the last seven digits of the matching phone numbers to our servers to find people who already have a Hive account. We do not upload or store your contact list or those partial numbers.

When you add a registered user from the results, we store that person as a member of the group (their Hive account ID and the phone number on their account) so sharing works. You can remove members at any time, and you can decline or later withdraw Contacts permission in system settings — searching by phone number still works without it. LooksHive never writes to or changes your device contacts.

3. How we use personal information

We use personal information to:

1. Provide and operate the Service (hosting, Hive authentication including email/password and Sign in with Google / Apple, wardrobe, Generate, sharing, collaboration, Trends, Lens, push and email notifications)
2. Process payments and grant credits (via Stripe on the web and/or Apple / Google Play in-app purchases where offered; see §2.5)
3. Communicate with you (service-related email from [email protected], SMS, and push when permitted; marketing only if you opt in where required)
4. Verify phone numbers and protect accounts (via Twilio or similar)
5. Deliver AI and shopping features — Generate via FASHN (or successor); Hive Help, safety thumbs, Classify, and Trends structuring via OpenAI; Lens / Trends / shopping via SerpAPI; affiliate wrapping via Sovrn — only as described in §2.3
6. Maintain security (fraud prevention, abuse detection, session limits, rate limits, logging)
7. Enforce our Terms, including moderation and compliance strikes
8. Comply with law and respond to lawful requests
9. Improve the Service (analytics, debugging, product development), consistent with applicable law and your choices
10. Show ads on Free LooksHive / when the ads-free window is not in effect, as described in §2.8

4. Legal bases (EEA, UK, and similar jurisdictions)

Where GDPR or similar laws apply, we rely on one or more of the following:

• Contract: processing necessary to provide the Service you request
• Legitimate interests: security, fraud prevention, product improvement, moderation, and analytics (balanced against your rights)
• Legal obligation: compliance with law
• Consent: where required (for example, certain cookies or marketing, or Generate / optional features where we ask explicitly)

You may withdraw consent where processing is consent-based, without affecting processing prior to withdrawal.

5. How we share personal information

We do not sell personal information for money. We do share information with service providers and, when Free LooksHive shows ads, with Google AdMob / AdSense as described in §2.8 (non-personalized ads only, which is not “sharing” for cross-context behavioral advertising under the CCPA/CPRA). We do not sell your private User Content. When you run Generate, Hive Help, Trends, or Lens, we share the images or query text you chose with those vendors as described in §2.3. Safety thumbs may be sent to OpenAI Moderation when you save new images.

5.1 Service providers (subprocessors)

We use third parties that process personal information on our behalf or receive it to deliver the Service, including:

We may update our list of service providers from time to time. Material changes will be reflected in this Policy (including the Last updated date at the top of this document). Links to each provider’s privacy policy are available on their official websites.

5.2 Legal and safety

We may disclose information if we good-faith believe it is necessary to:

• Comply with law, regulation, legal process, or government requests
• Protect safety, rights, or property of LooksHive, users, or the public
• Detect, prevent, or address fraud, security, or technical abuse
• Enforce our Terms or policies

This may include CSAM reporting or preservation where applicable law requires.

5.3 Business transfers

If LooksHive / HiveApp Technologies LLC is involved in a merger, acquisition, financing, or sale of assets, information may be transferred as part of that transaction. We will require the successor to honor this Policy or notify you of changes.

6. International transfers

LooksHive’s operator is based in Texas, United States. We currently process and store personal information in the United States in systems operated by us or our service providers. LooksHive does not commit to EU-only or other single-jurisdiction residency unless we explicitly offer a specific product or region in the future.

Where personal information is transferred across borders and required by law (for example, EEA/UK), we implement appropriate safeguards such as Standard Contractual Clauses or equivalent mechanisms when applicable.

7. Data retention

We aim to minimize retention and delete personal information when it is no longer needed for the purposes described in this Policy, consistent with legal, safety, and legitimate business requirements. In practice, we retain information as long as needed to provide the Service and for those purposes, including:

• Account records and credentials — While your Hive account is active or suspended (deactivated) in-product, we retain identifiers and authentication-related data (for example, hashed passwords and OAuth provider subject IDs) needed to operate the Hive identity. Suspension is per app only: you can suspend LooksHive and still use AlbumHive or VaultsHive (and the reverse). Hive storage stays available so the other apps can keep working. AlbumHive share-link entitlements stay with the Hive storage plan. Suspension is not Hive-wide deletion. Unused LooksHive credits are not refunded on suspend; they remain until each lot expires.
• Voluntary complete account deletion — After you follow the in-product Delete account flow in AlbumHive, VaultsHive, or LooksHive (including the acknowledgement checkbox described in our Terms of Service), deletion is immediate and Hive-wide: it removes the single Hive identity and cascades deletion of your data in AlbumHive, VaultsHive, and LooksHive (where used). SlamHive is not deleted. Deletion removes your wardrobe items, Avatars, Scenes, Looks, comments, collages, share links, Fashion Circles / groups, credits (forfeited, non-refundable), OAuth links, and push tokens, and removes your membership from Looks and groups where you were a contributor or invitee. Files you contributed to another user’s Look or collage may remain; attribution may show as “Unknown.” You are responsible for cancelling recurring billing in Stripe, Google Play, and the Apple App Store; any cancel we attempt is best effort only and does not stop Apple (and may not stop Stripe or Play). LooksHive credit packs are one-time; there is typically no LooksHive monthly subscription to cancel, but AlbumHive storage or other Hive store items may still bill you if you do not cancel them. Deletion may take time to propagate and may be subject to technical or backup retention for a limited period, and we may retain certain records where law, safety, or legal process requires (for example, abuse reports, billing, or tax records).
• Analysis / try-on credits — Credits are granted as lots. Each paid (or free-trial) grant expires 12 calendar months after that grant. Spend is FIFO (soonest-expiring lot first). When a lot’s date hits, that lot goes to 0; later lots keep their own dates. The date shown in-product is typically the soonest remaining lot.
• Push tokens — Retained while the device is registered; removed on logout, token rotation, permission withdrawal, or account deletion
• User Content — You may be able to delete or remove certain User Content through in-product controls where available. Removed items may persist in technical or backup systems for a limited period (typically short-term rolling deletion). LooksHive is not a backup service. Wardrobe / avatar originals are typically not retained.
• Billing records for periods required by tax and accounting law
• Stripe webhook logs or similar operational records for fraud and reconciliation for a limited period
• Report and moderation records as needed to investigate, audit, and defend claims, subject to law
• Expired share link metadata may be deleted after extended periods (for example, after one year in expired state in some cases) per system hygiene

In-app notifications may be purged after a limited period (for example, 90 days, where implemented).

8. Cookies and similar technologies

We use cookies, local storage, and similar technologies on web surfaces, for example to:

• Keep you signed in
• Remember preferences
• Secure public forms (e.g., CAPTCHA)
• Measure performance and usage (if enabled)

Where required by law, we will obtain consent before non-essential cookies.

8.1 Global Privacy Control and Do Not Track

We honor Global Privacy Control (GPC) signals where required by law. Depending on jurisdiction and product surface (for example, web browsers that send a valid GPC signal), we apply GPC in line with applicable rules (including, where applicable, California requirements to treat GPC as an opt-out of sale or sharing for cross-context behavioral advertising, to the extent those concepts apply to our processing).

Do Not Track (DNT). The legacy Do Not Track browser setting is not consistently standardized across browsers and services. We do not guarantee a specific response to DNT signals alone; where you seek to exercise opt-out rights that GPC can signal under applicable law, we prioritize recognized mechanisms such as GPC as described above.

9. Security

We implement technical and organizational measures appropriate to the risk, including:

• Encryption in transit (for example, TLS/HTTPS) between clients and our services
• Access controls and authentication for administrative systems
• Presigned URLs or equivalent time-limited access to stored objects where designed for private files
• Server-side encryption for object storage and databases as provided by our vendors (for example, Cloudflare R2, MongoDB Atlas)

No method of transmission or storage is 100% secure. You use the Service at your own risk. Sending images or prompts to a public LLM or fashion AI has additional residual risk described in §2.3.

Breach notification. In the event of a data breach, we will notify affected users and regulators as required by applicable law.

10. Your rights and choices

Depending on your location, you may have rights to:

• Access personal information we hold about you
• Correct inaccurate information
• Delete certain information (subject to exceptions)
• Export or port information in a machine-readable format
• Object or restrict certain processing
• Withdraw consent where processing is consent-based
• Opt out of sale or sharing for cross-context behavioral advertising (CCPA/CPRA concepts) if applicable

Data export and portability. We provide data exports in a structured, commonly used format where feasible, consistent with applicable law, technical limits, and security review. To request an export, contact [email protected].

Account deletion and erasure requests: Depending on your jurisdiction, you may have a right to delete or erase certain personal information. LooksHive provides self-service complete account deletion for eligible accounts through the in-product flow described in §7 and the Terms of Service. That wipe is Hive-wide (AlbumHive, VaultsHive, LooksHive). Suspend is different: it is per app and keeps Hive storage for the other apps. You must cancel Stripe, Google Play, and App Store subscriptions yourself; our billing cancel is best effort. Unused credits are forfeited. Accounts subject to compliance suspension or other restrictions may require support review.

How to exercise: Contact [email protected]. We may need to verify your identity before responding. You may appeal a decision where applicable law requires.

Authorized agents: Some jurisdictions allow authorized agents to submit requests; we may require proof of authorization.

10.1 EEA/UK rights

If you are in the EEA or UK, you may lodge a complaint with your local supervisory authority (for example, a Data Protection Authority).

10.2 California residents (CCPA/CPRA summary)

If you are a California resident, you may have additional rights under the CCPA/CPRA, including:

• Right to know categories and specific pieces of personal information collected
• Right to delete personal information
• Right to correct inaccurate personal information
• Right to opt out of sale or sharing of personal information — we do not sell personal information for money; Free LooksHive shows non-personalized AdMob / AdSense ads only and does not share personal information for cross-context behavioral advertising (see §2.8); we do not use or disclose sensitive personal information for targeted advertising to known minors as described in §11; Global Privacy Control (GPC) is addressed in §8.1

Sensitive personal information: We use sensitive personal information only as permitted by law and as described in this Policy. You decide whether a photo that contains sensitive data is uploaded or sent to Generate, Hive Help, Trends, or Lens.

Non-discrimination: We will not discriminate against you for exercising CCPA rights.

11. Children and teens

The Service is not directed to children under 13, and we do not knowingly collect personal information from children under 13 without verifiable parental consent where the law requires it.

Age brackets. For minors who use the Service where permitted by law, we may categorize protections by age band—for example Children (under 13), Young Teens (13–15), and Older Teens (16–17)—to apply privacy protections required in California, Utah, the EU, and other jurisdictions as they apply to our Service.

Practices for users under 18. For users known to be under 18, we do not engage in targeted advertising, profiling for solely automated decision-making that produces legal or similarly significant effects, or the sale of personal information without the opt-in consent required by law.

Data minimization for minors. We collect only the minimum personal information needed to provide the Service. We do not store precise geolocation for any user. Nearby shopping uses precise device location only after the user grants the device location permission, sends it with that one search, and does not keep it; teens can decline and still use the rest of LooksHive.

Account registration is subject to the age and consent rules in our Terms of Service. If you believe we have collected information from a child in violation of this Policy, contact [email protected].

12. Automated decision-making

LooksHive may use automated analysis of User Content and metadata for safety, search, folder Classify, and internal triage. Generate, Hive Help, and Trends use third-party models under the limitations in §2.3; they are not used to make solely automated legal decisions about your account. Automated outputs may be incorrect; do not rely on them as definitive determinations of lawfulness, medical, legal, or financial facts. Generated Looks are fashion visualizations, not a guarantee of fit, color, or merchant availability.

Where solely automated decisions with legal or similarly significant effects are restricted in your jurisdiction, LooksHive will comply with applicable requirements.

Your rights. You may request human review of decisions affecting your account (for example, enforcement or access decisions). Contact [email protected].

13. Third-party links and viewers

The Service may include links to third-party sites (including merchant and affiliate shopping links) or allow viewers to access shared Looks without a LooksHive account. Those third parties have their own privacy practices. LooksHive is not responsible for third-party sites, prices, or products.

14. Changes to this Policy

We may update this Policy by posting a revised version and updating the “Last updated” date. For material changes, we will provide additional notice where required by law (for example, email or in-app notice).

15. Contact

Privacy questions, general support, and data rights requests: [email protected]
Abuse reporting (trust and safety): [email protected]
Copyright / DMCA: [email protected] (see the Terms of Service — §10.3)
Do not reply to automated mail from [email protected] — that mailbox is not monitored.

Legal notices

Operator: HiveApp Technologies LLC — 11639 Creek Point Drive, Frisco, TX 75035, United States.

© 2026 HiveApp Technologies LLC. All rights reserved. LooksHive is a trademark of HiveApp Technologies LLC.

Document version 1.0 — Effective September 21, 2026 (Hive identity; OAuth; AdMob ads window; push; public LLM under user control; FIFO 12-month credit lots; user-owned store cancels; SerpAPI / Sovrn; mailboxes; non-personalized ads only, no ATT; device contacts §2.11; nearby-shopping precise location not stored — updated September 29, 2026)