Secure sign-in session
Essential · First party
- Purpose
- Keeps authenticated users signed in and protects the session.
- Duration
- Up to 12 hours, renewed during active use.
Technical identifier
evidencestudio_session
AI-powered evidence synthesis
AI-assisted systematic reviews from search to synthesis.
An integrated, AI-enabled workspace that helps research teams streamline literature search, screening, data extraction, meta-analysis, and living updates, with transparent human oversight.
End-to-end review workflow
Human-in-the-loop decisions
Audit-ready evidence trail
Academic review teams
Clinical guideline groups
Evidence synthesis units
Health technology assessment teams
Why EvidenceStudio
Faster reviews.
Faster reviews.
Transparent decisions.
Bring every review stage into one controlled workspace while keeping AI-supported work visible and reviewable.
One connected workspace
Coordinate search, screening, full-texts, extraction, and meta-analysis without scattering the review across disconnected files.
Flexible review rules
Use single-AI, dual-AI, dual-human, or human verification workflows depending on the stage, protocol, and sensitivity required.
Reproducible evidence trail
Keep source files, AI outputs, reviewer judgments, extracted values, and analysis results connected to the project.
Workflow
From search to synthesis, with living updates.
Move studies through a clear four-stage pathway, with living searches feeding each subsequent step.
1
Search
Run literature searches, save results, and schedule living updates.
2
Screen
Screen abstracts and full texts with AI-supported, human-only, or hybrid decision rules.
3
Extract
Extract baseline characteristics and outcome data from study reports, then verify values when needed.
4
Analyze
Run pairwise and network meta-analyses, then generate plots and analysis outputs.
Search
Screen
Verify
Extract
Analyze
Report
Collaboration
Built for coordinated review teams.
Assign users, manage roles, and keep reviewer activity connected across each project.
Project collaboration
Assign users, manage roles, and keep reviewer activity connected to the project record.
Human oversight
Choose single-AI, dual-AI, dual-human, or human verification workflows according to the review protocol.
Transparency
Every decision remains visible.
Keep the sources, AI outputs, reviewer judgments, and analysis files needed for reproducible evidence synthesis.
Traceable decisions
Keep prompts, models, providers, source files, decisions, and user judgments connected at every stage.
Review outputs
Download review results, audit records, PRISMA diagrams, plots, and analysis tables.
Contact
How can we help?
Tell us whether you are exploring EvidenceStudio, need support, or would like to discuss research collaboration.
Get in touch
Questions about the platform, access, technical support, or collaboration are welcome.
EvidenceStudio
Secure project access for collaborative evidence synthesis.
Reset your password
Enter your username or verified email address. If it matches an active account, we will send a secure reset link.
Terms of Service
These Terms of Service define the baseline rules for accessing and using EvidenceStudio. They are designed to protect users, project data, the application, and the integrity of evidence-synthesis work.
Agreement and definitions
- EvidenceStudio means the application, workflow tools, reports, documentation, local or hosted services, and related features made available by the app owner.
- Account Data means usernames, contact details, roles, authentication and security records, licence limits, and project memberships used to administer the service.
- Customer Project Content means search strategies, records, study reports, prompts, criteria, screening decisions, extracted values, notes, audit records, uploaded files, and project outputs supplied or generated within a customer project.
- Output means a workbook, report, table, plot, audit file, or other result generated from Customer Project Content. Project Entitlement means the project, user, storage, update, or processing allowance assigned to an account or subscription.
- Support Access means project-Administrator-authorized, temporary, read-only access for a stated support purpose. Restricted Operational Access means short-lived, read-only access used only by the platform owner for a documented security, availability, recovery, or legal necessity.
- By signing in, creating a project, or using a project, each user confirms that they are authorized to use EvidenceStudio and agrees to these Terms and the Use Policy.
Service scope and access
- EvidenceStudio supports systematic reviews, living literature updates, screening, data extraction, PRISMA reporting, and meta-analysis workflows.
- The app provides research workflow support. It does not provide medical, legal, regulatory, financial, or other licensed professional advice.
- Access is limited to authorized users and projects. User accounts must not be shared, resold, sublicensed, transferred, or used by anyone other than the assigned user.
- Each Project Entitlement is intended for one genuine evidence-synthesis project and its legitimate amendments or living updates. Users must not delete, replace, or repurpose project content to evade licensed project, user, update, storage, or processing limits.
- Project administrators are responsible for assigning users, roles, project limits, and access rights, and for removing users who no longer need access.
- Access may be restricted, suspended, or terminated when needed to protect the application, investigate suspected misuse, address security risk, enforce usage limits, or enforce these Terms.
Customer data and user responsibilities
- As between the parties, the customer retains its rights in Customer Project Content and Outputs. EvidenceStudio retains its rights in the service, software, interface, documentation, and product functionality.
- The customer grants EvidenceStudio only the limited permission needed to host, process, transmit, secure, maintain, support, back up, restore, and provide the service, and to follow documented customer instructions or legal obligations.
- Customer Project Content is not used to train shared or generally available AI models unless the customer gives separate, explicit authorization. Customer-selected AI providers may process submitted content under their own terms and settings.
- Users are responsible for the accuracy, quality, integrity, completeness, legality, reliability, and appropriateness of all project data and outputs they use or share.
- Users must have the necessary rights, permissions, licences, or institutional access to upload, store, download, process, or merge abstracts, full-text PDFs, supplementary materials, and extracted data.
- Users must comply with applicable laws, institutional policies, publisher terms, API-provider terms, and ethics or governance requirements for their review.
- Users must keep account credentials secure and promptly report suspected unauthorized access, data exposure, or misuse.
- EvidenceStudio may process customer data to provide the service, maintain audit trails, support troubleshooting, improve reliability, protect security, and comply with lawful or administrator-approved instructions.
- Do not upload personal data, protected health information, confidential records, proprietary materials, or regulated datasets unless your organization has approved that processing and appropriate safeguards are in place. Published bibliographic metadata and publicly available article information may be used as part of normal review workflows.
Platform administration and temporary access
- The Platform Owner has the highest platform authority and may administer accounts, licence limits, project ownership, service status, maintenance, backups, and other platform operations through a separate control plane. The owner may delegate selected control-plane permissions to designated Platform Administrators and may change or revoke that access at any time.
- Platform Administrators may act only within the permissions granted by the Platform Owner. They cannot appoint or manage platform operators, alter the owner account, perform protected project reset or deletion, permanently delete accounts, initiate restricted operational project access, or download or restore whole-service backup archives.
- Platform roles alone do not provide routine access to scientific project content. Project content remains subject to project membership, customer-authorized support access, or the narrowly restricted operational process described below.
- Platform-level project reset or permanent deletion is restricted to the Platform Owner and protected by identity reauthentication, authenticator verification, a verified safeguard export, a short-lived project-specific confirmation, and immutable lifecycle logging. Such actions should be performed only on documented customer instruction, account termination, security or recovery necessity, legal obligation, or another authorized operational basis.
- A content reset removes workflow records and files while retaining the project account structure, memberships, and permission settings. Permanent project deletion also removes that project structure. Verified safeguard archives and security history may remain subject to contractual retention, backup rotation, legal duties, dispute preservation, and security requirements.
- Support Access must be authorized by a project Administrator, limited to one project and a stated purpose, read-only by default, automatically expiring, immediately revocable, and recorded in access history.
- Restricted Operational Access may be used only when reasonably necessary for a security incident, service recovery, availability problem, or legal obligation. It requires identity reauthentication, a written reason, short expiry, enhanced logging, and notification to project administrators where appropriate and legally permitted.
- Temporary access does not expose passwords, password hashes, session or recovery tokens, invitation links, stored provider API keys, encryption keys, or other authentication secrets.
AI-assisted evidence synthesis
- AI outputs depend on source files, extracted text, prompts, provider behavior, selected models, and user settings. Outputs may be incomplete, inaccurate, inconsistent, or unsuitable for a given review question.
- AI-generated screening decisions, extracted values, rationales, summaries, and analyses must be reviewed by qualified humans before publication, clinical use, policy decisions, regulatory work, or other high-impact use.
- If a workflow allows AI-only progression, the user remains responsible for the selected decision rule, the resulting outputs, and the documentation needed for reproducibility.
- Users should preserve prompt versions, provider and model details, source files, decisions, extracted values, human judgments, and final outputs where auditability or publication readiness matters.
Third-party services and full-text access
- PubMed, publisher websites, AI model providers, R packages, hosting providers, and other integrations are third-party services governed by their own terms, availability, rate limits, data rules, and costs.
- Full-text discovery is intended to help users locate materials they may lawfully access. EvidenceStudio does not authorize bypassing paywalls, logins, copyright restrictions, publisher licences, or institutional access rules.
- Users are responsible for any API keys, provider accounts, institutional access, usage charges, and data-handling obligations connected to third-party services.
Intellectual property and restrictions
- EvidenceStudio, including its interface, workflow design, code, templates, documentation, generated report formats, and product features, remains the property of the app owner or licensors.
- Users may not copy, reverse engineer, decompile, scrape, resell, lease, sublicense, frame, mirror, or use EvidenceStudio to build a competing service, except where law expressly allows.
- Feedback or suggestions may be used to maintain, improve, and develop EvidenceStudio without compensation, while respecting any confidentiality obligations that apply.
Availability, export, and limits
- EvidenceStudio is provided as a workflow tool without a guarantee of uninterrupted availability, perfect security, error-free operation, provider uptime, or fitness for a specific review, publication, regulatory, or commercial purpose.
- Features, models, provider availability, cost, rate limits, and third-party integrations may change over time.
- Users should regularly export or back up important project outputs, workbooks, study reports, audit trails, and reports according to their organization’s retention policy. EvidenceStudio may provide an export period before planned account closure where commercially and technically reasonable.
- Planned maintenance will be announced where practicable. Emergency maintenance may occur without advance notice when needed to protect data, users, or service availability.
- Suspension or termination may follow non-payment, serious misuse, security risk, legal requirement, or material breach. Where risk and law permit, proportionate notice and a reasonable opportunity to export customer content will be provided.
- Sections concerning customer data responsibility, intellectual property, confidentiality, AI limitations, misuse, audit trails, disclaimers, and liability continue to apply after access ends where relevant.
- These Terms are a product baseline for EvidenceStudio. Commercial deployment, billing, service-level terms, data-processing terms, liability limits, governing law, and dispute-resolution clauses should be reviewed and adapted by legal counsel.
Last updated: July 21, 2026
This Use Policy explains acceptable and prohibited uses of EvidenceStudio. It supports lawful, secure, transparent, and responsible AI-powered evidence synthesis.
Responsible evidence synthesis
- Use EvidenceStudio for legitimate evidence-synthesis activities, including literature search management, title/abstract screening, full-text screening, data extraction, evidence verification, and meta-analysis.
- Use AI outputs as assistive evidence, with appropriate human review, source checking, and documentation of final decisions.
- Use full-text identification only for materials you may lawfully access, download, store, and analyze.
- Maintain protocols, eligibility criteria, prompts, model/provider selections, source files, decisions, extracted values, human judgments, and audit trails when transparency or publication readiness matters.
Illegal, harmful, or deceptive use
- Do not use EvidenceStudio for unlawful, harmful, deceptive, abusive, discriminatory, harassing, or rights-violating activity.
- Do not use the app to create, promote, or distribute false, misleading, fabricated, defamatory, infringing, discriminatory, or unsupported scientific or medical claims.
- Do not impersonate another person, misrepresent your identity or affiliation, conceal the role of AI where disclosure is required, or use the app for academic misconduct.
- Do not use EvidenceStudio in environments where app failure could directly cause death, serious injury, severe physical harm, or severe environmental damage.
Data, privacy, and intellectual-property rules
- Do not upload or process confidential, proprietary, personal, health, or sensitive data unless you have authorization, a lawful basis, and appropriate safeguards.
- Do not upload, store, download, copy, share, publish, or analyze content unless you have the rights, licences, permissions, or institutional access needed for that use.
- Do not use full-text discovery, DOI lookup, OpenURL, VPN access, or institutional access to bypass paywalls, logins, publisher restrictions, technical access controls, copyright rules, or licence terms.
- Do not remove required copyright, citation, source, provenance, or audit-trail information from project records or outputs.
AI and high-impact limits
- Do not treat AI outputs as clinical, legal, regulatory, financial, employment, insurance, education, or other high-impact advice without qualified human review and responsibility.
- Do not misrepresent AI-generated or AI-assisted work as purely human-generated, and do not remove audit-trail information where transparency is required.
- Do not use AI outputs to fabricate eligibility decisions, extraction values, citations, trial data, meta-analysis results, or conclusions.
- When discrepancies arise between providers, reviewers, or source documents, resolve them transparently and preserve both the original outputs and the final decision.
Security and network abuse
- Do not introduce malware, malicious code, credential-harvesting content, denial-of-service traffic, or other harmful scripts, files, or instructions.
- Do not probe, scan, test, bypass, disable, overload, interfere with, or attempt to defeat authentication, authorization, rate limits, safety controls, or security measures without written authorization.
- Do not use automated access, crawling, scraping, excessive jobs, or bulk downloads in a way that disrupts EvidenceStudio, PubMed, publisher sites, API providers, hosting providers, or other users.
- Do not send spam, unsolicited messages, forged messages, or abusive communications through any connected workflow.
Platform integrity and fair use
- Do not share accounts, sell access, exceed assigned project or user limits, evade usage limits, or use customer access to operate a competing service.
- Do not delete, rename, replace, or repurpose a licensed project, its records, or its outputs to use one Project Entitlement for unrelated reviews.
- Do not access or attempt to access another account or project without authorization, and do not obtain, disclose, or misuse another user’s confidential information or credentials.
- Do not alter, remove, conceal, falsify, or interfere with audit records, reviewer attribution, access history, source provenance, or security logs.
- Do not misuse stored provider connections, temporary API keys, batch jobs, scheduled updates, or automated workflows, including by submitting data that the account is not authorized to process.
- Use provider APIs, literature-search tools, and full-text retrieval features within normal research workloads, documented project limits, and third-party terms.
- Project administrators should remove inactive users, review access rights, and maintain appropriate project-level controls.
Monitoring, enforcement, and reporting
- EvidenceStudio may respond proportionately to suspected violations through a warning, temporary feature restriction, session or access revocation, account suspension, investigation, content isolation, or permanent termination for serious or repeated misuse.
- The app owner or project administrator may preserve relevant logs and records while investigating suspected misuse or security incidents, subject to applicable law and contractual obligations.
- EvidenceStudio may cooperate with lawful requests from regulators, courts, institutions, security teams, or service providers when required.
- Report suspected misuse, data exposure, unauthorized access, security incidents, or unsafe outputs to the project administrator or platform owner promptly.
Last updated: July 21, 2026
This Privacy Notice explains how EvidenceStudio handles personal data when people visit the website, contact us, create an account, or use the hosted application. It applies globally, subject to rights and requirements that may vary by location.
Who is responsible
EvidenceStudio generally acts as controller for the public website, Account Data, security, billing and platform administration. When a customer determines why and how personal data is placed in a project, the customer generally acts as controller and EvidenceStudio processes that Customer Project Content on the customer’s documented instructions. The legal role may vary by context and applicable law.
Data we handle
- Account and profile data: username, display name, email address, role, account status, project membership, and password-security records. Passwords are stored only as protected hashes.
- Project and workflow data: search strategies, bibliographic records, study reports, review criteria, screening decisions, reviewer notes, extracted values, analysis settings, outputs, and audit history submitted by authorized users.
- Technical and security data: session identifiers, authentication and multi-factor events, event outcome and time, a masked network range, keyed pseudonymous network and browser signatures, a general browser/device category, encrypted authenticator enrollment material, hashed one-time recovery codes, rate-limit and fraud-prevention signals, and operational logs needed to protect and run the service. EvidenceStudio's authentication history does not store the full source IP address or full browser user-agent string. Infrastructure and security providers may process source IP and request information separately to deliver and protect the service under their own documented retention controls.
- Privileged-access records: project, person, access type, reason, authorizer, start, expiry, revocation, pages requested, and related operational events. Request bodies, passwords, API keys, and authentication tokens are not written to this history.
- Aggregated public-site analytics: page paths, referrer hosts, device and browser categories, approximate country, and page-performance measurements used to understand and improve the public website. EvidenceStudio configures this measurement without analytics cookies, browser storage, individual fingerprinting, query strings, or tracking inside authenticated project workspaces.
- Communications: information supplied through contact, invitation, verification, password-recovery, support, or maintenance messages.
Why we use data
- Provide accounts, project access, collaboration, evidence-synthesis workflows, exports, and support.
- Authenticate users, prevent abuse, investigate incidents, maintain auditability, and protect the platform and its users.
- Send requested service communications, including invitations, verification, password recovery, maintenance notices, and security messages.
- Measure aggregated public-website use and performance so the homepage can be improved without profiling individual visitors.
- Meet legal obligations and establish, exercise, or defend legal claims where necessary.
EvidenceStudio does not sell personal data or use it for cross-context behavioral advertising.
Customer Project Content is not used to train shared or generally available AI models without separate, explicit customer authorization.
Depending on the applicable law and context, processing may rely on performance of a contract, legitimate interests in operating and securing the service, compliance with law, consent, or another lawful basis available in the relevant jurisdiction.
Authentication security history
EvidenceStudio records a limited history of successful and failed sign-ins, account locks, sign-outs, password-recovery activity, and authenticator events to detect misuse, help users recognize suspicious access, investigate incidents, and protect accounts. Within the European Economic Area and United Kingdom, this essential security processing generally relies on EvidenceStudio's legitimate interests in securing the service and its users, and on legal obligations where they apply. It is not used for advertising, behavioral profiling, or decisions that produce legal or similarly significant effects.
- Each user can view only their own recent authentication activity from the Profile window.
- The Platform Owner and only delegated Platform Administrators with audit permission can review the wider history for security and incident response. Project Administrators do not receive access to other users' authentication history merely because they manage a project.
- Network information is reduced to an IPv4 /24 or IPv6 /64 range, and browser information is reduced to a general device category. Keyed signatures support correlation during an investigation without displaying the source value. These controls reduce identifiability, but the resulting records remain personal data where they can be linked to an account.
- Passwords, password hashes, authenticator codes, recovery codes, API keys, session tokens, invitation tokens, form bodies, and complete browser identifiers are excluded from this history.
Services and international transfers
EvidenceStudio currently relies on service providers such as Render for hosting, Cloudflare for traffic protection, human verification, and cookie-free public-site analytics, and configured transactional email services. Research workflows may also send information to PubMed or NCBI, publishers, and AI providers selected or configured by the customer. Provider identity, processing location, and transfer mechanism may vary with customer configuration. Where required, EvidenceStudio and the customer should use an appropriate contractual or legal transfer safeguard and document relevant subprocessors.
Support and operational access
EvidenceStudio does not routinely inspect Customer Project Content. Project content may be accessed through Administrator-authorized Support Access or narrowly restricted operational access for security, availability, recovery, or legal necessity. Such access is least-privilege, read-only by default, time-limited where practicable, revocable, and logged. Project administrators are notified where appropriate and legally permitted.
When an authorized project reset or deletion is requested, EvidenceStudio creates a project safeguard archive before the action can be confirmed. The archive may contain Customer Project Content and is protected and retained according to the applicable customer instruction, agreement, backup cycle, legal obligation, incident hold, and security requirements.
Retention and protection
- Personal data is retained only for as long as needed for the service, security, legal obligations, project continuity, and documented retention requirements.
- Ordinary authentication events are retained for 90 days by default. Events for Platform Owner and Platform Administrator accounts, authenticator security events, and state-changing Platform Administration events are retained for 365 days by default because of their greater security and accountability risk. Expired records are deleted automatically. A different documented period may apply where required by law, contract, or a specific incident-preservation obligation.
- Deleting a user account does not automatically erase historical project decisions or attribution when those records are needed for scientific integrity, auditability, or the rights of other project participants.
- Project, account, support-access, audit, backup, and security records may follow different retention periods. Applicable customer agreements, documented instructions, legal duties, incident-preservation needs, and backup rotation determine the final period. Data is deleted or de-identified when it is no longer required, subject to those limits.
- EvidenceStudio uses access controls, protected password storage, secure sessions, rate limits, verification controls, and operational safeguards. No online service can guarantee absolute security.
Your choices and rights
Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or obtain a copy of personal data, withdraw consent, or appeal a decision. You may also complain to an appropriate privacy or data-protection authority. Requests can be submitted through the Contact form and may require identity verification. Some information may be retained where law, security, research integrity, or the rights of others require it.
Children and changes
EvidenceStudio is intended for professional research use and is not directed to children. This notice may be updated when the service, providers, or legal requirements change. Material changes will be communicated where required.
Security incidents
EvidenceStudio investigates suspected personal-data breaches, takes reasonable containment and remediation steps, preserves relevant evidence, and notifies affected customers or authorities when required by applicable law or contract. Customers remain responsible for their own downstream notification duties as controllers.
Last updated: July 22, 2026
This Data Processing summary describes the baseline safeguards used when EvidenceStudio processes personal data in Customer Project Content on behalf of a customer. Organization-specific processing should be governed by an executed Data Processing Addendum where required.
Account authentication, platform security, abuse prevention, and service-administration records are handled separately as EvidenceStudio controller data as described in the Privacy Notice. They are not made available to a customer merely because that customer administers a project.
Documented instructions and purpose limitation
- EvidenceStudio processes Customer Project Content only to provide, secure, maintain, support, back up, restore, and improve the reliability of the contracted service, or to comply with lawful instructions and obligations.
- Customer Project Content is not sold, used for behavioral advertising, or used to train shared AI models without separate explicit authorization.
- The customer is responsible for lawful instructions, data minimization, notices, legal bases, rights management, and determining whether sensitive or regulated data may be used.
Confidentiality and security
- Access is limited to authorized personnel and services with a need to know. Temporary support and restricted operational access are purpose-bound, time-limited, read-only by default, and auditable.
- EvidenceStudio applies authentication, mandatory multi-factor verification for Platform Owner and Platform Administrator accounts, least-privilege authorization, protected credential storage, encrypted provider connections, immediate session revocation after privileged-access changes, rate limits, logging, verified project safeguards, backups, release checks, and incident-response measures appropriate to the service.
- Privileged-account authenticator recovery requires a verified email, a short-lived single-use link, and password reauthentication; recovery revokes active sessions, requires fresh authenticator enrollment, and is recorded in security history. Exceptional offline owner recovery is restricted to authorized infrastructure operators and is also audited.
- Passwords, API keys, encryption keys, session tokens, invitation tokens, and recovery links are excluded from support-access interfaces and audit event details.
Subprocessors, assistance, and data lifecycle
- EvidenceStudio may use subprocessors for hosting, security, email, and customer-selected integrations. The customer should review applicable provider terms and transfer safeguards before submitting regulated data.
- EvidenceStudio will provide reasonable assistance with security incidents, data-subject requests, deletion or return, and compliance information, taking account of the service and information available.
- At the end of service, Customer Project Content is returned, exported, archived, or deleted according to the applicable agreement, documented instructions, backup cycle, audit obligations, and legal retention requirements.
This summary is not a substitute for an organization-specific DPA, security schedule, subprocessor schedule, or legal advice. Those documents should be finalized with qualified counsel before regulated or enterprise deployment.
Last updated: July 22, 2026
EvidenceStudio uses technologies required to provide and protect the service, remember settings you choose, and measure the public website without analytics cookies.
✓
No advertising cookies. Public-site analytics are aggregated and do not use cookies, browser storage, individual fingerprinting, or authenticated project activity.
Technologies in use
Cloudflare Web Analytics
Cookie-free · Public website only
- Purpose
- Provides aggregated page-use and performance information to improve the public EvidenceStudio website.
- Retention
- Cloudflare reports unsampled measurements for 7 days and makes aggregated analytics available for up to 6 months.
Information and scope
May include page path, referrer host, device type, browser, operating system, approximate country, and page-performance measurements. It does not use analytics cookies or local storage, collect URL query strings, create individual profiles, or run inside the authenticated EvidenceStudio workspace.
Cloudflare security
Essential · Third-party security
- Purpose
- Helps prevent automated abuse and supports human-verification checks.
- Duration
- Varies by the security control and Cloudflare configuration.
Provider and identifiers
Cloudflare may set cf_clearance, __cf_bm, or _cfuvid when its security controls are engaged.
Interface preferences
Essential · Browser storage
- Purpose
- Restores interface and navigation choices on this device and remembers that this notice was acknowledged.
- Duration
- Up to 180 days from the most recent save.
Settings stored
May include sidebar appearance, navigation state, selected project, status-panel state, and PDF viewer size. It does not include API keys, passwords, study reports, extracted values, or project datasets.
Your controls
You can clear interface preferences here or remove cookies and site data through your browser. Clearing preferences does not delete your account or project data. Blocking essential technologies may prevent sign-in, security verification, or other core functions.
For related personal-data processing, legal bases, service providers, and privacy rights, see the .
Last updated: July 16, 2026