Legal

Privacy Policy

How PerioMaxer handles your data — spoiler: it stays on your device.

PerioMaxer — Privacy Policy

Effective Date: April 14, 2026
Last Updated: July 19, 2026

This Privacy Policy describes how SmileMaxer LLC, a Maryland limited liability company and the developer of PerioMaxer ("Developer," "we," "us," or "our"), handles information in connection with the PerioMaxer application ("App"), available on iOS and macOS via the Apple App Store and on Android via Google Play.

By using the App, you agree to the practices described in this Privacy Policy.

1. Our Core Commitment

PerioMaxer is built so that your clinical data — patient records, periodontal charting, and voice — never leaves your device, and the Developer has no access to it. All such data remains exclusively on your device, under your control.

There is one narrow exception, and it never touches patient data: while you are first setting up the App (during onboarding, through the end of setup), the App uses Meta's mobile measurement tools to understand how new users discover PerioMaxer, so we can measure our advertising. This is limited, contains no patient data or protected health information, and is fully inactive once you finish onboarding and begin charting. It is described in Section 8.

2. Information We Do NOT Collect

We want to be clear about what we do not do. The Developer does not collect, receive, access, store, process, or transmit:

  • Patient names, dates of birth, or any patient demographic information.
  • Periodontal charting data, clinical measurements, or examination records.
  • Protected health information (PHI) of any kind.
  • Voice recordings or audio data.
  • Speech recognition transcriptions.
  • Biometric data (Face ID, fingerprints).
  • Location data.
  • Analytics about how you use the App while charting, or any behavioral profiling of your clinical work.
  • Crash reports (automatic).
  • The advertising identifier (IDFA). We never request it, and the App shows no App Tracking Transparency prompt. We do not track you across other companies' apps or websites, and we use no cookies or tracking pixels.

We have zero access to any of the patient or clinical data you enter into the App.

The one exception to the list above is a small amount of app-level setup measurement used to evaluate our advertising. While you are onboarding, Meta's measurement tools receive a few non-clinical events (for example, that the App was opened, which setup screens were viewed and for how long, that the subscription screen was reached, which plan was selected, whether a checkout was completed or abandoned, that a free trial was started, and that setup was finished), the non-clinical setup preferences you choose during the setup interview (your tooth-numbering system, the label you use for the gingival-margin row, your gingival-margin sign convention, which practice-management or charting software your office uses if you choose to answer, your professional role, and your chosen chart style), together with the standard device and network information any app exchange carries (such as a per-vendor device identifier and IP address). This contains no patient data or PHI, uses no cross-app advertising identifier, and stops entirely once onboarding is complete. See Section 8 for the full description.

3. Data Stored on Your Device

The App stores the following data locally on your device only:

3.1 Patient and Clinical Data

  • Patient names and dates of birth.
  • Periodontal examination records, including probing depths, gingival margins, bleeding on probing, suppuration, plaque, furcation involvement, tooth mobility, and related clinical measurements.
  • Exam dates, examiner names, and chart notes.

On iOS and iPadOS, this data is stored using Apple's SwiftData framework and protected at rest by iOS Data Protection — Apple's built-in, hardware-backed file encryption, whose keys are tied to your device passcode and the device's Secure Enclave. On macOS, the same SwiftData store is protected by macOS full-disk encryption (FileVault) when you have it enabled. On Android, this data is stored in the App's private, sandboxed storage on your device, protected by Android's device-level (file-based) encryption; your PIN and other credentials are additionally encrypted at the app level using AES-256-GCM, with keys held in the hardware-backed Android Keystore.

3.2 Authentication Data

  • A locally stored app-unlock PIN — held only in the device's secure key store (the Apple Keychain on iOS and macOS, the hardware-backed Android Keystore on Android) and never kept in plain text.
  • Biometric authentication configuration — managed on iOS and macOS by Apple's LocalAuthentication framework, and on Android by the system BiometricPrompt API. The Developer never accesses biometric data on any platform.

3.3 Audit Log

  • A tamper-evident log of user actions (logins, chart creation, edits, deletions) with timestamps and cryptographic hash chains for integrity verification.

