Privacy Policy

Your privacy matters. This policy explains how Nocturne handles your data and protects your privacy.

1. Introduction

Nocturne is a self-hosted, open-source diabetes data management platform. This means you control where your data lives. Unlike cloud-based services, Nocturne runs on your own server or hosting provider, and your data stays in your own database.

This privacy policy explains what data Nocturne collects (spoiler: very little), how it's stored, and your rights.

2. Data We DON'T Collect

Because Nocturne is self-hosted, we (the Nocturne project developers) do not have access to your data. Specifically:

No analytics: Nocturne does not send usage analytics or telemetry to us by default.
No tracking: We don't track your usage, browsing, or behavior.
No data collection: Your glucose readings, treatments, meals, and health data never leave your server unless you choose to share them.
No selling data: We don't sell your data because we don't have access to it in the first place.
No cloud storage: Nocturne doesn't store your data in our cloud or servers. It's all on your infrastructure.

3. Data Storage

All your Nocturne data is stored in your own database on your own server or hosting provider. This includes:

Glucose readings (blood sugar, CGM data)
Treatments (insulin, medications)
Meals and nutrition data
Activity and exercise logs
User account information
Settings and preferences

Where your data lives:

Your database: All persistent data is stored in a PostgreSQL database that you control.
Your hosting provider: Your hosting provider's privacy policy and security practices apply to your data. Choose a provider you trust.
Browser local storage: Some temporary data (like UI preferences) may be stored in your browser's local storage. This never leaves your device.

4. Third-Party Services and Connectors

Nocturne can connect to third-party diabetes data services to import your glucose and treatment data. When you use these integrations:

Third-party privacy policies apply: Services like Dexcom, FreeStyle Libre, Glooko, and Tidepool have their own privacy policies. Review them before connecting.
We don't control third parties: We cannot control what data these services collect about you or how they use it.
Credentials storage: Your API keys and login credentials for third-party services are stored encrypted in your database. Only your Nocturne instance can decrypt them.
Data transfer: When you connect to a third-party service, data flows between that service and your Nocturne instance. We (the Nocturne developers) do not see or have access to this data.

Third-party services you might connect:

Dexcom (CGM data)
FreeStyle Libre (CGM data)
Glooko (multi-source data aggregation)
Tidepool (open diabetes data platform)
Nightscout (diabetes data platform)
Others via community plugins

5. Optional Analytics and Error Reporting

In the future, Nocturne may offer optional, opt-in features for:

Error reporting: Send crash reports and error logs to help us improve Nocturne
Anonymous usage analytics: Aggregated, anonymized usage statistics

If we add these features:

They will be opt-in only - disabled by default
You'll have clear control to enable or disable them
We'll clearly explain what data would be collected
Data will be anonymized and aggregated when possible
No health data or personally identifiable information will be included

Current status: As of this writing, Nocturne does not include any analytics or error reporting features.

6. Your Rights and Data Control

Because you self-host Nocturne, you have complete control over your data:

You own your data: All data belongs to you. We make no claims to it.
Export anytime: You can export your data at any time. It's just a PostgreSQL database - you have full access.
Delete anytime: You can delete any or all of your data whenever you want.
Control access: You decide who can access your Nocturne instance and what they can see.
Move your data: You can migrate your database to a different server or hosting provider at any time.
Backup your data: You're responsible for backing up your database. We recommend regular backups.

7. Security

Nocturne is designed with security best practices:

Encryption: API keys and sensitive credentials are stored encrypted in the database.
HTTPS recommended: We strongly recommend running Nocturne behind HTTPS to encrypt data in transit.
Authentication: User accounts are protected with password hashing (bcrypt).
Open source: The code is open for security review by the community.

Your responsibility: As a self-hosted application, you're responsible for:

Keeping your server and dependencies updated
Using strong passwords
Securing your hosting environment
Configuring HTTPS/SSL certificates
Regular backups

8. Children's Privacy

Nocturne is often used to manage diabetes data for children. Because the software is self-hosted:

Parents/guardians control all data for their children
No data is sent to us (the developers)
All data stays within the family's or caregiver's control

If you're hosting Nocturne for your child, you have full control and responsibility for their data privacy and security.

9. Changes to This Privacy Policy

We may update this privacy policy from time to time. When we do:

The updated policy will be posted at this URL
The "Last updated" date will change
Major changes will be announced in the GitHub repository

Because Nocturne is self-hosted, privacy policy changes don't affect data you've already collected - it stays under your control regardless.

10. Contact

For questions about this privacy policy or Nocturne's privacy practices:

GitHub: github.com/nightscout/nocturne
Open an issue or discussion on GitHub

For questions about your specific Nocturne instance's privacy and data handling, contact your instance administrator (which might be you if you're self-hosting).

Summary

The key point: Nocturne is self-hosted, which means you control your data. We (the developers) don't collect it, don't have access to it, and can't sell it or share it. Your privacy is protected by design.