Privacy Policy

Last updated: September 16, 2026

This Privacy Policy covers the following products and services provided by Adrisco LLC ("Adrisco", "we", "us"):

• DCC One / Artemis, the nurse-call and resident-safety platform, including the on-premise Artemis site servers, the DCC One web dashboard and cloud service, and the support, messaging and notification features offered through them.
• Artemis Care (also referred to as DCC One) is a nurse-call pager app used by care staff in assisted-living and long-term-care communities to receive and respond to resident alarms.
• Artemis Setup is a companion app used by installers and technicians to configure Artemis hardware at a community.

These products are workplace tools. They are provisioned by a care community for its own staff and administrators. There are no consumer sign-ups and no advertising.

We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes.

How the system works

Understanding the architecture explains most of this policy.

Each community runs its own on-premise Artemis server. A device is provisioned by scanning a QR code generated from the community's admin console; from then on, the app communicates with the on-site server over the community's own local network using QUIC with encrypted transport. Many communities operate air-gapped networks with no internet connectivity at all, and in that configuration data never leaves the building.

Alarm information flows from the on-site server to staff devices on the community's network. Adrisco does not route resident data through consumer cloud services, and the mobile apps do not communicate with Adrisco, Apple, or any third party to deliver alarm content.

Communities that connect their site to the DCC One cloud service can manage configuration, review alarm history and reports, and receive support through the DCC One web dashboard. In that configuration the on-site server synchronizes configuration, alarm and diagnostic data with the DCC One cloud over an encrypted connection.

Information processed

Resident health information

To deliver alarms, the app processes:

• Resident names
• Room and location information
• Alarm types (for example, a pull-cord or pendant activation) and their timestamps

This information originates from the community's own on-site server and is displayed to authorized staff so they can respond to residents. We treat it as protected health information (see the HIPAA section below).

Staff and user information

• Staff sign in to Artemis Care with a PIN validated against the community's own configuration. There are no consumer accounts and no sign-up.
• Session information (who is signed in on which device) is held by the community's server and on the device.

DCC One account information

• Users of the DCC One web dashboard have accounts created by their organization or by Adrisco. We collect name, email address, organization, role and site access, and sign-in and session records.
• We keep an audit history of configuration changes and administrative actions, including which account made them.

Support requests and contact information

When you contact support through DCC One, we collect the information you provide: your name, email address, phone number (for callback requests), a description of the problem, and any chat messages you send. We use this information only to respond to your request, contact you about it, and keep a record of the support interaction.

SMS and messaging information

If you provide a mobile phone number and opt in to receive text messages from us, we collect your phone number, the date and method of your opt-in, and records of the messages sent to you and their delivery status. We also record replies you send, such as STOP or HELP.

Device and diagnostic information

• The app stores alarms, session state, and diagnostic logs locally on the device.
• A debug-log export exists for troubleshooting. It runs only when a user explicitly triggers it, and the user must share the resulting file themselves (for example, via AirDrop). It is never transmitted automatically anywhere.
• The apps contain no analytics SDKs, no advertising SDKs, no tracking, and no advertising identifiers.

How we use information

We use the information described above to:

• Deliver resident alarms and notifications to authorized care staff.
• Operate, configure, secure and maintain the DCC One / Artemis products.
• Authenticate users and control access to sites and data.
• Respond to support requests, including callbacks and chat.
• Send the service and support text messages you have opted in to receive.
• Diagnose problems and improve the reliability of the products.
• Meet legal, regulatory and contractual obligations.

We do not use personal information for advertising, and we do not use resident information for any purpose other than providing the service to the community.

SMS messaging

If you opt in to receive text messages from DCC One / Artemis, we use your mobile phone number to send service messages, such as support callback notifications and operational alerts. Message frequency varies. Message and data rates may apply. Reply STOP to opt out at any time, or HELP for help. You may also contact us at [email protected] to opt out.

