Privacy Policy

COCO & TAMY, represented by Kim Jaehyeon, is responsible for Liloi's processing. Privacy requests are handled by Kim Jaehyeon at l@liloi.ai.

Liloi processes email, account ID, display name, locale, authentication events, projects, work logs, notes, uploaded files and images, extracted text and evidence, generated outputs, subscription status and identifiers, support messages, and necessary security/error logs to provide, secure, support, and improve the service.

Liloi does not store the complete payment-card details that Creem collects directly in checkout.

Account content is deleted when you delete the relevant records or account. Daily database backups retain seven days of history and can contain deleted records until rotation. These backups contain file metadata, not stored file contents. Provider security records and legal holds may follow separate retention rules.

Where Korean e-commerce retention rules apply, display and advertising records are kept for six months, complaints and dispute records for three years, and contract, withdrawal, payment and supply records for five years. Creem product-sale records are kept for at least seven years under its merchant terms. Legally retained records are access-restricted and not reused for marketing.

You may request access, correction, deletion, suspension, withdrawal of consent, export, and account deletion. Records retained only by law are separated and access restricted. Contact l@liloi.ai.

Supabase provides authentication, database and private file storage. The primary database and storage region is Seoul, South Korea. Vercel hosts the web service; server functions run in the United States and its delivery network is distributed internationally. Hosting in Seoul does not mean all processing stays in Korea.

Resend delivers authentication emails using your email address, authentication message and delivery metadata. Sending is routed through Tokyo, Japan; message content and delivery logs are stored in the United States for 30 days, with separate seven-day backups. These emails contain no work records. Liloi does not enable click or open tracking in authentication emails. Resend contact and processing information: resend.com/security/gdpr. For privacy requests, contact l@liloi.ai.

Creem processes Merchant of Record billing, invoices, indirect taxes, subscriptions, refunds and disputes. AI, connected tools and browser push use the providers and data described in their sections above. Provider security, support and legal-retention activities follow their own applicable policies.

Verified users with Pro access or an unused shared first-use grant may authorize liloi plug for selected work collection. Liloi stores the provider account ID and label, granted scopes, encrypted access and refresh tokens, and selected project or repository identifiers until disconnection or account deletion. Authorization alone does not start work collection. Collection begins only after you choose a scope and separately agree to AI processing.

Collection reads Jira issues you reported or currently own, and GitHub issues and pull-request summaries you authored or are currently assigned to. New v2 consent also covers your submitted GitHub review body, state, submission date and PR title. If separately selected, it reads your default-branch commit messages, Git author/committer dates and GitHub identity, not Git names/emails. Existing v1 jobs keep their issue/PR scope. Code, diffs, inline comments, former assignments and attachments are excluded. Reviews are not implementation credit; commits are not shipping or project-completion proof. Titles, descriptions, provider identifiers, source links, status, participation and provider dates may be sent to OpenAI, potentially overseas, under the AI processing terms below. Updated timestamps are not proof of work dates or completion. Full collected text, temporary PR-title cursors and drafts are automatically removed when processing ends; unfinished collections expire after 48 hours and are cleared by scheduled cleanup. Records and supporting excerpts remain until deletion. Disconnection stops unfinished collection and removes locally retained credentials; separately revoke the app in Jira or GitHub settings to remove provider-side permission. Provider and backup retention are separate.

Where available, Linear, Notion task databases, Asana, Trello, ClickUp and monday.com connections read selected task titles, descriptions, custom properties, checklists and task relationships, together with native account/task identifiers, source links, status, participation and provider dates. Only work with evidence linking it to your account is retained for classification. Liloi makes read requests only; the provider's authorization may allow broader access, particularly ClickUp. Attachments, comments and linked document contents are not collected through these connections. Source text may be sent to OpenAI under the AI processing terms above. A board, database or List name is not automatically a project, and an updated timestamp or deadline is not automatically a work date or completed outcome.

