Privacy policy

About Hiryo and how to contact us

Hiryo is an invitation-only personal project for selected invited adults in the United States. For service questions, account requests or privacy questions, contact [email protected].

1. What this notice covers

This notice describes the information Hiryo can receive, store, use, and disclose through the workspace.

2. Information collected

Depending on the feature used, Hiryo can process:

account email, name, role, account status, password hash, sessions, MFA state, recovery state, reset state, OAuth state, and security audit events; profile and career information such as resume text, target roles, keywords, locations, workplace and sponsorship preferences, compensation preferences, career memory, evidence, snapshots, and versions; job and application information such as source configuration, job descriptions and metadata, fit evaluations, evidence, opportunities, applications, resumes, generated documents, answers, and activity records; configured provider account metadata, encrypted credentials, masked credentials, selected provider/model, pricing version, usage, reservations, budgets, and audit records; and cookie and analytics choices, essential cookies, product analytics identifiers and events, email preferences, and limited email open/click observations when you turn them on.

3. Cookies and security state

Essential cookies support sign-in, pending activation or MFA flows, cookie and analytics choices, OAuth state, and validated return destinations. The return destination is limited to approved internal paths and is short-lived.

Product analytics use a random browser identifier and a session cookie that expires after 30 minutes of inactivity. The detailed analytics described in section 6 also keep a random session identifier and a tab identifier in the browser's own storage. For signed-in accounts these are used by default. For signed-out visitors they are set only after the visitor accepts in the cookie banner. Section 6 explains both choices. Switching analytics off in Cookie settings removes the analytics cookies and does not limit the workspace.

4. How information is used

Hiryo uses the information to authenticate accounts, operate the workspace, collect and organize configured job sources, evaluate fit, prepare drafts, run requested model-assisted features, send necessary account email and optional summary email, record security and operational events, enforce limits, troubleshoot, and protect the service.

5. Providers and data flows

Google sign-in gives Hiryo the basic Google profile claims needed to verify the sign-in. It does not request Gmail, Calendar, Drive, or Contacts access. Email delivery and feedback can involve AWS SES, SQS, and SNS when the corresponding private configuration and worker are enabled. Password breach screening can query the Have I Been Pwned range API using only the first five characters of a SHA-1 password hash; Hiryo does not send the password, full hash, or email address to that service. Cloudflare currently carries configured web traffic as part of the deployment path.

For model-assisted work, Hiryo may use a locally configured model service or a selected OpenAI or DeepSeek account. The actual provider and feature path depend on deployment configuration and the user's selection. Hiryo does not claim that every listed integration is enabled at all times or that data never leaves the workspace.

6. Product analytics, email observations, and necessary logs

Signed-in accounts: product analytics are on by default. Hiryo accounts are invitation-only beta accounts, and analytics show us which pages are useful and where things break. You can switch analytics off at any time in Cookie settings, linked in the site footer. Collection stops right away, in every open tab, and the analytics cookies are removed. You can switch it back on in the same place. Switching analytics off does not limit the workspace.

Signed-out visitors: the public site asks first, in the cookie banner. Hiryo collects analytics from a signed-out browser only after the visitor accepts.

What analytics collect (since 19 October 2026): which pages you open and in what order; how long each page is on screen while its tab is visible and in use, and how much of that time was idle; how far you scroll; where you click, meaning the kind of element, a short button or menu name such as "Save", the page a link leads to and the position on the screen; whether a link was opened in a new tab; clicks that changed nothing or were repeated quickly in one spot; how long the pointer rested on a card or chart; that something was copied, but not what; keyboard shortcuts used outside text fields; the category of an error message shown to you, but not its words; how long pages and requests took, and the type of any file that failed to load; how many Hiryo tabs are open; going back and forward; and when a visit starts and ends. Events are grouped by a random session identifier, a tab identifier and a page-view identifier. When you are signed in they are linked to your account.

What analytics never record: anything you type, the contents of forms or fields, passwords, API keys, resume or job text, the words of messages shown to you, URL parameters, IP addresses, or screen and session recordings. An element inside a form field or an area marked private is recorded only as the kind of element it is. Nothing is sent to a third-party analytics provider.

Why: to see what works and what gets in the way, so we can improve Hiryo (an administrator reviews a weekly summary of where people spend time and where they get stuck), and to train and evaluate Hiryo's own AI models, for example to learn which screens and suggestions people find useful. For training, analytics may be joined with your account's other Hiryo activity. Analytics are never sold or shared with advertisers.

How long: detailed analytics events are kept for up to 180 days. Daily summaries made from them, which hold counts and timings per page and element but no account identifiers, are kept for up to two years. The page-count analytics Hiryo used before are kept for 90 days, with their detailed history limited to the most recent 200,000 events. Administrators can see analytics linked to an account and can export reports.

How to opt out: open Cookie settings at the bottom of any page and switch analytics off. Collection stops at once, the server keeps nothing more from your account, and records already collected expire under the limits above. Email [email protected] to ask for analytics linked to your account to be deleted sooner.

Email open and click observations are a separate choice under Settings › Email. They are off unless you turn them on, and the analytics setting does not change them. When they are on, weekly or daily summary messages can contain open and click observations. Mail proxies and automated scanners can create observations, so an event does not prove that a person read a message.

7. Who can see information

The account holder can access the account's workspace through the authorized session. Owner/admin functions can inspect administrative records, including product analytics linked to an account, and manage permitted user or provider targets. Provider credentials are masked in ordinary listings; the configured owner can reveal a key only after fresh security reauthentication. Configured source, email, identity, cloud, or model providers may process the information required for the feature they provide.

8. Retention

The implemented cleanup rules below run on scheduled maintenance. They describe cleanup of the live database, not guaranteed deletion at an exact time or expiry of backup copies:

detailed product analytics events: 180 days; daily analytics summaries without account identifiers: 2 years; page-count product analytics and email engagement tokens/events: 90 days, with page-count analytics capped at the newest 200,000 events/sessions; weekly or daily summary payload ciphertext: cleared after 30 days; completed summary metadata: eligible for cleanup after 180 days; other completed email metadata: eligible for cleanup after 90 days; email delivery/send attempts: 180 days; administrative and LLM account audit records: 365 days; and expired pending authentication, reset, OAuth, and reauthentication records: removed after expiry.

Queued or uncertain email records may remain until they are resolved. Unresolved charges and active usage reservations are retained for reconciliation. Cleanup does not delete primary user or job records. Protected backup copies may retain older records and currently require separate operator review and expiry; live-database deletion does not automatically remove those copies. Contact [email protected] for access, correction, export, or deletion requests. Requests are handled manually.

9. Security

Hiryo uses password hashing, encrypted provider credentials, scoped sessions, MFA and reauthentication flows, limited return paths, provider and budget checks, and audit records. These measures reduce risk, but no storage or transmission method is completely risk-free.

10. Requests and changes

Questions and privacy requests may be sent to [email protected]. Hiryo may update this notice as the beta changes and will identify the version or update date.