HiJen.Back to HiJen
Terms and policies

Privacy and Cookie Notice

Version 1.0 · November 17, 2026

1 Who we are and how to contact us

HiJen is provided by ViaJen Technologies Limited, trading as HiJen, company number 16399225, registered in England and Wales at 7 Granard Business Centre, Bunns Lane, Mill Hill, London NW7 2DQ, United Kingdom. For privacy questions or rights requests, the contact is privacy@hijen.ai; general support is hello@hijen.ai.

We are controller for our own account administration, billing, security, fraud prevention and legal records. The business identified on a guest page is controller for its guest chats and business-specific Watch requests; HiJen processes them on that business’s documented lawful instructions. Watch is a request for specified updates or offers from that business only. We do not reuse it to recommend or promote another business.

2 Information we collect and where it comes from

Business users and testers provide account/email details, workspace and business information, uploaded content, menu PDFs, support messages and purchase-authority records. We also receive billing status and identifiers from Stripe. Payment-card entry takes place on Stripe’s hosted page; HiJen’s billing schema has no card-number or CVC fields.

Guests may provide questions, conversation history and preferences in Jen, and an email or WhatsApp contact if they explicitly choose Watch. We process request, device, session and diagnostic information to deliver and secure the service. With accepted analytics consent, we record visits, content views and contact clicks.

Business information may also come from business websites, permitted public sources and Google Places, including public business contact information. Public availability does not remove privacy or source-use obligations. We receive error reports, filtered logs and AI traces through service providers. Do not include payment-card details, identity documents or highly sensitive information in chat or uploads.

3 Why we use information and our lawful bases

Account and feature delivery: where necessary to perform our contract with an individual user, we use information to authenticate them, provide their requested service and manage their requests. Where the customer is an organisation, use of its representatives’ details relies on legitimate interests in administering that relationship.

Billing and records: we use account, order and payment-status information to manage purchases, subscriptions and disputes, relying on contract where applicable, legitimate interests in business administration and applicable legal record-keeping duties.

Security, support and complaints: we use proportionate access, request and diagnostic information to protect users, prevent abuse, investigate reports and maintain the service. Necessary access to individual chats or journeys to support and improve a business’s authorised service is controlled and limited to that service. Processor activity follows the business’s lawful instructions. For our own security, fraud prevention and complaints handling, the basis is legitimate interests in a safe, reliable service, with legal obligations where applicable.

Business-specific Watch: if you choose Watch, we record your request and choice to receive the specified availability updates or offers from that business. You can withdraw it. It does not authorise another business’s offers, cross-business profiling or unrelated marketing. Optional visit analytics run only after you accept optional analytics cookies. Declining them means we collect no page-view counts. Watch and optional analytics are separate choices; the business controller is responsible for the lawful basis and notices for its guest service.

4 AI processing and private previews

We use AI providers to organise business content and answer guest questions. Inputs can include website material, uploaded documents, questions, recent conversation history and relevant business context. Public guest conversations are stored in our application database.

Private-preview conversations are not written to the normal guest-conversation tables, but the client supplies history for later turns and AI instrumentation can record prompt, reply and tool content in Logfire. Temporary application handling does not mean no trace or provider retention.

We use OpenAI’s global Responses API, which includes processing in the US; there is no EU-only processing or Zero Data Retention arrangement. We send requests with response storage turned off. OpenAI may keep abuse-monitoring data for up to 30 days, subject to exceptions. OpenAI does not use API data to train its models unless the customer opts in, and we have not opted in.

We do not use guest personal data to train or fine-tune AI models, and do not permit our AI providers to use it for their own model training. We use genuinely anonymised aggregate information and general feedback to improve HiJen across businesses, without identifying guests or disclosing confidential business information. We do not independently repurpose guest personal data or build cross-business guest profiles. Anonymising guest personal data must itself follow the business’s documented lawful instructions and applicable law.

5 Recipients and countries

Our providers include Vercel for frontend delivery and telemetry; Railway for the backend; Supabase for database, authentication and private storage; OpenAI for AI processing; Pydantic Logfire for AI and request traces; Sentry for errors and filtered logs; Cloudflare Browser Rendering for website ingestion and Turnstile for the account bot check; Google Places for business search and photo requests; Google Workspace for support and privacy email; Resend for sign-in codes and service emails; and Stripe for hosted billing. Internal alerts sent to our team’s Slack carry technical details only, not personal data.

Our application runs in Frankfurt and the Netherlands, and service emails are sent from Ireland. This is not a promise that all processing or access stays in Europe. OpenAI’s endpoint is global; providers may also process account information or provide support from other countries. The provider register in the Business Agreement lists each provider’s role, location and data processing terms.

