Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Privacy Policy

Last updated: 4 Jun 2026

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 a trustless proof and settlement protocol where agreements, conditions, and settlement outcomes are cryptographically verifiable, enabling secure coordination and execution without intermediaries.

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™, including smart contracts, dApps, ABIs, APIs, algorithms, documentation, and UI/UX, are proprietary and are the exclusive intellectual property of the Platform Owner. Certain components developed under the Contract Foundry Project may also be subject to patent-pending protection.

Nothing herein shall be construed as a transfer, license, or waiver of any intellectual property rights.

Supporting intellectual property and technical certification documentation may be provided to qualified business partners upon request, subject to confidentiality obligations.

  • 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

Access to and use of the Platform, including its decentralized application (dApp), smart contracts, interfaces, APIs, and any related services (collectively, the “Platform”), is strictly prohibited for individuals or entities located in, incorporated in, resident in, or accessing the Platform from any restricted jurisdiction.

Restricted jurisdictions include: Argentina, Australia, Bahrain, Canada, Costa Rica, Egypt, Estonia, France, Germany, India, Israel, Italy, Japan, South Korea, Kuwait, Lithuania, Pakistan, Poland, Qatar, Saudi Arabia, Ukraine, United Arab Emirates, United Kingdom, United States of America, and Uganda.

By accessing or using the Platform, you represent and warrant that you are not located in, resident in, or accessing the Platform from any restricted jurisdiction and that you are legally permitted to use the Platform under applicable law. We reserve the right to restrict, suspend, or terminate access to the Platform at any time if we reasonably believe you are in breach of this section.

SafePulse is built by Hassan Qasemi, a software engineer, protocol engineer, and systems architect.

SafePulse is independently developed and operated, registered as a sole proprietorship in the Islamic Republic of Iran (Registration No. 18892452), The software is copyright registered (No. 8-107218-103731) and it has passed software conformity assessment (No. 207518).

The core ecosystem protocols and components are patent-pending, with all intellectual property held by the creator.

11. Content Restrictions & User Responsibility

Users must ensure that their usage:

  • Complies with local laws and regulations
  • Does not involve illegal, abusive, harmful, or exploitative content
  • Respects platform restrictions against prohibited misuse

Users are responsible for their cryptographic materials and account security.

Users are solely responsible for ensuring that their use of the Platform complies with applicable laws, regulations, and restrictions in their respective jurisdictions.

12. Age Restriction

SafePulse is intended for users 22 years of age or older. No personal or non-personal data is knowingly collected from minors.

13. Data Sharing

SafePulse:

  • Does not share, sell, or monetize data
  • Does not profile users
  • Does not integrate ad networks
  • Analytics remain local and anonymous

All user activity remains private on your device.

14. Security Measures

SafePulse uses:

  • Local encryption and decenrtalized identifiers mechanisms
  • Decentralized architectures and secure cryptographic standards

However, no system is perfectly secure. Users must:

  • Protect and backup contract DID's
  • Do initialization after deployment soon as possible
  • Understand the risk of DID loss and losing access to smart contracts

SafePulse do not access to DID keys.

15. Updates to This Privacy Policy

SafePulse may update this Privacy Policy to reflect:

  • Changes in technology
  • Security improvements
  • New platform features
  • Updates in decentralized identity or smart contract standards

Continued use constitutes acceptance of the updated policy.

16. Contact Information

For privacy questions or administrative matters: support@safepulse.xyz