yoohoo! hot sauce please
10:27, 7 September 2026 (UTC)
Contact and legal: Difference between revisions
Deep-dive addendum: new pages + expansions |
Yushe wrote the engine; Taro is security lead |
||
| Line 11: | Line 11: | ||
The site asks security researchers to report vulnerabilities '''privately''' and not to post exploit details publicly: "We appreciate responsible disclosure and will review good-faith reports." | The site asks security researchers to report vulnerabilities '''privately''' and not to post exploit details publicly: "We appreciate responsible disclosure and will review good-faith reports." | ||
A machine-readable <code>security.txt</code> is published at <code>2swagg.net/security.txt</code> and <code>2swagg.net/.well-known/security.txt</code>. It names '''<code>[email protected]</code>''' as the security contact, that is [[Taro]], | A machine-readable <code>security.txt</code> is published at <code>2swagg.net/security.txt</code> and <code>2swagg.net/.well-known/security.txt</code>. It names '''<code>[email protected]</code>''' as the security contact, that is [[Taro]], the site's security lead. | ||
== Privacy (plain-language summary) == | == Privacy (plain-language summary) == | ||
Revision as of 19:29, 31 August 2026
How to reach 2swagg, and a summary of its legal and privacy posture. This page links to the site's own pages rather than reproducing legal text, which can change. Read the current About, Contact, Legal, and Privacy pages on 2swagg.net for authoritative wording.
Contact
- General, legal, copyright, privacy, and security matters go through a single contact address, linked from the site's Contact, Legal, and Privacy pages.
- 2swagg Pass support (renewals, PIN resets): [email protected]
Posture
The site's informational pages consistently describe it as "a small, independently operated community project" without an in-house legal department. People with copyright, content, or privacy concerns are asked to email directly and in good faith before pursuing formal action.
Security disclosure
The site asks security researchers to report vulnerabilities privately and not to post exploit details publicly: "We appreciate responsible disclosure and will review good-faith reports."
A machine-readable security.txt is published at 2swagg.net/security.txt and 2swagg.net/.well-known/security.txt. It names [email protected] as the security contact, that is Taro, the site's security lead.
Privacy (plain-language summary)
The site's Privacy page is a plain-language notice. In summary, it covers:
- All posts and uploads are public and may be copied, archived, or indexed by third parties outside the site's control.
- Standard technical and moderation data is collected: IP addresses, browser and device information, timestamps, cookies, and anti-abuse signals, retained for moderation, security, and compliance.
- Cookies are used for staff authentication and for site preferences.
- A standard disclaimer applies to third-party links and infrastructure.
Legal entity
The site footer names 2swagg community support LLC as the operator.
Public transparency pages
- Status and uptime: status.2swagg.net
- Ban log: 2swagg.net/bans (see Bans)
