Privacy Policy

Last updated: October 12, 2026

1. Overview

Tiptree Advanced Systems Corporation, carrying on business as Tiptree Systems (“Tiptree”, “we”, “us”, or “our”), operates Lacuna, Atlas and Althea (collectively, the “Services”), three interconnected platforms designed to support scientific research and collaboration.

This Privacy Policy (the “Policy”) explains how Tiptree collects, uses, discloses and otherwise processes personal information in connection with the Services.

Capitalized terms used but not defined in this Policy have the meanings given to them in the Terms of Service.

2. Personal Information We Collect

For the purposes of this Policy, “Personal Information” means any information that identifies or can reasonably be used to identify a specific person, either on its own or when combined with other information.

Personal Information we collect depends on the Service you use, how you interact with it, and the features available to you.

We may collect Personal Information from account holders, such as:

• first and last name, account and usernames, affiliation, position, display name, email address, profile image, and telephone number;
• account identifiers, identity-provider details, OAuth provider, external username or identifier, profile claims, authentication records, authentication events, email or SMS verification status, verified identity status, access scopes, tokens and sign-up context;
• academic or institutional email, organization, laboratory, institutional affiliation, role, and workspace membership, field, expertise, biography, ORCID, scholarly-profile links, publications, CV, and application answers;
• searches, filters, result clicks, result position, reading time, bookmarks, folders, saved items, chat workspaces, tabs, prompts, responses, and feedback;
• profile corrections, support requests, rights-request history, application review, invitations, project eligibility, fellowship eligibility, and related correspondence;
• time zone, language, country, and age or confirmation of adulthood;
• account settings, consent choices,
• identity-provider identifiers, and
• conflicts of interest, employer or institution permissions, funding, sanctions or export eligibility, required ethics approvals, and representations about authority to contribute.

We may collect Personal Information about researchers and other profile subjects:

• Identity and scholarly identifiers such as first and last name, aliases, country, timezone, ORCID, OpenReview, DBLP, OpenAlex, Semantic Scholar, Google Scholar, and similar identifiers
• Professional information such as institutional affiliations, positions, education, professional history, home-page and professional-profile links
• Scholarly record such as papers, author order, venues, dates, citations, topics, co-authorship links, and research directions
• Public web and social information such as research interests, GitHub or Bluesky identifiers, public professional-profile fields, and limited public posts used as evidence of current research activity
• Images such as a publicly available professional portrait or avatar
• Source evidence such as source URLs, retrieval dates, cleaned page text, provenance, match confidence, and records used to resolve whether sources concern the same person
• Inferences and generated material such as similarity relationships, impact indicators such as “foundational” or “influential”, topic classifications, and AI-generated biographies or summaries
• Rights correspondence such as corrections, objections, supporting evidence, identity-verification information, and the outcome of a request

We collect and process the material you provide to the Services and the records it creates for you, which may include:

• messages, prompts, agent responses, feedback, citations, and conversation titles;
• uploaded papers, data, images, code, notes, and other files;
• instructions, plans, checkpoints, model inputs and outputs, tool calls, tool results, terminal or computer-use traces, and error records;
• readable memory entries, researcher-profile fields, corrections, preferences, and context used across channels;
• documents or records retrieved from an integration at your direction; and
• network requests, proposed disclosures, your approval or refusal, delivery state, and audit records.

Research content may contain unpublished intellectual property and Personal Information about you or others.

We may also combine records from multiple sources and infer that they relate to the same individual.

We may collect Personal Information relating to usage, device, analytics and security, such as :

• IP address, approximate region derived from IP,
• date and time,
• requested URL,
• route or endpoint,
• referring page,
• browser,
• device type and operating system,
• language,
• session and journey identifiers,
• feature or interaction events,
• response status,
• latency, errors, crash data,
• logs,
• security or abuse events,
• page views, navigation,
• engagement,
• referral,
• campaign information using cookies or similar local storage.

We may collect Personal Information relating to support, communications and legal records, such as:

• communications relating to support requests, call or meeting details you choose to provide, and survey responses;
• privacy, authorship, scoring, intellectual-property, integrity, security, and legal matters;
• rights requests, complaints, incident records, and related correspondence;
• identity-verification material needed for a request;
• consent and signature records;
• contract version and hash;
• timestamps;
• the outcome of a request, review, or dispute; and
• information reasonably needed for legal claims or compliance.

We may collect Personal Information from connected services:

If you connect a third-party account, we receive the information covered by the scopes you authorize. Depending on the features available to you, this may include: name, email address, profile image, and account identifier; event title, time, location, attendees, description, identifiers, and permission to create, change, or delete events at your direction; message or thread identifiers, message content, attachments, and permission to draft, send, receive, or organize messages at your direction; and records from code hosts, document stores, scholarly services, compute systems, or other integrations you enable.

In connection with Atlas, we may collect Personal Information relating to the project session, including:

