Privacy Policy

This policy covers the Context is Love website and application operated by Context is Love LLC, including the public pages, the signed-in product, shared spaces, and related emails. It does not cover other companies' websites or services you may reach through links you save.

Context is Love is an evolving product under active development. Features and wording may change, and this policy will be updated as the product changes.

• Account and authentication information. Your email address, account and user identifiers, and sign-in and session information. If you sign in with a third-party provider such as Google or Apple, we receive the account identifiers that provider shares with us. Where Apple requires it, we also store the sign-in token Apple issues, described under "Sign-in provider tokens" below.
• Context you provide. Conversations, notes, saved links and saved content, screenshots or files you choose to add, descriptions, goals, decisions, tasks, corrections, memories, and other information you deliberately give the product. Files you upload are stored in our private uploads storage area, kept under your own account folder.
• Shared and collaborative information. Spaces you create or join, invitations you send or accept, memberships and roles, permissions, and the content you choose to share into a space.
• Feedback and testing information. The feedback you write, plus limited debugging metadata our feedback tool collects with it, such as the page or path you were on, your screen size, and your browser's user agent string.
• Newsletter, early-access, and tester information. If you sign up for the newsletter, early access, or the tester program, we collect the contact details and responses you submit in those forms.
• Security and technical information. At a category level: device, browser, and network information, security and sign-in event logs, and diagnostic or error information. We use this to authenticate you, protect accounts, troubleshoot problems, and prevent abuse. We do not publish the internal details of those protections.

• To provide the product: keeping your context, generating understanding, organizing decisions and tasks, and resurfacing things when they matter.
• To operate shared spaces and honor the permissions and scope you set.
• To authenticate you, protect accounts, investigate suspicious activity, and prevent abuse.
• To respond to feedback and support requests, and to fix defects.
• To improve the product's reliability, usability, and quality.
• To send product, account, testing, and — if you signed up — newsletter emails.
• To meet legal obligations and enforce our terms.

Paid plans and pilots are processed by Stripe, our payment processor. Payment details such as your card number are entered on Stripe's own hosted checkout page and are handled by Stripe — we do not receive or store full card numbers. We receive the confirmation and account-level billing information Stripe returns to us, such as the purchase, its amount and status, and the email address used at checkout.

Where you arrived through a referral or a specific offer, a reference identifier may be attached to the checkout so we can match the purchase to the right account and offer. Stripe processes payment information as its own controller under its privacy policy.

If you book a 15-minute pilot conversation, we collect what you enter on that form: your name, your company, your email address, and — only if you choose to provide them — a phone number and a short note about the problem you want to talk through. We also store the time slot you chose, the time zone your browser reported, where on the site the booking came from, the status of the booking, and a one-way hashed form of your network address used solely to limit abusive repeat submissions.

We use this to hold the slot, prevent double-booking, confirm the appointment, and prepare for the conversation. We send a confirmation email to you and a notification to our own address, both through our managed email provider, and the confirmation includes a standard calendar invitation file containing the appointment time, title, and organizer. Your note and phone number are not shown on the reschedule or cancel screen; that screen is reached through a private link and shows only the appointment itself.

Booking details are not readable through the public data interface — they are reachable only through guarded server functions. A booking is not an account, so deleting an account does not remove a booking made through this form. We have not set a fixed retention period for booking records; if you want yours removed, email us and we will delete it.

Context is Love uses artificial intelligence to interpret, summarize, connect, and respond to the information you provide. To do that, relevant context you provide may be sent through the application's AI processing path to a model provider so a response, summary, interpretation, or connection can be generated and returned to you.

AI output can be incomplete or wrong. It is meant to support your understanding and judgment, not to replace professional care, legal or medical advice, emergency services, or your own decision-making.

We do not make a promise here about whether model providers do or do not use data for model training, because that depends on provider terms we have not independently verified for this policy. We will state it plainly once it is verified.

