Compliance built into the platform
How Acolher supports privacy rights, responsible AI, fair employment practices, accessibility and enterprise audit needs in the United States — and how that architecture extends to new countries.
Acolher is wellbeing support, not medical care
Acolher provides educational, emotional and self-care support powered by AI. It is not a healthcare service, not treatment, and not a substitute for a licensed professional.
- Acolher does not diagnose, treat, cure or prevent any disease, disorder or health condition, and does not provide medical, psychological, psychiatric, legal or financial advice.
- Acolher is not a medical device and has not been reviewed, cleared or approved by the U.S. Food and Drug Administration. Nothing in the product should be read as a clinical claim or a promised health outcome.
- Acolher does not prescribe, recommend, adjust or discontinue medication. Decisions about medication or treatment belong to you and your licensed clinician.
- Content is generated by AI and can be incomplete or inaccurate. Do not rely on it for any clinical, diagnostic or safety-critical decision.
- Check-ins, cognitive activities, radar scores and summaries are self-reported reflections and educational signals only. They are not screenings, not clinical assessments and not test results.
- The doctor summary you can generate is a convenience copy of what you yourself recorded, meant to help you talk to a clinician. It is not a medical record and not a clinical interpretation.
- Individual results are not typical, not guaranteed and not predictable. We make no claim that using Acolher improves any medical or cognitive outcome.
- Acolher does not provide emergency or crisis services and is not monitored by clinicians in real time.
If you are in danger or in crisis
In the United States, call or text 988 (Suicide & Crisis Lifeline) or call 911 for an emergency. In Brazil, call CVV at 188 or SAMU at 192. Please reach a human service — do not wait for a reply inside the app.
Health-related data and breach notification
Acolher is not a HIPAA covered entity or business associate, does not provide treatment and does not sign BAAs. Health-related information exists only because you chose to type it in. If we learn that such information was acquired without your authorization, we will notify affected users and, where the FTC Health Breach Notification Rule applies, the Federal Trade Commission, describing what happened, what information was involved and what you can do — following the timelines that rule requires.
Your privacy rights in the United States
This notice describes the personal information Acolher collects, why we collect it, who processes it on our behalf and the rights you can exercise. It is written to meet the disclosure expectations of the California Consumer Privacy Act as amended by the CPRA, and of the consumer privacy statutes of Colorado, Virginia, Connecticut, Utah, Texas, Oregon and Montana.
Who is responsible
The service is operated by the Acolher team at acolher.live. For any privacy matter, write to privacy@acolher.live and we will respond directly.
Registered legal entity and postal address: to be published here once the U.S. entity registration is complete.
Categories of personal information we collect
- Identifiers: the email address you sign up with, an internal account identifier, and a display or preferred name if you provide one.
- Account and preference data: language, country, timezone, communication style, retention window, personalization level, notification settings and consent choices.
- Content you create: chat messages, journal entries, check-ins, goals, habits, saved memories, radar and CBT records, cognitive activity results and voice transcripts you choose to record.
- Commercial information: subscription plan, status, renewal period and payment events. Card numbers never reach Acolher — they are handled by our payment processor.
- Sensitive personal information: health, mental-health or wellbeing details appear only if you type them. We use them solely to deliver the support you asked for, never to infer characteristics about you and never for advertising or profiling.
- Technical and security data: authentication events, error diagnostics, and coarse request metadata needed to keep the service working and to enforce free-usage limits.
Where the information comes from
- Directly from you: sign-up, settings, conversations and anything you record in the product.
- Automatically from your use of the service: session, device and error information generated as you use the app.
- From your payment provider: subscription status events, so your access matches what you paid for.
- From your employer, only if your organization enrolled you: your membership, role and department. Your personal content is never shared with your employer, and organizational reporting is aggregated with a minimum cohort size.
Why we use it
- To provide the conversations, records, summaries and features you request.
- To personalize tone, language and continuity — only within the consent scopes you turned on.
- To keep your account secure, prevent abuse and enforce free-usage limits.
- To process subscriptions, renewals, cancellations and refunds.
- To respond to your support and privacy requests.
- To meet legal obligations and to protect the rights and safety of users.
Who we disclose it to
- Service providers under contract, acting only on our instructions: cloud hosting and database infrastructure, the AI model providers that generate replies, transcription for voice you record, email delivery, and payment processing.
- Nobody for money. We do not disclose personal information to data brokers, advertisers or ad networks.
- Legal recipients, only when required by valid legal process or to protect someone's safety, and limited to what is necessary.
No sale, no cross-context advertising, no profiling
Acolher does not sell personal information and does not share it for cross-context behavioral advertising, in the meaning those terms have under CCPA/CPRA and the other state statutes. We do not use your data for targeted advertising and do not run advertising or cross-site tracking cookies, so there is nothing to opt out of on that front. We also do not use automated decision-making or profiling to make decisions that produce legal or similarly significant effects about you. Because we do not sell or share, there is nothing to authorize through a Global Privacy Control signal — and we would honor an opt-out signal if that ever changed.
Right to know and access
Ask what categories and specific pieces of personal information we hold, where they came from, why we use them and who processes them.
Right to portability
Receive a structured, machine-readable copy of your data. Available immediately from your account settings.
Right to correct
Fix inaccurate personal information. Profile fields and stored memories are directly editable.
Right to delete
Delete memories, conversations, wellbeing records or your entire account. Deleting the account removes the data tied to it.
Right to limit sensitive information
Turn off any consent scope, including health-related records. Withdrawing a scope stops that processing and removes the data that depended on it.
Right to opt out
You may opt out of sale, sharing for targeted advertising and profiling. We do none of these, so there is nothing enabled to disable.
Right to non-discrimination and non-retaliation
Exercising any right never changes your price, your plan or the quality of support you receive.
Right to appeal
If we decline a request, you may ask us to reconsider, as the Colorado, Virginia, Connecticut, Texas, Oregon and Montana statutes provide.
How to exercise your rights
- In the app: open Account and Privacy to view your data, edit or delete memories, export everything, change your retention window, withdraw a consent scope or delete your account.
- By email: write to privacy@acolher.live with the request you want to make. Say which right you are exercising, and use the email address on your account so we can locate it.
- Authorized agents: an agent may submit a request on your behalf with written permission; we may contact you to confirm the authorization and the agent's identity.
- To appeal a decision: reply to our response, or write to privacy@acolher.live with the word Appeal in the subject line.
How we handle a request
- We confirm receipt within 10 business days.
- We verify that the request really comes from you — usually by confirming control of the account email. For deletion or a copy of sensitive information we may ask for one additional confirmation.
- We respond substantively within 45 days, and may extend once by another 45 days when a request is complex, telling you why.
- We do not charge for a request, unless it is manifestly unfounded or excessive, in which case we explain before doing anything.
- If we deny a request, we say which exemption or legal basis applies and how to appeal.
How long we keep information
- Content you create is kept until you delete it, or until the end of the retention window you chose in your settings.
- Account and preference data is kept while your account exists.
- Payment and subscription records are kept as long as tax, accounting and dispute-resolution obligations require, even after account deletion.
- Security and privacy-event logs are kept for a limited period so we can investigate abuse and evidence that requests were honored.
- Deleting your account removes the personal data tied to it; backups and logs age out on their normal cycle.
Children and teens
Acolher is not directed to children. We do not knowingly collect personal information from anyone under 13, and accounts require age confirmation. If you believe a child used the service, write to privacy@acolher.live and we will delete the account and its data.
Changes to this notice
When this notice changes materially we update the date shown here and, where the change affects how we use information you already gave us, we tell you inside the app before it takes effect.
Notice last updated 2026-08-23
Core principles
Ten commitments that shape how the product is architected, not only how it is described.
Privacy by design
Personal content is scoped to the person by default at the database layer, not by application convention.
Compliance by design
Access, correction, deletion, portability and consent are product surfaces, not manual back-office tickets.
Responsible AI
Inviolable rules sit above every prompt: no diagnosis, no fabrication, no manipulation.
Human oversight
Safety, governance and knowledge changes require explicit human approval before release.
Transparency
We publish what is live, what is in progress and what is only planned.
Security
Encryption in transit and at rest, row-level access rules, role separation and append-only audit logs.
Accountability
Administrative and analytics access is logged and attributable.
Accessibility
WCAG-oriented design is part of the definition of done for every screen.
Ethics
No dark patterns, no engagement manipulation, no use of wellbeing data against a person.
Continuous improvement
Policies, reviews and controls are re-examined on a schedule and after any finding.
Legal architecture
Not every customer is subject to the same rules. Compliance capabilities are configurable by customer, industry and jurisdiction rather than hard-coded to one regime.
Person layer
Consent scopes, retention window, personalization level and memory switches live on the individual's own record and always win over organizational settings.
Organization layer
Roles (employee, manager, HR admin), campaign participation, notification policy and access permissions are configured per organization.
Jurisdiction layer
Locale, crisis resources, terminology and privacy-request handling adapt by region; new countries are added as configuration, not as a rewrite.
Enforcement layer
Database row-level rules, security-definer aggregate functions and a 5-person minimum cohort enforce the boundaries regardless of which UI is used.
Because enforcement lives in the database rather than in a screen, an organization cannot configure its way into seeing an individual's content.
Privacy compliance
The mechanics expected by CCPA/CPRA and the Colorado, Virginia, Connecticut and Utah statutes are built into the product. Contractual and notice obligations are handled per customer agreement.
Consent management
Six independent scopes — long-term memory, personalization, pattern analysis, conversation history, progress tracking and connected services — all off by default.
Privacy preferences
Personalization level, response style and memory behavior configurable per person.
Cookie preferences
No advertising or cross-site tracking cookies are used, so there is nothing to opt out of.
Access requests
Self-service view of everything stored about the person.
Correction requests
Profile fields and stored memories are directly editable.
Deletion requests
Scoped erasure — memories, conversations, pattern data or everything at once.
Portability requests
One-click structured export in a machine-readable format.
Retention controls
Per-person retention window; data past the window is removed.
Processing restrictions
Withdrawing a scope stops that processing and removes the data it depended on.
Children's privacy
Acolher is not directed to children; age confirmation is required and accounts under the supported age are not intended users.
Privacy request audit trail
Consent changes and privacy events are recorded with policy version and timestamp.
Sale and sharing
Personal information is not sold or shared for cross-context behavioral advertising.
Employment compliance
Wellbeing data must never become an employment instrument. This is enforced technically, not only contractually.
Wellbeing information is never used for
- Hiring decisions
- Termination decisions
- Promotion decisions
- Compensation decisions
- Performance evaluation
- Disciplinary action
- Individual ranking, scoring or comparison of employees
Anonymous analytics are used only to
- Understand aggregated wellbeing trends across a team or organization
- Identify workload, recovery and psychological-safety pressures at group level
- Design campaigns, learning and support that address those pressures
- Measure whether an organizational initiative helped, in aggregate
Accessibility
Employee experiences are designed against WCAG 2.2 AA expectations and evaluated during development.
Keyboard navigation
Every interactive control is reachable and operable by keyboard with a visible focus state.
Screen readers
Semantic landmarks, labeled controls and accessible names on icon-only actions.
Color contrast
Text and interface colors are drawn from a token palette designed to meet AA contrast.
Resizable text
Relative units throughout, so browser and OS text scaling does not break layouts.
Reduced motion
Animations respect the operating system's reduced-motion preference.
Accessible forms
Associated labels, described errors and status messages that are not color-only.
Responsive layouts
Mobile-first layouts with tap targets sized for touch.
Captions and media alternatives
Audio and video practices will ship with captions and transcripts as that content is added.
Continuous evaluation
Accessibility checks are part of the review before a screen ships; we have not commissioned an external VPAT/ACR yet.
Workplace wellbeing
The platform supports healthier work environments through education and support. It does not replace employer responsibilities for workplace safety and employee wellbeing.
Burnout prevention
Early-signal education, recovery routines and workload-boundary practices.
Psychological safety
Team-level indicators and manager guidance on speaking up and error tolerance.
Healthy leadership
An AI leadership coach with themes grounded in organizational psychology.
Stress reduction
Guided practices from 1 to 10 minutes in the wellbeing center.
Healthy communication
Difficult conversations, feedback and boundary-setting modules.
Resilience
Support networks, meaning-making and recovery habit design.
Work-life balance
Break reminders, quiet hours and disconnection practices.
Healthy workplace culture
Voluntary campaigns and team goals, with participation never individually reported.
Responsible AI governance
What we document and evaluate for every AI system in the platform.
Model documentation
Which models are used, for what purpose and with which limits.
Prompt documentation
Governance, safety, specialist and quality instructions kept as reviewable source.
Model version history
Model changes are versioned and reviewed before production.
Knowledge version history
Knowledge entries carry evidence levels and versioned changes.
Testing history
Behavioral checks before prompt and model changes reach production.
Quality metrics
An internal quality gate runs before each reply; routing and quality scores are recorded without message content.
Safety evaluations
Risk detection, escalation and crisis-resource behavior evaluated per release.
Bias evaluations
Structured testing for demographic and cultural bias in responses is being built; we do not publish results yet.
Human review history
Approvals for safety, governance and knowledge changes are recorded.
NIST AI RMF alignment
Governance, safety and measurement design follows govern/map/measure/manage. A design choice, not an assessment.
Enterprise administration
What an administrator can configure for their organization today, and what is still on the roadmap.
Access permissions
Employee, manager and HR-admin roles stored separately from profiles and enforced server-side.
Organization policies
Campaigns, team goals, action plans and communications scoped to the organization.
Notification policies
Nudge types, frequency and quiet hours, with the individual keeping final control.
Audit settings
HR and executive access recorded in an append-only log that cannot be edited or deleted through the app.
AI features
Per-organization enablement of assistant capabilities.
Retention periods
Organization-level retention defaults, with the individual's own window taking precedence.
Consent flows
Customizable onboarding consent text per organization and policy version.
Privacy policies
Customer-specific privacy notice surfaced inside the app.
Regional compliance settings
Region-specific defaults for resources, terminology and request handling.
Audit
Administrative and privacy events are recorded so an organization can reconstruct what happened. Audit records are protected from modification through the app.
Administrative access
HR and executive dashboard access is logged with the area, action and timestamp.
Consent changes
Every grant and withdrawal is stored with its policy version.
Data export requests
Export events are recorded as privacy events.
Data deletion requests
Scope and time of each erasure are recorded.
Tamper resistance
Audit tables deny update and delete through the application's access rules.
Permission changes
Role grants and revocations recorded in the audit trail.
Configuration changes
Organization policy and setting changes recorded with the actor.
Security events
Authentication anomalies and suspicious access surfaced to administrators.
Log export
Customer-initiated export of their own audit trail.
Global expansion
Country-specific requirements are configuration, not architecture. Adding a jurisdiction should not require rebuilding the platform.
Locale and language
PT-BR and EN-US written natively, with the assistant thinking and answering in the selected language.
Regional crisis resources
Emergency resources adapt to the person's region — 988 and 911 in the US, CVV 188 and 192 in Brazil.
Terminology
HR, manager and benefits vocabulary adapts to the market.
Data residency options
Today, processing occurs in the United States. Regional residency is a roadmap item, not a current capability.
GDPR and LGPD readiness
The access, correction, deletion, portability, restriction and consent mechanics generalize to these regimes; contractual instruments are handled per customer.
EU AI Act watch
We track transparency and risk-classification obligations relevant to wellbeing assistants.
Continuous compliance
Review cadence across every governance area, plus the triggers that pull a review forward.
Policy reviews
Policies re-examined at least annually and after any material product change.
Security reviews
Dependencies and application code reviewed as part of the release process.
Privacy reviews
New data collection requires a purpose, a retention answer and a deletion path before it ships.
AI governance reviews
Prompt, model and knowledge changes reviewed and approved by a person.
Clinical governance reviews
Evidence checks and clinical review of wellbeing content, described on the Clinical Governance page.
Internal audits
Periodic self-assessment against the controls published here.
External audits
Third-party assessment is a roadmap item; no audit has been completed.
Compliance reporting
Customer-facing reporting on controls, incidents and changes.
User rights
Every right below is exercisable by the person, in the app, without contacting support.
Understand AI usage
How the assistant works, what it can and cannot do, and how suggestions are produced.
Trust Center and in-conversation transparency
Manage privacy preferences
Six independent consent scopes, all off by default and withdrawable individually.
Privacy Center
Review stored memories
See every durable fact the assistant has kept, with its category and source.
Memory page
Delete stored memories
Delete one memory or all of them; withdrawing memory consent erases them immediately.
Memory page and Privacy Center
Download personal information
Structured export of profile, consents, memories, conversations and history.
Privacy Center
Control personalization
Choose the personalization level, response length, tone and language.
Profile and Privacy Center
Withdraw consent
Any scope, at any time, with the dependent data removed rather than merely hidden.
Privacy Center
Set retention
Choose how long data is kept; anything past the window is removed.
Privacy Center
Documentation library
Available to enterprise reviewers, under NDA where indicated. Planned items have not been written yet.
Privacy Policy
What is collected, why, for how long and with whom it is shared.
Terms of Service
Service scope, acceptable use and the explicit non-medical limitation.
Responsible AI Policy
Inviolable rules, safety behavior, oversight and evaluation.
Security Policy
Access control, encryption, logging and release practices.
Data processing practices
Processing purposes, categories, locations and subprocessors.
Incident response plan
Detection, triage, containment, notification and post-incident review.
Business continuity plan
Critical dependencies and continuity of service commitments.
Disaster recovery plan
Backup, restore procedures and tested RTO/RPO targets.
Administrator guide
Roles, configuration, audit and privacy request handling.
Employee guide
What is private, what is aggregated and how to opt out.
Release notes
Product, prompt and policy changes with dates.
Legal and compliance contact
Legal, procurement and security review teams talk directly to the right people.
Privacy and compliance
privacy@acolher.livePrivacy requests, DPAs, subprocessors and compliance questionnaires.
Running a legal or procurement review? Send your questionnaire and we will answer it with the same honesty you see on this page.