Artful Intelligence, LLC · North Carolina, United States
Privacy Policy
Protocol is local-first. Core records stay on your device unless you export them or send information with feedback. Optional Protocol accounts use Sign in with Apple or an email sign-in link; related authentication and account-management data are handled as described below.
Scope and controller
This Privacy Policy explains how Artful Intelligence, LLC ("Artful Intelligence," "we," "us," or "our") handles information in connection with the Protocol iOS app, theprotocolapp.co, support, and optional Protocol accounts.
Protocol is designed to be local-first. Core records remain in the app's local container unless you choose to export them or send information with feedback. Catalog retrieval, voluntary catalog-related submissions, support, and optional account authentication and management can transmit the limited data described below.
Information and on-device processing
Protocol processes protocol, compound, schedule, concentration, dose, administration, injection-location, notification, inventory, vial, preparation, reconstitution, storage, free-text records, preferences, appearance settings, warning thresholds, and local workflow state on your device. It also processes files you create through JSON or CSV export and information you choose to include in feedback or a support request.
Core app records are stored locally using Apple's app-storage technologies with iOS data protection. Protocol does not enable CloudKit synchronization for these records. The app's local data directory is excluded from ordinary iOS device backup by the app. A local-data wipe removes the app's local records and settings; it does not delete an optional account or server-side data. Deleting the app normally removes its local app container, subject to iOS behavior. Exports are unencrypted after creation and are controlled by you and the destination you select.
Network and service data
The following features communicate with services we operate or providers working for us.
- Compound catalog: Protocol may retrieve a current compound-title catalog. Versions with the optional product analytics controls keep catalog-title selections on your device. Older versions may still send automatic selection requests; our service discards their contents without recording the selected title. Previously recorded selections may still contribute to aggregate catalog-popularity suggestions. If you voluntarily submit a catalog-related suggestion, report, feedback, or support request, we receive the information you choose to submit and the limited metadata described for feedback and support below. Catalog retrieval can provide network and request information used for security and rate limiting.
- Feedback and support: if you submit feedback or a support request, the service receives the information you enter and may receive your email, app/build version, iOS version, device model, optional screenshot, and an optional diagnostic log. The diagnostic log is designed to exclude Protocol records and Keychain contents, but you should still review every attachment before sending it. The app uses a persistent client token stored in the iOS Keychain; the support page uses a separate client token stored in that browser's local storage. Each is transmitted with its request, and the service stores its hashed form to associate submissions, prevent abuse, and apply rate limits. If you choose a public request and an administrator approves it, the title, public description, type, status, and aggregate votes may be displayed to other users. Your email, private troubleshooting fields, diagnostic log, and attachments are not intended for public display. Public ideas are reviewed before display. When you report a public idea, we receive the reported idea, the reason you select, and a pseudonymous installation hash. Administrators can remove public content and block an installation hash from submitting additional content; this does not create a broad ban on a person.
- Website access requests: if you submit the website access-request form, we receive your email address, acknowledgement, invite code or source path, browser user agent, and request timestamps. We use network information for security and rate limiting. The site stores your selected appearance preference in your browser's local storage.
- Optional account authentication and management: when you create, sign in to, manage, or delete an authenticated Protocol account, our service receives the account identifier and the information necessary to provide that request. Sign in with Apple is processed through Apple's authentication service; email sign-in links are delivered through the configured transactional-email provider.
- Optional product analytics: if you choose to enable product analytics in Protocol, the app sends limited event information through a gateway to PostHog, which processes it for us. The app creates a separate random analytics token, and the gateway uses a salted hash of that token as the pseudonymous analytics identifier. It is not your account ID, support token, catalog token, email address, or a cross-device identifier, and we do not use it to join analytics to your account. The gateway receives network information, including IP address, for security and rate limiting; it excludes that information from the PostHog event payload. Events may include the event type, app/build and operating-system version, device family, release profile, distribution channel, coarse screen or workflow stage, bounded outcome or error category, and event timing. They do not include Protocol records, compound or medication names, doses, schedules, analyte results, report files or images, free text, search or clipboard contents, notification content, prompts, responses, account identifiers, raw error text, or URLs with parameters. Analytics is off unless you enable it; declining does not limit app functionality.
Use, providers, and disclosures
We use information only as reasonably necessary to provide, secure, maintain, troubleshoot, and improve Protocol; respond to website access and support requests; administer optional account authentication, management, and deletion requests; enforce our terms; prevent abuse; comply with law; and protect users, Artful Intelligence, and others. We do not use health or routine records for targeted advertising. We do not sell personal information, and Protocol does not include third-party advertising or cross-app tracking SDKs.
We may disclose the minimum information reasonably necessary to service providers that host infrastructure, provide authentication, deliver transactional email, process optional product analytics, support or security events, or otherwise act for us under appropriate restrictions. Current categories include Supabase-hosted infrastructure, PostHog for optional product analytics when enabled, Apple platform and authentication services, and Resend for email delivery where configured. We may also disclose information as reasonably necessary for law, valid process, fraud, abuse, security, rights and safety, corporate transactions with safeguards, or with your direction or consent. Apple and other platforms, and your export destination, email provider, Files provider, or recipients, independently process information under their own terms.
Retention and requests
Local records remain until you delete them, wipe local data, or uninstall Protocol, subject to iOS behavior. User-created exports remain wherever you place them until you delete them there. Deleting an optional Protocol account is designed to delete its authentication user record and previously stored account files and metadata. The deletion cannot be undone once processed. It does not erase Protocol records stored locally on the device or exports stored elsewhere. For an account created with Sign in with Apple, Protocol requests revocation of a retained Apple authorization token when available. If no retained token is available for that account, Protocol presents the applicable manual Apple-account step after deletion. Keep any export you need before requesting deletion.
Website access-request, support, catalog, security, diagnostic, and usage records are retained only for as long as reasonably necessary for the purposes described above, legal compliance, dispute resolution, and abuse prevention. System caches and logs may take additional time to expire. Optional product analytics events are retained for up to one year under the currently selected provider plan; provider deletion and cleanup can take additional time. When you turn optional analytics off, Protocol stops new capture and clears its local queue. The gateway requests deletion of the current analytics identity and clears its provider capture metadata after that deletion is confirmed. It retains only a minimal salted hash of the former analytics token and a deletion receipt to reject late or replayed requests using that old token. That receipt contains no event records, account mapping, health information, or other Protocol content. If the analytics consent version changes, Protocol stops capture until you make a new choice; analytics already collected with prior consent remains subject to this retention policy unless you use the deletion control. We have not independently verified a configured automatic deletion period for pseudonymous install-hash feedback, votes, catalog-selection, or related security records. Account deletion does not automatically remove feedback, votes, catalog-selection, or related records keyed to a pseudonymous installation hash. Because optional analytics is not joined to an account in this version, an account-deletion request cannot locate analytics from another anonymous installation.
You can review or edit local records; delete individual records; wipe local data; and create, manage, or delete an optional Protocol account through available controls. You can control permissions through iOS where available. Privacy laws may give you rights to access, correct, delete, or obtain a copy of personal information we hold, or appeal a request decision. Submit a request through the private Support & Privacy Request form at theprotocolapp.co/support or email support@theprotocolapp.co. We may need to verify your identity and may retain information where permitted or required by law.
Security, changes, and contact
We use technical and organizational safeguards intended to protect information, including on-device data protection, encrypted transport, and access controls. No storage, network, device, or service is completely secure or continuously available. You are responsible for device security and safe export handling. If we determine that a security incident triggers a legal notification duty, we will provide notice as required by applicable law.
Protocol is not designed to solicit personal information from children, and we do not knowingly collect personal information from a child through the service. Artful Intelligence operates from the United States; transmitted information may be processed there or other locations used by providers. We may update this policy as Protocol or law changes and will provide additional notice or request renewed consent when legally appropriate. Use Settings > Help & Feedback, the private Support & Privacy Request form, or support@theprotocolapp.co for support, privacy, and account-deletion requests. Do not send medical emergencies, full medical records, or passwords through support.