Beyond what you type, the product stores what it derives from your material: summaries, extracted facts, interpretations, connections, briefings, proposed decisions and tasks, and private insights. Derived records follow the permissions of the context they came from — a derivation from private context is private, and a derivation made inside a shared space follows that space's rules. Derived output is an interpretation, not a source fact.

When source context is changed, corrected, withdrawn, deleted, or loses permission, personal derivations that materially depend on it are re-evaluated, invalidated, or removed from current use, so stale material cannot become a route to future disclosure. Legitimate shared or organizational history and provenance can remain with the space where that record belongs, and revoking a permission does not retract output already legitimately shared with other people or copies that exist outside the product.

Corrections are preserved as history rather than silently overwritten, so you can see what changed. Deleting an item removes it and its versions from our live systems; we do not promise that every historical trace is erased everywhere at once, including from shared records that other members legitimately rely on.

You can connect an external AI application — for example an AI assistant that supports connected apps — to your Context is Love account. Connecting is per-user, requires your own sign-in and authorization, and is off unless you turn it on.

While connected, that application can, acting as you: list your spaces, read space briefings and tasks, search and add items in your private context, and post messages into spaces you belong to. It is subject to the same permission rules as the product itself — private context tagged as never usable in a group is not disclosed to it, and it cannot reach anything you could not reach yourself. Content sent through a connected application is also processed by that application's provider under their terms, not ours. You can disconnect it at any time from that application, and you can email us to revoke access.

When you share content into a space, the other members of that space can see it according to the space's permissions. Private context stays private to you unless you choose to share it. Scope controls exist so you can decide what a space sees.

You may describe other people in your context — a family member, a colleague, a client. You are responsible for having the appropriate authority or permission to provide information about other people, and for sharing only what is appropriate to share.

You may choose to provide sensitive personal context. Share only what you are comfortable providing, and use the privacy and scope controls when other people are involved. Context is Love does not create a medical, legal, or other privileged relationship, and is not a regulated recordkeeping system.

Some spaces belong to an organization rather than to one person. Context created inside an organization or a shared space — messages, decisions, tasks, briefings, and the operational record of what happened — is part of that shared record and can remain with the organization and its remaining members after you leave or delete your account, with your authorship removed. Your private context is never part of that record.

If you are the only member of a space or organization, it is deleted with your account. If other members remain, ownership passes to a remaining owner or the longest-standing member.

Permissions and cross-context AI consent are default-deny and revocable by you at any time. Revoking stops future use of that context. It cannot retract output that was already generated and shared with other people before you revoked, and it does not delete the shared record another member already relies on. To remove the underlying material as well, delete the content itself.

Context is Love uses product analytics (PostHog) and error and diagnostics reporting (Sentry). Both are optional, both are off until you turn them on, and each is a separate choice you make in the cookie banner the first time you visit. When analytics is on it records product-event and status metadata — such as which step of a flow was reached, or whether an action succeeded — so we can understand usage and improve the service. You can change or withdraw either choice at any time from “Cookie choices” in the site footer; withdrawing stops future sending immediately. Storage that keeps you signed in, secures the account, and takes payment is strictly necessary and is not part of that choice. Analytics may not be enabled on every deployment or environment.

As configured in the product today, automatic event capture, session recording, and persistent person profiles are turned off, page text and element attributes are masked, and page URLs and referrers are excluded from the events we send. Our policy is not to intentionally send raw private conversation or context text, or the literal content of private AI insights, to product analytics. As with any internet service, the analytics provider also receives standard technical request information such as IP address and user agent.

We do not sell your context. We share information with service providers that operate parts of the product on our behalf, and with others only as described below.

