Last updated: October 3, 2026
This policy explains what the Hingr mobile app and the hingr.ai website collect, why, and what you can do about it. Hingr is made by Hingr ("we", "us"). It is written to be read, not skimmed — if anything is unclear, ask us.
In short: we collect what the app needs to work and nothing else. There are no ads and no analytics trackers. Photos and voice notes sent to the AI features are processed to answer you and are not kept; a profile photo, if you add one, is kept until you remove it. You can export or delete everything from Settings, or from
this page without the app.
1. What we collect
Information you give us
- Account: your name, email address, a password (stored only as a one-way hash), and an optional username. If you sign in with Google, we receive your name, email address and profile picture URL from Google; we never see your Google password.
- Company and team: the company or team name a manager sets, your role on it (manager or technician), the apprentice flag a manager may set, and the trade you pick when you first sign in.
- Two-factor authentication, if you turn it on: an authenticator secret and hashed backup codes.
- What you ask: the text of your Assist conversations and code checks, the devices you look up, favourite, and export, the wiring plans you request, the products you pin, and the ratings and corrections you submit.
- Profile photo, only if you add one: we keep one small square copy (at most 512 pixels a side), saved again as a new JPEG so nothing of the original's metadata, such as where or when it was taken, is kept. Only you and the people on your team see it. Replacing or removing it deletes the old one, and it is deleted with your account. It is never sent to an AI provider.
- Photos and voice notes you choose to send for identification, installation review or dictation — see AI processing.
- Your door checklist: the items you add, reword or reorder, your ticks, and the site line you type or fill in.
- A site address, only when you ask for one. Share location and the checklist's site line can read your phone's position once, at the moment you tap Use my current location, to fill in the street address. You can edit it before it goes anywhere. It goes only where you send it: into the conversation or the checklist (kept like the rest of them), or into a text you send yourself. We keep no record of where you were.
- Messages you send through the contact form or by email.
Information created as you use the app
- Usage events: which features you used and when (a device lookup, an Assist session, a photo identification, a wiring plan, a Learn topic). Managers see a per-person count of these for their own team. We use them for the daily quotas, the team's activity view and to understand which parts of the app matter.
- AI metering: how much AI capacity each request used and its cost, so the per-team monthly allowance and the daily quotas can be enforced.
- Notifications delivered to your in-app feed, and whether you have read them.
- Sign-in sessions: a token for each device you sign in on (stored hashed), its label and last use, so you can see and end them.
- Technical logs on our server: request paths, timestamps, IP addresses and error details, used for security and to keep the service running.
What we do not collect
- No location tracking. The app never follows your position and never reads it in the background. It reads it once, only when you tap Use my current location, and keeps no location history.
- No contacts, files, calendar or messages from your phone.
- No advertising identifiers and no analytics or crash-reporting SDKs. The app contains none.
- No payment card details. Payment happens on our processor's page; we never receive your card number.
2. How we use it
- To provide the service: sign you in, show your team its catalogue, answer your questions, keep your conversations, and deliver notifications you have not turned off.
- To run your subscription: apply the plan, count seats, enforce the trial, the daily quotas and the monthly AI allowance, and show invoices.
- To keep the service safe: rate limiting, abuse prevention, security investigation.
- To improve the catalogue and the answers: the corrections you report, the ratings you give and the photos the app could not identify tell us where the data is thin. This is reviewed by people; nothing trains a third-party model on your data.
- To contact you about the service — verification codes, password resets, trial and billing notices, and replies to your messages. We do not send marketing email without asking first.
3. AI processing
Assist, Snap & ID, installation review, code check, wiring plans and voice notes are produced with models from OpenAI. When you use one of these features, the relevant content — your question, the retrieved documentation passages, the photo you took, or the audio you recorded — is sent to OpenAI's API to produce the answer.
- Photos for Snap & ID and installation review are sent to produce the identification or review and are not stored by us afterwards. We keep the outcome (which device was matched, or that none was, and any correction you make), not the image.
- Dictation and voice mode turn your speech into text with your phone's own speech recognition (Apple's on iPhone, Google's on Android). The words appear as you speak, and only the finished text is sent to us. On a phone without speech recognition, the microphone records a voice note instead.
- Talking over a spoken answer: while voice mode reads an answer aloud, the microphone stays open so you can interrupt it. The listening is done on the phone by the app itself, and nothing it hears leaves the phone unless you talk over the answer. Then the few seconds you said are sent to us as audio, transcribed like a voice note, and the audio is discarded. Tapping Interrupt still works, and on a phone that cannot cancel its own voice the answer plays as before, with the microphone closed.
- Voice notes are transcribed and the audio is discarded; the transcript is what you see and what is sent on.
- Spoken replies are read by your phone's own voice (Apple's or Google's text-to-speech, built into the phone), so the answer text is not sent anywhere to be read. Only on a phone with no voice for the language is the answer text sent to OpenAI to make the audio, which is not tied to your account.
- Requests are sent under our API agreement with OpenAI, which does not use API data to train its models. OpenAI's own privacy policy applies to its processing.
AI answers can be wrong. They are a reference to be checked against the manufacturer's documentation and the local authority, not a substitute for either.
4. Who else sees your data
We do not sell personal data, and we do not share it for advertising. We share it only with providers we need to run the service, each bound to use it solely for that purpose:
| Provider | What it receives | Why |
|---|
| OpenAI | Questions, retrieved documentation, photos and audio you send to AI features | Producing the answers, identifications, reviews and transcripts, and spoken replies on a phone with no voice of its own for the language |
| Creem | Your email, the plan you chose, and the payment details you enter on their page | Payment processing and subscription billing. We receive the subscription status and invoices, never your card number |
| Resend | Your email address and the content of the message | Delivering verification codes, password resets and service notices |
| Google | Only if you choose "Continue with Google": the sign-in itself | Authentication. Google shares your name, email and picture with us; we share nothing with Google |
| DigitalOcean | Everything, at rest and encrypted in transit | The servers the service runs on |
| Apple or Google, through your phone | Your speech while you dictate or use voice mode, the answers it reads aloud, and your position when you ask for the site address | Speech recognition, text-to-speech and address lookup built into iOS and Android. Your phone sends these under its own terms with Apple or Google; we send them nothing |
Within your team, everyone sees each member's profile photo, if they added one, and managers can see members' names, roles, when they were last active and their weekly activity counts. Other teams see nothing of yours. We may also disclose information if the law requires it, or to protect the rights and safety of users and the service.
5. How long we keep it
| Data | Kept for |
|---|
| Account, team, favourites, conversations, wiring plans, picks, your checklist | Until you delete them, or delete your account |
| Usage events | 365 days |
| Notifications | 90 days |
| AI metering records | 400 days |
| Sign-in sessions | 90 days from last use, or until you end them |
| Profile photo | Until you replace or remove it, or delete your account |
| Photos and voice recordings sent to AI features | Not stored |
| Generated wiring-plan images | About one day, then regenerated on request |
| Invoices and subscription records | As required for tax and accounting after the account closes |
6. What lives on your phone
- Your sign-in token, in the phone's secure storage.
- Your settings: language, notification and voice-reply switches, and the appearance (light, dark or matching the phone), which stays on the phone.
- Profile photos of you and your team, so the avatars show without signal: kept up to 30 days and deleted from the phone when you sign out.
- With Offline device cards turned on: your last 20 device cards and your last plain-text export, so they open without signal. They are filed under your account and team, and are deleted from the phone when you turn the switch off or sign out.
The app asks for camera access only when you use Snap & ID or installation review, or take a profile photo; microphone access (and on iPhone, speech recognition) only when you first speak to it, to dictate, record a voice note or use voice mode (which keeps it open while an answer is read, so you can talk over it); and location access, while the app is open only, the first time you tap Use my current location. Each can be revoked in your phone's settings; the rest of the app keeps working.
7. Your rights, including deletion
- Access and export. Settings → Export my data gives you a copy of what we hold about you.
- Correction. Edit your name, email, username and company details in Settings, or ask us.
- Deletion. Settings → Delete account permanently removes your account, profile photo, sessions, favourites, conversations, notifications, team membership, subscription and invoices. Any subscription you own is cancelled first — effective immediately — and if the payment processor cannot confirm the cancellation, nothing is deleted and the app tells you, so you are never left paying for an account that no longer exists. If you no longer have the app installed, use Delete your account or email us. We keep only a record that your email address has used its one free trial, and any invoices the law requires us to retain.
- Objection and restriction. Turn notifications off in Settings; turn the AI features off simply by not using them — the device catalogue works without them.
- Portability and complaints. Ask us for your data in a machine-readable form. If you are in a jurisdiction with a data-protection authority, you may also complain to it.
To exercise any of these, use Settings in the app or email contact@hingr.ai from the address on your account. We respond within 30 days.
8. Security
- All traffic between the app and our servers is encrypted (TLS).
- Passwords are stored as bcrypt hashes; sign-in tokens, backup codes and the authenticator secret are hashed or encrypted at rest.
- Sign-in, code and AI endpoints are rate-limited. Repeated wrong passwords slow the account down rather than lock it out, so a named technician cannot be shut out of their own tools by someone else.
- Optional two-factor authentication with an authenticator app and eight single-use backup codes.
- Photos are limited to 5 MB and voice notes to 10 MB and are validated before processing.
No service is perfectly secure. If we learn of a breach affecting your data, we will tell you and, where required, the relevant authority.
9. Children
Hingr is a professional tool for working technicians and is not directed at anyone under 18. We do not knowingly collect information from children. If you believe a child has created an account, contact us and we will delete it.
10. Changes to this policy
When we change this policy in a way that matters, we will tell you in the app and update the date at the top. The current version is always at https://hingr.ai/privacy.html.
Affiliate disclosure
The Store tab and the "Buy on Amazon" buttons on device cards use affiliate links. Hingr is a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for sites to earn advertising fees by advertising and linking to Amazon.com. If you buy through one of these links we may earn a small commission at no extra cost to you. It helps fund new devices, documentation and features, and we only list products we believe are genuinely useful to technicians in the field. Following a link shares nothing about your account with the retailer.
Hingr
Email: contact@hingr.ai
Web: https://hingr.ai