• messages, prompts, critiques, questions, instructions, responses, edits, votes, and reactions;
• ideas, hypotheses, text, code, data, files, figures, designs, methods, protocols, experiments, results, failures, and citations;
• agent plans, model inputs and outputs, tool calls, compute jobs, logs, checkpoints, repository events, and error traces;
• source and license declarations, background-material disclosures, approvals, provenance, and intellectual-property notices;
• content-review, formal-publication, identity-disclosure, and authorship decisions; and
• research-integrity reports, corrections, disputes, reviews, and outcomes.

3. Why We Use Personal Information

We use Personal Information for the following purposes:

• To provide, operate, maintain, and improve the Services and their features.
• To create, manage, authenticate, and administer accounts, projects, workspaces, and user preferences.
• To build, maintain, publish, and improve scholarly, research, and attribution records.
• To facilitate research, collaboration, publications, contributions, attribution, and intellectual property management.
• To provide AI-powered tools, agents, integrations, analytics, and other functionality requested by users.
• To communicate with users and provide customer support.
• To monitor, secure, troubleshoot, and protect the Services, users, research integrity, and our systems from fraud, abuse, and unauthorized activity.
• To measure usage, conduct analytics, and improve the performance, reliability, and user experience of the Services.
• To respond to inquiries, correction requests, complaints, and the exercise of privacy or other legal rights.
• To comply with legal obligations, enforce agreements, and establish, exercise, or defend legal claims and rights.
• To investigate fraud or abuse; protect a person or the Services;
• To comply with applicable law, a court order, a lawful government request, or other valid legal process or establish, exercise, or defend legal claims or rights;
• To be reviewed under confidentiality in connection with a financing, merger, reorganization, or sale, and transferred if the transaction closes, subject to applicable notice, consent, purpose-limitation, and deletion requirements; and
• To process sensitive or special-category Personal Information where necessary for approved research activities and in accordance with applicable law and Project Rules.

4. Third Party Services

We may disclose Personal Information to third parties that provide services on our behalf or that support the operation of the Services, including:

• Hosting, cloud infrastructure, storage, database, search, and security providers;
• Artificial intelligence, machine learning, and data-processing providers ;
• Authentication, identity verification, and communications providers;
• Analytics and performance providers;
• Payment, billing, subscription, and fraud-prevention providers;
• Integration and connectivity providers;
• Research, publication, and scholarly-record providers; and
• Professional advisers and legal service providers.

Personal Information may be processed in Canada, the United States, and other countries where our providers operate. A provider may also act as an independent controller where its own legal obligations require it.

Google user data

Tiptree’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use Google user data only to provide the Google integrations you enable. We do not use it to serve ads, for retargeting or marketing profiling, or to develop, train or improve generalized AI/ML models, and we do not allow humans to read it except as necessary to provide the Services at your request, for security and abuse prevention, or as required by law. You can revoke our access at any time in your Google Account settings or by disconnecting the integration, and you can request deletion through section 14.

The Services use Google Analytics and Grafana Faro for the usage analytics and performance monitoring described in section 5.

5. Cookies and Analytics Choices

We use necessary cookies or local storage for authentication, security, load balancing, and remembering privacy choices. We do not use third-party advertising cookies and does not sell information for targeted advertising. We do not set or read analytics cookies until you accept them where consent is required, and declining analytics does not prevent ordinary use of the applicable Service. You can change your choice through the “Privacy choices” link available here. Withdrawing consent does not affect processing that occurred lawfully before withdrawal. Browser controls may also block cookies, although account features may require strictly necessary cookies. We may send transactional messages needed for authentication, billing, security, or service delivery. We may also send marketing email or SMS with the consent or other authority required by law and include a working unsubscribe method. Opting out of marketing does not stop necessary service notices. Carrier message and data rates may apply to SMS.

Atlas specific: Atlas may also use necessary cookies or local storage to maintain project state. With consent where applicable, analytics, pre-sign-up journey linking, real-user monitoring, and session replay do not start until you accept the relevant category. Withdrawing consent does not prevent ordinary use of the application or project participation.

6. International Processing and Transfers

We and our subprocessors may process information in Canada, the United States, and other countries where approved providers operate. Those countries may have different privacy laws, and information may be available to their courts, law-enforcement, or national-security authorities under local law.

Before Personal Information is transferred to another jurisdiction, Tiptree will conduct required privacy impact assessment and enter into appropriate written agreements as required by applicable law. Where a jurisdiction requires specific transfer mechanisms, we will use an applicable adequacy decision, approved contractual clauses, or another recognized safeguard, together with supplementary measures where required. You may request information about the relevant safeguard through the contact details in section 14. For the avoidance of doubt, public repository publication is global by nature. Transfer safeguards applicable to a processor do not prevent a public record from being accessed worldwide; the project-specific notice must make that consequence clear.

7. Security