Consent to receive text messages is not a condition of purchasing any product or service. Your phone number and SMS opt-in data are used only to send the messages you have agreed to receive. We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes. Mobile opt-in data and consent are never shared with third parties or affiliates except with the service providers that deliver messages on our behalf (such as our SMS carrier and messaging platform), and only for that purpose.

Service providers

For DCC One cloud features, we rely on a small number of service providers that process information on our behalf and only to provide the service: cloud hosting, email delivery, SMS and WhatsApp message delivery, browser push notification delivery, support chat, and the AI assistant built into the DCC One dashboard. These providers are bound by contractual obligations appropriate to the data they handle and may not use it for their own marketing purposes.

Where data is stored and processed

• On the community's server. The primary copy of alarm and configuration data lives on the on-premise Artemis server operated at the community.
• In the DCC One cloud. For connected sites, synchronized configuration, alarm history, reports, accounts and support records are stored in the DCC One cloud service.
• On the device. The app keeps a local store of alarms, session data, and logs on the community-owned device.
• Data residency. Where data is hosted on servers, those servers are located in the country of origin, the United States or Canada, and data stays in-region.

HIPAA and the business-associate relationship

Resident data handled by these products is treated as protected health information (PHI) under the U.S. Health Insurance Portability and Accountability Act (HIPAA), and under applicable Canadian provincial health privacy law for Canadian communities.

The care community is the covered entity (in Canadian terms, the custodian or data controller) and remains the owner of its residents' data. Adrisco acts as a business associate to the community and processes resident data only to provide the nurse-call service to that community.

What we do not do

• We never sell, rent, or distribute your data to anyone.
• We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes.
• The mobile apps do not send resident or staff data to Apple or to any third party.
• We use no analytics SDKs, no advertising, and no tracking of any kind.
• We do not put protected health information in push notifications (see below).
• Data does not leave its region of origin (United States or Canada).

Push notifications

When a staff device has no live connection to the community's local network, the on-site server can send an Apple Push Notification as a fallback so the device can alert staff.

That push payload deliberately carries no protected health information: no resident name, no room, no alarm details. It contains only an opaque alarm identifier. When the device receives the notification, it looks up the alarm details from its own local store. As a result, resident information is never exposed to Apple's push infrastructure or to any party outside the community's system.

Data retention and deletion

The community controls its own data. Retention periods for alarm history and related records are determined by each community according to its own policies and legal obligations; Adrisco does not impose or override them.

Data stored locally on a device is removed when the device is de-provisioned or the app is deleted. Requests concerning a specific resident's records should be directed to the care community, which is the covered entity and controller of that data.

Requesting data deletion

To request deletion of your personal data, email [email protected] or go to one.poltys.com/en/support and submit a request for data deletion. We will complete the deletion within 30 days of receiving your request.

Security

• All communication between the app and the community's server, and between the community's server and the DCC One cloud, is encrypted in transit (QUIC/TLS).
• DCC One accounts are protected by authentication and role-based access controls, and administrative changes are audited.
• Device credentials are held in the device's secure hardware keychain.
• Access to the app is gated by a staff PIN validated against the community's configuration.
• The apps run on community-owned, community-managed devices, not personal phones.
• In air-gapped deployments, the system operates with no internet connectivity at all.

Demo mode

Artemis Care includes a demonstration mode used solely for App Store review. Demo mode contacts no server and uses only simulated, fictitious data. No real resident or community information is involved.

Children's privacy

DCC One / Artemis, Artemis Care and Artemis Setup are workplace tools for care-community staff, administrators and installers. They are not directed at children, and we do not knowingly collect personal information from children.

Changes to this policy

We may update this policy from time to time. The "Last updated" date at the top reflects the most recent revision. Material changes will be reflected on this page before they take effect.

Contact

For questions about this policy or our privacy practices, contact Adrisco LLC at [email protected].

Use of our products is also governed by our Terms & Conditions.

For questions about a specific resident's data, contact the care community where the system is deployed. The community is the covered entity responsible for that data.