No technology is perfect, and UpHabit believes that working with skilled security researchers across the globe is crucial in identifying weaknesses in any technology. If you believe you've found a security issue in our product or service, we encourage you to notify us. We welcome working with you to resolve the issue promptly.

Disclosure Policy

• Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.

• Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.

• Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder.

Exclusions

While researching, we'd like to ask you to refrain from:

• Denial of service

• Spamming

• Social engineering (including phishing) of UpHabit staff or contractors

• Any physical attempts against UpHabit property or datacenters

• User access to the users own data including access tokens (including, but not limited to: device backups, export functionality)

• Access to mobile device secrets such as API keys without extra proof of using the key to create an otherwise eligible vulnerability

The following classes are also considered ineligible

• SPF/DMARC/DKIM records issues without verifiable proof of spoofing to a major mail client (e.g. gmail).

• Email or user enumeration / account oracles

• CSP Weaknesses

• Open Redirects

• Descriptive error messages or headers (e.g. Stack Traces, application or server errors, banner grabbing) .

• Use of a known-vulnerable library without a description of an exploit specific to our implementation

• Password or account recovery policies, such as reset link expiration or password complexity.

• Publicly accessible login panels.

• Lack of email address verification during account registration .

• Rate-limiting issues.

• Issues related to active sessions after password changes or logout.

• "Scanner output" or scanner-generated reports

• Publicly-released bugs in internet software within 7 days of their disclosure

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Thank you for helping keep UpHabit and our users safe!