Privacy Policy

Last updated: 20 Dec 2025

By using SafePulse (“SafePulse”, “the Platform”, “we”, “us”, “our”), you agree to the practices described in this Privacy Policy. If you do not agree, you must not use the Platform.

1. Introduction

SafePulse is committed to protecting your privacy and ensuring that you maintain full control over your data.

The Platform is designed with:

Data minimalism
Local-first identity
Non-custodial architecture
User-controlled smart contract interactions

This Privacy Policy explains how SafePulse handles information, what is (and is not) collected, and your responsibilities as a user.

2. Zero Personal Data Collection

SafePulse collects no personal information whatsoever.

We do not collect, store, or process:

Names, email addresses, phone numbers
Government IDs, documents, or biometric data
Wallet private keys, seed phrases, or sensitive financial details
Location-linked identity or IP-linked profiles
Personal behavioral tracking
KYC information or verification data

SafePulse performs no KYC, no identity verification, and no account creation with personal data.

3. Local Device Control of Identity and Keys

All cryptographic materials—including identity keys, DID keys, private keys, credential keys, and signing keys—are generated and stored exclusively on your device.

SafePulse:

Does not access, store, back up, or transmit your keys
Does not retain credential-related information

You are solely responsible for securing your keys, recovery phrases, and devices. If keys are lost, SafePulse cannot recover them, reset them, or restore access.

4. No Cloud Backups & No Cloud Recovery

SafePulse does not provide:

Cloud backup or cloud key storage
SRP-based backups
Server-side identity storage
Remote account restoration

All recovery is performed locally by the user using their own passphrase or recovery materials.

5. No Traditional Authentication Services

SafePulse does not use or rely on:

OAuth, email/password, phone verification
Firebase Authentication or centralized login systems
Third-party identity providers

Authentication and identity generation occur entirely on-device and are self-sovereign.

6. Optional Diagnostic Analytics

SafePulse may collect non-personal diagnostic data solely to improve:

Stability
Performance
Security
Crash detection

This data:

Is anonymous and cannot identify users
Contains no personal or behavioral information
Can be disabled at any time in settings

Analytics may include device type, error logs, and crash traces—only for performance improvement.

7. No Tracking Technologies

SafePulse does not use:

Cookies, web beacons, or fingerprinting
Targeted advertising identifiers
Cross-site tracking or behavioral analytics

No data is sold, shared, or monetized.

8. Third-Party Integrations

Interactions with third-party services (e.g., blockchain RPCs, event loggers, error trackers) are:

Optional and user-initiated
Separate from SafePulse systems
Governed by the third-party’s privacy policies

SafePulse does not control or store data from third-party services.

9. Smart Contract Interactions

Smart contract interactions may appear on public blockchains.

Transactions are irreversible
Blockchain records are public by default
SafePulse cannot delete or alter blockchain data
Users must understand the immutable nature of blockchain systems

Smart Contract Upgrades:

SafePulse may release updates or improvements
Users may choose whether or not to adopt updates, at their own discretion
The Platform provides no guarantees regarding performance, compatibility, or outcomes of upgraded contracts

10. Intellectual Property & Platform Ownership

All components of SafePulse—smart contracts, dApps, ABIs, APIs, algorithms, documentation, and UI/UX—are the sole property of Hassan Qasemi, under copyright and the Contract Foundry Project, and are patent pending
Users must not reverse engineer, decompile, copy, modify, or create derivative works of any platform components
Users must not connect unauthorized third-party proxies or clients to SafePulse smart contracts