1. Who we are
Hinru is operated by ODUMWORLD GROUP LLC, a Florida limited liability company, with its principal office at 9350 Lake Hickory Nut Drive, Winter Garden, FL 34787. We are the controller of the personal data described here.
For any privacy question or request, write to hello@odumworld.com. A person reads that address.
This policy covers the Hinru web application at https://app.hinru.com. Our website, email list and optional application have a separate policy at https://hinru.com/privacy.
2. The short version
You own your content. We hold it so the Service can work for you.
- We do not sell it, we do not share it with advertisers, and we do not train models on it. (§5, §6)
- Assistant providers may retain requests under their own policies. We use no-training settings, but do not promise zero data retention. (§6)
- We keep readings from your screenshots and chat files, not the original attachments. The readings can include extracted text and game information. A club crest you add to a save is stored and shown back to you. (§3)
- OpenAI and Anthropic process assistant requests. Which provider receives a request depends on the task. §5 explains what they can see.
- We run no product analytics. We use necessary cookies and functional browser storage to support signing in, save workflows and display preferences. (§3, §7)
- You can take your work with you, and you can delete your account. After you delete, the copies we control in Hinru and its backups go within 30 days, apart from anything the law requires us to keep and one scrambled record if you had free access. Assistant providers' retention is described in §6. (§8, §9)
Everything below is the detail. Where this summary and a section differ, the section governs.
3. What we collect
Information you give us
- Account details. Your email address, an optional name, and your password, which we store only as a cryptographic hash and never in readable form.
- Your content. Everything you create in Hinru: decisions, rules, saves, session history, and anything else you enter. This is yours under §5 of the Terms.
- Screenshots and chat files. When you share a screenshot or supported file, it is sent to an assistant provider so it can be read. We do not keep the original image or file as an attachment in Hinru. We do keep readings made from it, which may include extracted text, game information and the assistant's replies. Those readings become part of your saved content. The original image or file is not included in your download. Keep your own copy of anything you need. Assistant providers' handling of requests is covered in §6.
- A club crest you add, which we do keep. If you set a crest for a save, your browser shrinks the image and we store it with that save, because the Service shows it back to you. It is in your download, and it is deleted with your account.
- Messages to us. Support emails, problem reports and feedback.
Information created by using the Service
- Usage and session records. Which sessions you opened, when, and what the Service did, so the product works and so you can see your own history.
- Assistant call records. For each request sent to an assistant provider, we record the provider, the model, token counts, and the cost. This is operational data used to manage costs, investigate failures and keep the Service running. It is not sold.
- Basic technical data. IP address and browser information as part of ordinary web server logs and security protections.
We do not run product analytics. No analytics, tracking, or measurement provider is installed. If we add one, we will update this policy and tell you before it starts.
Payment information. No card is needed for free access. We plan to use Stripe Managed Payments, Stripe's merchant of record service, for paid subscriptions. Before paid checkout becomes available, we will update this policy to explain the payment information involved and how it is handled.
4. How we use it, and why we are allowed to
- What we use
- Account details
- Legal basis (UK/EU)
- Performance of a contract
- What we use
- Your content
- Legal basis (UK/EU)
- Performance of a contract
- What we use
- Your content, at your direction
- Legal basis (UK/EU)
- Performance of a contract
- What we use
- Technical data, usage and assistant call records
- Legal basis (UK/EU)
- Legitimate interests
- What we use
- Usage records, error data
- Legal basis (UK/EU)
- Legitimate interests
- What we use
- Messages to us
- Legal basis (UK/EU)
- Legitimate interests
- What we use
- As required
- Legal basis (UK/EU)
- Legal obligation
5. Who we share it with
We share personal data only with the providers below, only so the Service can run, and only under contracts that require them to protect it and to process it on our instructions. We do not sell personal data, we do not share it for cross-context behavioral advertising, and we use no ad networks.
- What it does
- Hosting and content delivery
- What it can see
- Requests to the Service, server logs
- What it does
- Routes assistant requests to the model provider
- What it can see
- The content of assistant requests passing through it
- What it does
- Database
- What it can see
- Your account and your stored content
- What it does
- Sends the emails the Service sends, such as a password reset link
- What it can see
- Your email address and the contents of those emails
- What it does
- Hosts our support email inbox
- What it can see
- The email address and message contents you send to us
- What it does
- Receives the problem reports you send from inside the Service
- What it can see
- Your report, your account name or email as reporter, the save name and id, the app section and the report date
- What it does
- Processes assistant requests for conversations, reading game information, writing things up and working with saved context
- What it can see
- The conversations, screenshots, files and saved context needed for the request
- What it does
- Processes assistant requests, including reading squad screenshots and keeping useful context from conversations
- What it can see
- The conversations, screenshots, files and saved context needed for the request
Which assistant provider receives a request depends on the task and our configuration. If we route your content to an assistant provider not named here, we will update this policy and tell you before it starts. If you want to know which provider handled a specific request, the Service records it and we will tell you. Processing locations are described in §10.
Other disclosures. We may disclose data if the law requires it, to protect our rights or someone's safety, or in connection with a merger or sale of the business, in which case we will tell you first.
6. We do not train on your content
We do not use your content to train, fine-tune, or evaluate machine learning models. If we ever offer a way to voluntarily contribute content to improve the product, it will be opt-in and off by default.
This is our commitment. The assistant providers in §5 process requests under their own terms. We select providers and settings with this commitment in mind, and we will tell you if that changes.
We use no-training settings, but we do not promise zero data retention. Assistant providers may retain requests and responses under their own policies, including for security, abuse prevention and legal obligations. That can include content sent from your conversations, screenshots, files and saved context. Their retention periods and exceptions are governed by their terms. The provider retention policies are linked below this document.
7. Cookies and browser storage
Hinru uses cookies and browser storage to support the functions you ask for:
- a session cookie keeps you signed in;
- a save-restart cookie lets the app offer to reopen a save after you restart;
- local storage and session storage keep functional information in your browser, such as display preferences, unfinished drafts, password-reset flow information and save-reader progress.
We use no analytics cookies, no advertising cookies, and no third-party tracking cookies. If we add a non-essential cookie or tracking technology, we will ask for consent before using it.
8. Keeping and deleting your data
We keep your account data and content for as long as your account is open.
When you delete your account, we delete your content within 30 days, including working copies in our backups as they age out. We may keep limited records longer only where the law requires it, and only for that purpose.
This deletion timeline describes the copies we control in Hinru and its backups. Requests already sent to an assistant provider are also subject to that provider's retention policies, as described in §6.
If your account had free access, we keep one small record after you delete it: a scrambled code made from your email address, which cannot be turned back into your address, and the total cost of the assistant work on your account. We keep it only so that free access and free trials go to each person once, and so we know what free access cost. It holds nothing else about you.
You can download a portable copy of the work in your account from within the Service, including your conversations, your saved records, and your write-ups. Internal system, security, and processing records are not part of this download. You may separately request a copy of the personal data we hold about you, using the contact details in §14.
9. Your rights
Wherever you live, you can ask us to:
- tell you what personal data we hold about you;
- give you a copy in a portable format;
- correct anything that is wrong;
- delete your account and its data;
- restrict or object to certain processing;
- withdraw consent where processing is based on consent.
If you are in the UK, EU, or EEA, these are your rights under the GDPR, and you may also complain to your local supervisory authority. We would rather you came to us first.
If you are in California or another US state with a privacy law, you have rights to know, delete, correct, and obtain a portable copy, and to opt out of the sale or sharing of personal data. We do not sell or share personal data, so there is nothing to opt out of, and we will not discriminate against you for exercising any right.
How to use them: email hello@odumworld.com, or use the export and delete controls in your account settings. We respond within 30 days, and we will tell you if we need longer. We may ask you to confirm your identity first, which usually means replying from the address on the account.
10. Where your data is processed
Hinru is hosted in the United States. The providers in §5 may process data in the United States or other countries under their service agreements. Selecting a US-based provider does not guarantee that every part of its processing takes place in the United States.
If you use Hinru from the UK, EU, or EEA, your personal data is transferred to the United States. We rely on Standard Contractual Clauses, or the UK equivalent, with providers that require them.
11. How we protect it
Passwords are stored as bcrypt hashes and never in readable form. Sessions use signed tokens. Your content is read and written through helpers that resolve your save from your signed-in session rather than from anything in the request, so one person's request cannot reach another person's data by changing an identifier. Access to production systems is limited to people who need it.
No service is perfectly secure. Keep a copy of anything you cannot afford to lose. If a breach affects your personal data, we will notify you and any regulator we are required to notify, without undue delay.
12. Children
Hinru is for people 18 and over. We do not knowingly collect personal data from anyone under 18. If we learn that we have, we will delete it. If you believe a child has given us data, write to hello@odumworld.com.
13. Changes to this policy
We may update this policy. If a change materially affects how we handle your personal data, we will tell you by email or in the Service before it takes effect, and we will update the date at the top.
14. Contact
ODUMWORLD GROUP LLC 9350 Lake Hickory Nut Drive, Winter Garden, FL 34787 hello@odumworld.com