We use administrative, technical, and physical measures designed to protect Personal Information in proportion to its sensitivity, volume, purpose, and format. These safeguards include access controls, authentication, least-privilege restrictions, encryption in transit and for sensitive information at rest, separation of environments or information where appropriate, protected/secure infrastructure and development practices, logging, backups, confidentiality obligations, vendor review, and incident response. Where applicable, enterprise security commitments may be documented in an applicable Order or security schedule. No online system is guaranteed to be completely secure, where an incident creates a legally reportable risk, we will notify affected people, customers, and regulators as required, take reasonable steps to limit harm and prevent recurrence, and preserve required incident records

Atlas specific: Given the sensitivity of identity mapping data, comprehensive research session data, unpublished works, and integrity-related records, we require the implementation and maintenance of multifactor authentication for all privileged access accounts. Users must maintain unique account credentials, implement appropriate security measures to protect connected accounts and devices, regularly review and manage workspace permissions, and refrain from submitting regulated, sensitive, or restricted data unless expressly authorized under an applicable Order. Users acknowledge that pseudonymity does not constitute a security control or guarantee anonymity. Users are solely responsible for safeguarding their account credentials and must not disclose information that could directly or indirectly reveal their identity, nor submit restricted materials in contravention of the applicable Project Rules.

8. Retention

We retain records for the periods set out below, subject to any longer period required by law. We may retain a record beyond its stated period when required by law or a documented legal hold. During a legal hold, we isolate the affected records and restrict access to them. Deletion resumes when the hold ends.

We may retain irreversibly aggregated statistics that no longer identify a customer, user, conversation, or person. We will not attempt to re-identify such data, and de-identification will not be used to avoid a valid suppression request. Where applicable, an Order or DPA may specify shorter retention periods.

Atlas specific: We do not retain full raw transcripts permanently by default. After the seven-year period, we retain only the minimum durable evidence needed for IP title, attribution, reproducibility, and integrity, and delete irrelevant conversational detail.

9. Accuracy

We seek to ensure that information incorporated into profiles is derived from sources reasonably relevant to scholarly identity, that provenance is preserved, that private contact information is not harvested or repurposed, and that generated, inferred, or algorithmically derived content is clearly distinguished from source-based factual information. While we implement measures designed to promote the accuracy of profile information, we do not manually verify every profile, record, or data point. Users acknowledge that researchers, institutions, affiliations, roles, publications, and websites may change over time, and that automated identity resolution, matching, and deduplication processes may incorrectly combine, separate, attribute, or associate records. Lacuna is not designed, intended, or provided for the purpose of making decisions that produce legal, employment, educational, financial, or similarly significant effects concerning an individual. To the extent Personal Information is used in connection with any such decision-making activity, Lacuna will implement and maintain any accuracy, record preservation, correction, transparency, or other obligations required under applicable law.

10. Your Privacy Rights

Depending on your jurisdiction and the circumstances of the processing, you may have the right to:

• know whether we hold Personal Information and how it is used, processed and disclosed;
• access your Personal Information and receive a copy of it;
• request the correction of inaccurate or incomplete information, including where applicable affiliation, session, or scoring inputs;
• withdraw consent for future processing based on consent;
• object to processing based on legitimate interests, including profiling;
• request deletion, de-indexing, restriction of dissemination, suppression or account closure;
• obtain information regarding the use of automated-making processes and submit observations reviewed by a qualified individual;
• Where applicable, disconnect integration and revoke its tokens;
• Where applicable, opt out of marketing communications, targeted advertising, sale, or qualifying profiling activities;
• lodge a complaint with a competent privacy or data protection authority; and
• receive equal service and not be retaliated against for exercising a right.

11. Children

The Services features and accounts are intended for adults and are not directed to children. We do not knowingly create enriched professional or social profiles about a person under 18. A scholarly database may nevertheless contain a minor author's name or publication. If you believe a profile concerns a child or that a child submitted account information, contact us as soon as possible so that we may review and take appropriate action. Notwithstanding the foregoing, where applicable, if an authorized education deployment or project is intended for younger users, it requires separate terms, an age-appropriate notice, verified authorization, and a specific assessment before collection begins.

12. Third-Party Sites and Independent Users

Lacuna links to sources and can be queried by third-party MCP or API clients. Those third parties may independently collect Personal Information when you visit or use them and may act as separate controllers. Their privacy notices apply to their activities. This Policy does not govern a third party that copies a public Lacuna record without acting on our behalf. We strongly encourage you to review the privacy policies and data protection practices of any third-party platform or website before providing personal information to it.

13. Changes to This Policy

We may update this Policy from time to time. We will post revisions with an updated effective date and make prior versions available where appropriate. We will not use personal information previously collected for a purpose that is materially different from, incompatible with, or unrelated to the purposes for which it was originally collected solely by amending this Privacy Policy. Continued use of our Services after any posted changes constitutes your acceptance of those changes.

14. Contact and Complaints

Tiptree Advanced Systems Corporation, 1100 René-Lévesque Boulevard West, 25th Floor, Montréal, Québec, H3B 5C9

Privacy Officer: privacy@tiptreesystems.com; Questions, complaints, and rights requests may use the email above.

If you are not satisfied, you may lodge a complaint with the competent privacy or data protection authority in the jurisdiction where you reside or where you believe an infringement has occurred.