-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
📝 Add SEAL 911 Data Retention Policy (#13)
- Loading branch information
1 parent
eee4cc9
commit ab59de0
Showing
3 changed files
with
47 additions
and
5 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
# SEAL 911 Data Retention Policy | ||
|
||
## Privacy Protection | ||
|
||
**Your privacy is our highest priority and is always protected.** We never share your data outside of SEAL 911 without your explicit consent. | ||
|
||
## Data Retention Period | ||
|
||
The default retention period for your data is **12 months**. You have the option to opt out of this default retention period at any time. To do so, please notify us through a new ticket in the [SEAL 911 Telegram bot](https://t.me/seal_911_bot). | ||
|
||
## Data Retention Cycle | ||
|
||
The personal data retention cycle consists of three distinct successive phases: | ||
|
||
1. Active ticket: Your data is actively used and managed inside of the SEAL 911 Telegram bot. | ||
2. Intermediate archiving: Upon closing of the ticket, your data is moved to a secure intermediate archive. | ||
3. Deletion: After 12 months, your data is fully deleted within the SEAL 911 Telegram bot and the intermediate archive. | ||
|
||
If special circumstances require us to retain the data beyond the 12-month period, we will contact you to seek your consent. If we do not receive a response, we will assume that you do not consent. | ||
|
||
## Data Sharing With SEAL-ISAC | ||
|
||
SEAL 911 members may share non-PII (Personal Identifiable Information) data and moderately sensitive data with SEAL-ISAC (Information Sharing and Analysis Center), which operates under a separate data retention policy. To enable potential future communication with victims, we collect and store Telegram usernames and jurisdiction information, classified as **TLP:RED** within SEAL-ISAC. When relevant, we will include essential details about the incident, such as compromised on-chain addresses, destinations of stolen funds, and pertinent Indicators of Compromise (IoCs) and Tactics, Techniques, and Procedures (TTPs). These efforts are designed to support future investigations or cases involving the same threat actors. You can opt out of this sharing at any time and request deletion of your data from SEAL-ISAC. To do so, please notify us through a new ticket in the [SEAL 911 Telegram bot](https://t.me/seal_911_bot). | ||
|
||
## Communication Channels | ||
|
||
Please note that the SEAL 911 Telegram bot operates on Telegram, which is not encrypted by default. We are happy to open other communication channels (e.g., Signal) to exchange sensitive information securely. | ||
|
||
## Your Concerns and Requests | ||
|
||
As security professionals, we value your privacy above all. If you have any questions or specific requests, please let us know via the [SEAL 911 Telegram bot](https://t.me/seal_911_bot), and we will do our best to address your concerns. **Privacy is not a meme at SEAL 911; it is one of our core principles!** | ||
|
||
--- | ||
|
||
By adhering to this policy, SEAL 911 ensures the protection and respectful handling of your personal data at all times. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters