Privacy Policy

1. Who we are

AIPEOPLE Private Limited (“we”, “us”, “AIPEOPLE”) operates the Herely mobile application and related services (the “Service”). Herely is a product of AIPEOPLE. We are the controller of personal data processed to run the Service, except where a store or cloud vendor acts as its own controller (for example Apple or Google for in-app purchases, or Amazon Cognito for identity).

We process personal data in line with applicable Indian law, including the Digital Personal Data Protection Act, 2023 (DPDP Act), and other laws that may apply where you live.

Registered office: AIPEOPLE Private Limited, C/O Sheela Rani Srivasta, H. No. 63, Tmsa Marg, Akbarpur, Ambedkar Nagar — 224122, Uttar Pradesh, India.
CIN: U62013UP2026PTC253715
Incorporated: 12 October 2026 (Company limited by shares)

Contact:
Support: support@getherely.com
Privacy: privacy@getherely.com
Product site: https://getherely.com

Related document: Terms of Service.

2. Scope

This policy covers the Herely mobile app, our APIs, and the cloud services we use to authenticate you, store inventory, process images, detect objects, bill subscriptions (when enabled), and email you. It does not cover independent websites or apps we do not operate.

3. Data we collect

We collect only what you give us, what the Service generates while you use it, and what our infrastructure records to keep it working.

3.1 Account and authentication

• Email address (used as your username).
• Password, handled by Amazon Cognito (we do not store your password in our application database in clear text). Accounts are protected by a strong password requirement; we do not offer multi-factor authentication (MFA / authenticator apps / SMS login codes).
• Cognito user id, session tokens (JWT access/refresh), and email verification status.
• One-time email codes only for sign-up confirmation and password reset — not as ongoing login MFA.

3.2 Profile and onboarding

• Display name (full name), place / location name (for example home, shop, or workplace label), optional profile photo.
• Self-reported age in years (to enforce the minimum age of 16).
• Preferred display currency.
• Whether deletion is pending and when the 7-day recovery window ends.

Incomplete onboarding (name, place name, age, currency, local photo path) may be stored on the device until you tap Save.

3.3 Inventory (storages and products)

• Storage names, location / room names, descriptions, and illustration choices.
• Product names, descriptions, notes, categories, quantities, condition, and estimated values you enter or accept.
• Links between products and storages, and counts used for dashboards and valuation reports.

Inventory may relate to a home, shop, lab, small workplace, or similar place you manage. Photos of places or objects can incidentally show people, serial numbers, or other sensitive details if they appear in the frame. You control what you photograph.

3.4 Photos, camera, and gallery

• Images you take or pick for profile, products, and batch detection.
• Compressed JPEG bytes we create on-device before upload.
• Cloud object keys and time-limited pre-signed download URLs for display (including storage-box thumbnails).

Camera and photo-library access is requested only when you start a photo action — not at sign-in. The OS permission dialog is the legal basis for that device access. Denying permission limits photo features; it does not stop email login.

3.5 Object detection (machine processing)

When you use batch or single-item detection, we send the image to our API, which may forward it to an internal detection service (computer-vision / YOLO-style models) to suggest crops, labels, and values. Those outputs are stored as inventory if you save them. Images used only for a detect call may be processed in memory or short-lived storage by that pipeline; saved product images are kept as inventory photos. Detection may be rate-limited when the Service is busy.

3.6 Search

• Search queries you type (products, storages, categories).
• Recent-search terms stored with your account so the Home screen can show them. You can clear them in the app.

3.7 Consent records

When you accept Terms and Privacy at sign-up we record: that you accepted, policy version, source (sign_up), time, app language, and app version. Until the API call succeeds, a pending flag (email + version + time) is kept on the device.

3.8 Subscriptions and payments

We do not collect your full card number. When store billing is enabled, Apple and/or Google process payment. We receive and store what we need to unlock the plan:

• Store product id, platform (App Store or Play), plan code, status, start/end dates, auto-renew flags.
• Google Play purchase tokens and/or Apple transaction ids / signed transaction payloads for verification and restore.
• Payment history shown in the app (date, amount, currency, description, status).
• Whether you previously had a paid plan (used for Free-tier retention after expiry).

3.9 Usage and quota telemetry

To enforce Free / Basic / Premium limits we measure, among other things: cloud image bytes, database bytes for your records, number of storages and products, detection calls used/remaining, product and profile image upload counts, and API call totals (including today / this month and last API access time). This is operational metering, not advertising analytics. The app currently does not embed third-party advertising or analytics SDKs.

3.10 Language and client settings

• App language you choose (English, French, Hindi, Danish, or device default). Sent as Accept-Language so error messages can be localised.
• On-device flags such as connectivity (online/offline UI), local detection-call counters, and paid-downgrade reminders.

3.11 Device information (limited)

We may read OS type/version on the device to choose the correct photo-library permission (Android) or to help developers pick an API host when running against an emulator. We do not use this as an advertising identifier. We do not currently collect precise GPS location. Your place name is a label you type, not a map pin.