After monday.com disconnection or account deletion, collection stops immediately. Only the disconnected grant's encrypted credentials and cleanup identifiers remain in a separate queue for provider-side revocation. Their use expires after 24 hours; successful revocation or expiry triggers deletion by scheduled cleanup. Failed cleanup is retried. This queue never reads work or calls AI. Other locally retained credentials are removed on disconnection or account deletion. Provider settings can also revoke the app; provider-side retention and backups are separate.

Trello account deletion or provider-side access revocation removes the affected Trello records, evidence and resume blocks citing them. Manual records and other providers' work remain. Expired Trello access stops collection and requests reconnection; without a new grant, affected data is deleted after seven days. Profile changes replace the stored username. Ordinary Liloi disconnection keeps saved work; it is separate from these provider privacy requests.

After separate upload consent, Liloi sends work text, images, document pages and embedded attachments to OpenAI to propose records. Request filenames use neutral labels; account identifiers and private storage URLs are not added. Your materials may themselves contain identifying information or metadata. Processing may occur overseas; Korean-only processing is not guaranteed. Do not upload personal data or confidential information without authority. Earlier text-only consent does not authorize sending raw images or documents.

Response storage is disabled, but OpenAI may keep abuse-monitoring content for up to 30 days or longer where required. This is not zero retention. For new uploads, originals, full extracted text and temporary classification drafts are automatically deleted when processing ends, without separate approval. Failed deletions are retried automatically. Supporting excerpts and organized records remain until you delete them. Backups, legal retention and external-provider retention are separate. Decline by using manual records instead. Withdrawal or deletion: l@liloi.ai. AI-read images are interpretations; drafts are not verified facts.

Browser push is off until you choose to enable it and grant browser permission. Liloi stores a browser-generated push endpoint, encryption keys, account association and language to deliver service updates. Push passes through your browser provider (such as Google, Mozilla, Apple or Microsoft), potentially overseas. Alerts contain no work content, original files or filenames. The browser provider's own retention rules apply; delivery is not guaranteed.

You can disable notifications for this browser in the notification inbox. Account deletion removes registered endpoints. In-app events are kept for up to 90 days, the delivery journal for up to 7 days, and endpoints for up to 180 days without renewal, subject to scheduled cleanup and separate backup retention. Local storage remembers only the account association for this browser, not work contents. Notifications are service updates, not marketing.

A photo you choose is cropped and re-encoded for your private account and resume. Liloi removes image metadata during encoding and stores the processed portrait in owner-only storage. This photo is not sent to the AI classification service. It remains until replacement, removal or account deletion, subject to separate backup retention. Uploading a resume as work material is a different, separately consented AI process.

You can report a classification issue without sharing work content. Receipts contain your account and related record IDs, issue category, status and timestamps. Failed import jobs contribute only identifiers, processing stage, retry counts and a pipeline version. Receipts, diagnostics and access records are retained for up to 90 days.

Sharing excerpts, results or notes is optional and requires separate consent. You can edit or remove private details before sending. Only authorized reviewers can open shared text; access is recorded. Shared text expires after 30 days and is deleted when you cancel the request or delete the related material or account. Daily database backups may retain deleted text for up to seven days. Original files are not retained for feedback.

Feedback does not trigger AI processing, model training or changes to your records. Reviewers use fictional examples for long-term regression tests. Review status appears in My reports and service notifications. Contact l@liloi.ai to exercise your rights.

Liloi applies owner-scoped database access, server-only secrets, encrypted transport, signed-webhook verification, and account export/deletion controls. Essential session and language storage are used; non-essential analytics or advertising will not be enabled without the required disclosure and consent controls.

The GDPR supplement explains applicable rights, processing roles and international-transfer review. Regional protections depend on applicable law and processing circumstances, not the selected language. A paid export feature cannot restrict statutory access or portability; privacy requests may be sent to l@liloi.ai without a Pro subscription.