• Backend, authentication, and database: Supabase.
• Application hosting and AI gateway infrastructure: Lovable-hosted infrastructure, including the AI gateway the product calls.
• AI/model providers reached through that configured AI path, which process the context sent to them in order to generate the requested output.
• Email infrastructure: Lovable's managed email service, used to send account, invitation, tester, and newsletter emails.
• Payments: Stripe, for paid plans and pilots, as described above.
• Product analytics (PostHog) where enabled, as described above.
• Error and diagnostics reporting (Sentry) where enabled, so we can find and fix defects. Reports are scrubbed before they are sent: email addresses, identifiers, and long tokens are replaced with placeholders.
• Connected AI applications you authorize yourself, as described above.
• Other people you share with — the members of any space you post into, and people you invite.
• Legal and safety — if required by law, legal process, or to protect the rights, safety, or security of users, the public, or Context is Love LLC.
• Business transfers — if the business is involved in a merger, acquisition, or sale of assets, information may transfer as part of that transaction.

We do not currently sell personal information for money or use private context to serve third-party behavioral advertising.

If you sign in with Apple, Apple requires us to revoke your sign-in when you delete your account. To do that we store the token Apple issues at sign-in on our servers, where the browser cannot read it, and we use it for nothing else. When you delete your account we call Apple's revocation endpoint before removing your login record.

We keep a small record that a revocation was attempted and whether it succeeded. It is deliberately kept separate from your account so the proof survives deletion, and it contains no name, email, or content.

We keep information for as long as needed to provide the product to you and for the purposes described in this policy. We are not stating a fixed deletion timeline here, because we will not publish a number we have not verified in production.

You can delete or correct content through the controls available in the product, and you can permanently delete your whole account yourself from your account settings when signed in. If you cannot reach that control, email us and we will process the deletion.

When an account is deleted, your personal data is removed: your private context, preferences, permissions and consents, saved items, uploaded files, profile, plans, onboarding responses, roles, and pending invitations you sent. Spaces where you were the only member are deleted with everything in them. Your login record is deleted and all sessions are revoked.

Deletion in a shared space has to respect the other participants' legitimate record of what happened there, while not exposing the departing person's private information. Where shared history must remain for the other members, we remove your identifying details from it rather than preserve them, and security and audit logs are stripped of identifying information rather than kept intact.

Deletion applies to our live systems. Our infrastructure providers keep their own operational backups and logs on schedules we do not control, so copies can persist there for a period after deletion before they age out. We do not restore deleted accounts from those backups.

We use administrative and technical measures intended to protect your information, including server-side permission enforcement, per-user access rules on stored data, and logging of security-relevant events. We do not describe the internal details of those protections publicly.

No product or transmission method is perfectly secure, and we cannot guarantee absolute security. Please use a strong, unique password and tell us if you believe your account has been accessed by someone else.

• Choose what you provide. Nothing enters your context unless you put it there.
• Use scope and permission controls to decide what a shared space can see.
• Set resurfacing preferences for sensitive memories so they are not brought back automatically.
• Correct or update context; the product preserves history rather than silently overwriting it.
• Delete content you no longer want kept, and permanently delete your whole account from your account settings.
• Unsubscribe from newsletter emails using the link in any newsletter email.
• Privacy, correction, departure, and permission controls are not paywalled.

Account holders must be at least 18 years old, and Context is Love is not directed to children. Adults may provide family-related context, including context about children, and are responsible for having the appropriate authority or permission to do so. If you believe a minor has created an account, please contact us so we can address it.

Context is Love LLC is based in the United States, and our service providers may process and store information in the United States or in other countries where they or their subprocessors operate. If you use the product from outside the United States, you understand that your information may be processed in a country whose data-protection rules differ from those where you live.

We will update this policy as the product changes. When we make a material change, we will update the effective date at the top of this page and, where appropriate, tell you in the product or by email. Continuing to use Context is Love after an update means the updated policy applies.

For privacy questions, contact Context is Love LLC at hello@contextislove.com.

If you are signed in, the fastest route is the in-product Give feedback option, which reaches us directly.

Context is Love LLC · New Jersey, United States