3.12 Technical logs and network data

Standard internet processing applies: IP address, timestamps, request path, status codes, and similar logs on our API, load balancers, Cognito, object storage, and email systems. These are used for security, debugging, abuse prevention, and uptime — not to sell profiles.

3.13 Emails we send

• Sign-up confirmation and password-reset codes.
• Data-export ready notices (Free and paid plans), with a time-limited download link.

4. Where data lives (not only S3 and the database)

5. Why we use data

• Provide the Service: create your account, show inventory, run search and valuation, apply plan quotas.
• Photos and detection: store images you add; generate crop/label suggestions you can edit.
• Security: authenticate JWTs, detect stale sessions, rate-limit, investigate abuse.
• Billing: verify and restore store purchases; show payment history (when enabled).
• Legal: record Terms/Privacy acceptance; enforce minimum age; keep invoices as required.
• Support and operations: usage reports, deletion and export jobs, localised messages, maintenance notices.

We do not sell your personal data. We do not use inventory photos for advertising. We do not currently train public generative models on your private photos for third-party ads. If we ever use aggregated or de-identified data to improve detection quality, we will not treat that as a sale of your identity.

6. Legal bases (EEA/UK and similar laws)

• Contract: running the account, inventory, detection you request, and paid plans.
• Consent: Terms/Privacy checkbox; optional camera/gallery; optional profile photo.
• Legitimate interests: security logs, quota metering, fraud prevention, service improvement — balanced against your rights.
• Legal obligation: tax/accounting for paid transactions where applicable; responding to lawful requests.

7. Sharing

We share data only as needed:

• Processors who host or run Herely (AWS and similar cloud, email, detection compute) under our instructions.
• Apple and Google for in-app purchases and restore when billing is enabled; they have their own privacy policies.
• You, when you download an export or open a pre-signed link.
• Authorities if required by law, or to protect users and the Service.
• Successors if the Service is later transferred as part of a business change, with notice where required.

Other users cannot see your inventory. There is no social feed.

8. International transfers

Cloud regions may be outside your country. Herely’s primary cloud deployment is currently in AWS Asia Pacific (Mumbai) — ap-south-1. Where required, we use appropriate safeguards (such as Standard Contractual Clauses) with processors.

9. Retention

• Active account: profile and inventory until you delete them or the account is purged.
• Free plan: inventory may be deleted after 14 days from account creation if you never paid, as shown in the app.
• After a paid plan ends: inventory may be kept about 40 days then purged. Login and payment history may be kept longer for billing and anti-abuse.
• Account deletion: 7-day recovery window after you request deletion; then Cognito user and associated inventory are removed, except records we must keep by law. Billing-related rows may be retained about 180 days after deletion, then removed.
• Export files: generated ZIPs and download URLs expire (typically about 24 hours for the link).
• Images: kept while the related profile or product exists; orphaned objects are cleaned by our jobs where implemented.
• Logs: rotated on a limited schedule (typically about 30–90 days unless needed for a security incident).
• On device: local caches and drafts remain until you clear app data, uninstall, or we overwrite them after sync.

10. Your choices and rights

• Access and update profile and inventory in the app.
• Change language and currency in the app.
• Revoke camera/photos in system settings.
• Clear recent searches.
• Manage or cancel subscriptions in Apple or Google account settings (when billing is enabled).
• Request a data export on any plan, including Free (ZIP via email and in-app download while the account exists or during the deletion grace window).
• Request account deletion (7-day recovery window; restore by signing in and confirming restore in the app).

Depending on your country you may also request access, correction, deletion, restriction, portability, or objection, and you may complain to a supervisory authority. Contact us at privacy@getherely.com or through the Herely app / store listing. We may need to verify it is your account.

11. Children

Herely is not for children under 16 (or the higher minimum shown in the app). We do not knowingly create accounts for younger users. If we learn we have, we will delete them.

12. Security

We use HTTPS, bearer tokens from Cognito, private object storage with short-lived URLs, and access controls on APIs. Sign-in relies on your email and a strong password; Herely does not currently provide multi-factor authentication. No method is perfectly secure. Choose a strong unique password and protect your device.

13. Automated decisions

Detection and suggested values are automated assistance. They do not by themselves produce legal or similarly significant effects. Plan enforcement (blocking extra storages or detections) is automated quota logic based on your usage meters.

14. Changes

We may update this policy. The version on this page is 2026-10-17, matching the version recorded when you accept Terms and Privacy in the app (after we publish that version to the legal API). Material changes will be posted here and, where required, called out in the app for re-acceptance.

15. Contact

Privacy: privacy@getherely.com
Support: support@getherely.com
Website: https://getherely.com
Terms of Service: Terms of Service
Controller: AIPEOPLE Private Limited
Registered office: C/O Sheela Rani Srivasta, H. No. 63, Tmsa Marg, Akbarpur, Ambedkar Nagar — 224122, Uttar Pradesh, India
CIN: U62013UP2026PTC253715