We may disclose proportionate information to advisers, authorities or others where required by law or necessary to handle a genuine claim, subject to applicable safeguards.

6 Watch and business contact sharing

Watch lets you ask for specified availability updates or offers from the business whose guide you are using. HiJen handles that request on behalf of that business. We do not take the request, interests or other signals and use them to recommend or promote another client. Choosing Watch records the contact method and consent evidence for that request. You may withdraw using the available withdrawal control or privacy contact.

Raw Watch contact details are not shared with the business. HiJen sends the requested updates on its behalf. Any future direct contact-sharing feature requires its own clear notice, lawful basis and appropriate user choice; it is not authorised merely by choosing the current Watch service.

7 Retention and deletion

We keep information only for as long as necessary and honour deletion rights.

Guest chats are retained for up to 90 days and business-specific Watch requests for up to 12 months, unless an earlier valid deletion request, Watch withdrawal or necessary lawful retention applies. Events associated with a chat are part of that chat and are deleted with it, including earlier deletion.

Private drafts and associated content are ordinarily retained for up to 30 days after trial access expires or paid-service access ends, subject to earlier valid return/deletion instructions and necessary lawful retention. For unresolved non-payment, the Business Agreement reserves rights to suspend or end service, close the account and delete content after the 14-day payment notice expires; it does not guarantee an additional 30-day storage period in that case. The notice explains the possible deletion and return/export route. Mandatory return/deletion rights and legally required retention still apply. Guest-chat expiry, Watch withdrawal and independent legal-record retention are separate.

Billing and acceptance records are retained for six years after the account ends. Trust-and-safety reports are retained for 12 months after staff close the report. Necessary legal holds or mandatory retention are limited to the relevant records and purpose. Detailed, consented visit and content-activity records are retained for up to 90 days, then deleted or genuinely anonymised. Genuinely anonymous aggregate statistics may be retained beyond 90 days for reporting and system improvement. Aggregation or removal of names alone is not sufficient if a guest remains identifiable. These rules do not extend the retention of underlying guest chats or permit independent reuse of guest personal data or cross-business guest profiles.

Managed Supabase Pro database backups use a seven-day rolling window. That does not cover Storage files, separate downloads/exports, legal holds or other providers’ copies. On restoration, prior deletion instructions must be reapplied. Logfire keeps traces for 30 days. Sentry keeps logs for 30 days and errors for 90 days. OpenAI retention is separate as described above.

The documented manual privacy process locates records from sufficient context, deletes or anonymises relevant data and records completion without retaining deleted guest content. Deletion requests are handled by our privacy team; providers’ copies expire on the schedules above.

8 Cookies, browser storage and telemetry

Necessary functions include sign-in, security, remembering a consent choice and providing a signed session identity for requested chat. Without analytics consent, guest chat identity is session-only. Embedded-widget identity remains partitioned and session-only. On a hosted guest site, consented identity and language preferences are limited by remaining consent, up to one year.

Optional website analytics, including visit, content-view and contact-click analytics and optional Vercel Web Analytics/Speed Insights, use the same visitor cookie-banner choice. They run only after acceptance. If you decline optional cookies, we collect no page-view counts or optional analytics events and keep no lasting analytics identifier. A necessary cookie remembers your choice; session-only identifiers needed for requested chat remain separate. Refusal does not prevent use of the guide or Jen.

Cloudflare is used for Browser Rendering during ingestion and for Turnstile, the bot check on HiJen account sign-in and email-code screens, which processes the IP address and browser signals of the person signing in. It does not sit in front of guest traffic and sets no cookies on guest pages.

Sentry is used only to detect and fix software errors, with personal information removed. It is not used for marketing or tracking guest behaviour.

9 Your rights and choices

Depending on the applicable law and processing, you may request access, correction, deletion, restriction or portability, and may object to processing based on legitimate interests. You may withdraw optional consent without affecting earlier lawful use. We may need proportionate information to verify a request and locate the relevant records; do not send identity documents unless specifically and securely requested.

Contact privacy@hijen.ai using enough context to identify the account, business or conversation. Where we act only for a business controller, we will route or assist with its request handling. You may complain to the UK Information Commissioner at ico.org.uk or another competent authority, including in your place of residence where applicable.

An email and necessary account information are needed for account access; declining them prevents that feature. Watch contact details are optional; declining them does not prevent browsing or asking Jen questions. Refusing optional analytics consent does not itself prevent the requested service.

10 Automated decisions and updates

Jen provides informational AI answers. The Business Agreement explains our rights concerning unpaid subscriptions.

We will date the approved notice and explain material changes through an appropriate channel. A notice update is not consent to a new optional purpose.