3.4 App Preferences

  • User settings and preferences (e.g., charting mode, voice control settings, display preferences).
  • Subscription status (verified locally via Apple's StoreKit framework on iOS and macOS, or Google Play Billing on Android).

None of the above data ever leaves your device through the App.

4. Voice and Speech Data

The App offers voice-controlled charting using on-device speech recognition: Apple's native framework (SFSpeechRecognizer) on iOS and macOS, and an on-device Vosk speech model on Android.

  • On-device processing only. Speech recognition runs entirely on your device — on iOS and macOS the App requires on-device recognition (requiresOnDeviceRecognition = true); on Android the Vosk model runs locally on the device. Audio is never sent to Apple, Google, the Developer, or any third party.
  • No recording. The App does not record, store, or retain any audio. Voice data is processed in real time and discarded immediately after transcription.
  • No transmission. No audio or transcription data is transmitted to the Developer or any external service.

5. Biometric Data

The App supports biometric authentication — Face ID or Touch ID on iOS and macOS (through Apple's LocalAuthentication framework), and fingerprint or face unlock on Android (through the system BiometricPrompt API).

  • Biometric data is processed and stored entirely on your device by the platform's secure hardware — Apple's Secure Enclave on iOS and macOS, and the hardware-backed Android Keystore (Trusted Execution Environment or StrongBox) on Android.
  • The Developer never receives, accesses, processes, or stores any biometric data.
  • You can enable or disable biometric authentication at any time within the App or through your device settings.

6. Subscription and Payment Data

Subscriptions are managed entirely by the platform's app store — Apple through the App Store on iOS and macOS, and Google through Google Play on Android.

  • The Developer does not collect, process, or store any payment information, including credit card numbers, billing addresses, or your Apple ID or Google account credentials.
  • The App verifies subscription status locally using Apple's StoreKit 2 framework (iOS and macOS) or Google Play Billing (Android).
  • Purchase history and billing are managed by Apple or Google and subject to Apple's Privacy Policy or Google's Privacy Policy, respectively.

7. Bug Reports

The App includes an optional bug report feature that allows you to send feedback via email.

  • Bug reports are entirely voluntary and user-initiated. The App never sends information automatically.
  • When you submit a bug report, it opens your device's native email client. You control the content of the email before sending.
  • Bug reports are sent to: support@periomaxer.com
  • We recommend that you never include patient data or PHI in bug reports.

8. Third-Party Services

The App keeps your clinical data on your device and integrates with only two categories of third party: the platform app store, and — during onboarding only — Meta's app-measurement tools.

8.1 App Store / Google Play

Subscriptions are handled by the platform app store — Apple's App Store (iOS and macOS) or Google Play (Android) — each governed by its own privacy policy.

8.2 Meta (Facebook) acquisition measurement — onboarding only

To measure the effectiveness of our advertising, the App includes Meta's measurement SDK. Its use is deliberately and tightly limited:

  • Onboarding only. It is active only from first launch through the end of onboarding setup. Once you finish onboarding and begin charting, it is inactive and sends nothing.
  • No patient data, ever. It never receives patient names, charting values, voice, or any protected health information. It sends only a few non-clinical setup events — for example, that the App was opened, which setup screens were viewed and for how long, that the subscription screen was reached, which plan was selected, whether a checkout was completed or abandoned, that a free trial was started, and that setup was finished — along with a value associated with the chosen plan and, once per install, the non-clinical preferences you choose during the setup interview: your tooth-numbering system, the label you use for the gingival-margin row, your gingival-margin sign convention, which practice-management or charting software your office uses (an explicit "prefer not to say" option is always offered), your professional role, and your chosen chart style. These preferences describe how you chart, never whom you chart; we use them in aggregate to understand our users and improve the App.
  • No cross-app tracking, no IDFA, no prompt. We do not request the advertising identifier and show no App Tracking Transparency prompt. On Apple devices, install measurement uses Apple's privacy-preserving SKAdNetwork, which reports only aggregated results and no information that identifies you.
  • Automatic logging is turned off. The SDK does not silently log your activity; only the specific setup events above are sent, and only during onboarding. Standard device and network information that any network exchange carries (such as a per-vendor device identifier and IP address) accompanies those events.

Information Meta receives in connection with these events is handled under Meta's Privacy Policy.

8.3 What the App does NOT use

Beyond the two integrations above, the App uses:

  • No general-purpose analytics platforms (Google Analytics, Firebase Analytics, Mixpanel, etc.) for your in-app activity.
  • No crash reporting services (Crashlytics, Sentry, Bugsnag, etc.).
  • No social media login or sharing integrations.
  • No cloud storage or sync services (iCloud, Google Drive, Dropbox, etc.) — your records are not uploaded anywhere.
  • No external API or web service that receives your patient or clinical data.

9. Data Security

While the Developer does not have access to your data, the App implements the following on-device security measures:

  • Encryption at rest. On iOS and iPadOS, all patient data is protected by iOS Data Protection — Apple's hardware-backed file encryption, keyed to your device passcode and Secure Enclave. On macOS, it is protected by FileVault full-disk encryption when enabled. On Android, patient data is held in the App's private, sandboxed storage protected by the device's file-based encryption, and credentials such as your PIN are encrypted using AES-256-GCM via the hardware-backed Android Keystore.
  • Secure key storage. On iOS and macOS, file-encryption keys are managed by the operating system and protected by the device's Secure Enclave, while the App's own credentials (such as your unlock PIN) are stored in the Apple Keychain. On Android, encryption keys are held in the hardware-backed Android Keystore.
  • Authentication. Access to the App requires PIN or biometric authentication (Face ID/Touch ID on Apple devices, or fingerprint/face unlock on Android).
  • Auto-lock. The App automatically locks after a configurable period of inactivity (default: 10 minutes).
  • Audit trail. All actions are logged in a tamper-evident log with cryptographic hash chains.

Your responsibility: You are responsible for maintaining the physical security of your device, keeping your operating system up to date, and configuring appropriate device-level security settings (passcode, encryption, remote wipe, etc.).

10. Data Retention and Deletion

10.1 Data Retention

All data is stored on your device for as long as the App is installed and you choose to retain it. The Developer has no ability to access, retain, or delete your data.

10.2 Data Deletion

  • You can delete individual patient records and charts within the App at any time.
  • Uninstalling the App will remove all App data from your device.
  • The Developer cannot recover data after deletion.

10.3 Subscription Expiration

If your subscription expires, data previously entered remains on your device. Access to certain App features may be restricted, but your data is not deleted.

11. Children's Privacy

The App is not intended for use by individuals under the age of 18. We do not knowingly collect information from children. The App is designed exclusively for licensed dental professionals and their authorized staff.

12. Your Compliance Obligations

12.1 Your Responsibility

You are solely responsible for ensuring that your use of the App complies with any laws, regulations, or professional standards that apply to records you store within the App.

12.2 No Data Custodian Relationship

Because the Developer does not create, receive, maintain, or transmit any data on your behalf, no data custodian, processor, or business associate relationship exists between you and the Developer. No data processing agreement is required or provided.

12.3 On-Device Architecture

The App's architecture — with all data stored and processed locally on your device, no cloud connectivity, and no data transmission — is designed to support your data security and privacy efforts. Your overall compliance posture depends on your broader practices, not solely on the App.

13. International Users

If you are located outside the United States:

  • All data remains on your device and is not transferred internationally by the App.
  • You are responsible for compliance with applicable data protection laws in your jurisdiction, including the GDPR, PIPEDA, or other applicable regulations.
  • The App does not transfer any data to the Developer or across international borders.

14. Your Rights

Because the Developer does not collect or store any personal data:

  • Access requests. There is no data held by the Developer to access.
  • Deletion requests. There is no data held by the Developer to delete. You can delete all data locally on your device.
  • Data portability. All data is stored on your device. The Developer does not hold any copies.
  • Opt-out. There is no data collection to opt out of.

If you have questions about data stored on your device, you can review it within the App.

15. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. When we do, we will update the "Last Updated" date above and post the revised policy at this URL.

If we make a material change to how personal information is handled, we will provide notice through the App or by another reasonable means before the change takes effect. Non-material changes, such as clarifications or formatting, take effect when posted. We encourage you to review this Privacy Policy periodically.

SmileMaxer LLC may offer applications other than PerioMaxer under separate privacy policies. A change that applies only to a different application does not affect this Privacy Policy or your rights with respect to PerioMaxer.

16. Contact

If you have questions about this Privacy Policy, you may contact us at:

SmileMaxer LLC
Baltimore, Maryland, USA
Email: support@periomaxer.com

This Privacy Policy was last updated on July 19, 2026.