Click here to go back to the beepboop.systems' main page.
Other legal documents at beepboop.systems:
Things on this document:
beepboop.systems (the root domain of the site) does not
collect any personal information. The only information collected is in
the form of server logs, which:
- are purged periodically, from time to time, except for analysis in the case of server outage, downtime, or security incident; and
- contain only IP address, and path requested.
If you'd like your entries in server logs purged, please send mail to
webmaster@beepboop.systems with your IP address. You should
get a response in a maximum of thirty (30) business days.
git.beepboop.systems (the self-hosted Gitea code forge)
does collect personal information. Information collected
includes:
- name or alias used to register;
- email address used to register; and
- user contributed content in the form of git commits, tags, annotations, issues, pull requests, etc.
If you'd like your git information purged, please send mail to
webmaster@beepboop.systems with your account name and proof
of account ownership. You should get a response in a maximum of thirty
(30) business days.
If you'd like, you can also delete your Gitea account via the built-in web interface, by navigating to the settings page, clicking on 'Account', and scrolling all the way to the bottom to see the account deletion area.
git.beepboop.systems is not subject to CCPA or GDPR
regulation, because it fails the same tests that
beepboop.systems fails. For more information, read down to
CCPA compliance and GDPR compliance, below.
bit.beepboop.systems, aka
bitwarden.beepboop.systems (the self-hosted Bitwarden
instance) does collect personal information: Information
collected includes:
- name or alias used to register,
- email address used to register, and
- encrypted and inaccessible forms of user submitted content (like passwords)
If you'd like your Bitwarden information purged, please send mail to
webmaster@beepboop.systems with your account name and proof
of account ownership. You should get a response in a maximum of thirty
(30) business days.
Additionally, you can delete your Bitwarden account in the web interface.
bit.beepboop.systems is not subject to CCPA or GDPR
regulation, because it fails the same tests that
beepboop.systems fails. For more information, read down to
CCPA compliance and GDPR compliance, below.
All other subdomains at beepboop.systems are personal, non-publicly-available instances of self-hosted software.
CCPA compliance
Pursuant to the California Civil Code, div. 3, part. 4, title 1.81.5 ("The Californica Consumer Privacy Act of 2018"), 1798.40, beepboop.systems fails the 1798.140(d) test -- that is, beepboop.systems is not a business:
- “Business” means:
- A sole proprietorship, partnership, limited liability company, corporation, association, or other legal entity that is organized or operated for the profit or financial benefit of its shareholders or other owners, that collects consumers’ personal information, or on the behalf of which such information is collected and that alone, or jointly with others, determines the purposes and means of the processing of consumers’ personal information, that does business in the State of California, and that satisfies one or more of the following thresholds:
beepboop.systems fails being a "sole proprietorship, partnership, [...], or other legal entity that is organized or operated for the profit or financial benefit of its shareholders", because it's run by one person.
Reading on:
- As of January 1 of the calendar year, had annual gross revenues in excess of twenty-five million dollars ($25,000,000) in the preceding calendar year, as adjusted pursuant to paragraph (5) of subdivision (a) of Section 1798.185.
- Alone or in combination, annually buys, sells, or shares the personal information of 100,000 or more consumers or households.
- Derives 50 percent or more of its annual revenues from selling or sharing consumers’ personal information.
I'm a person, and my behavior fails all three tests.
The only remaining relevant prevision of the 1798.140(d) that I could satisfy is this:
- A person that does business in California, that is not covered by paragraph (1), (2), or (3), and that voluntarily certifies to the California Privacy Protection Agency that it is in compliance with, and agrees to be bound by, this title.
I don't do business in California, even though I am not covered by 1798.140(a-c). I also haven't voluntarily certified to the California Privacy Protection agency anything, because I haven't agreed to be bound by the title. Thus, because beepboop.systems is not a business, the CCPA does not apply to beepboop.systems.
You're more than welcome to request erasure via the privacy policy above, though.
GDPR compliance
Persuant to Regulation 2016/679 of the European Parliment, also known as the General Data Protection Regulation, or GDPR, beepboop.systems is not subject to its provisions because it fails the Chapter 1, Article 2.2c test:
- This Regulation does not apply to the processing of personal data:
[...]
- by a natural person in the course of a purely personal or household activity;
beepboop.systems is hosted as a hobby, which qualifies under the "purely personal" language.
You're more than welcome to request erasure via the privacy policy above, though.
beepboop.systems or any other service therein,
you constitute full acceptance to these terms.
beepboop.systems services immediately.beepboop.systems
is expressly forbidden. beepboop.systems has no active bug
bounty program. Instead of exploitation, send mail to
webmaster@beepboop.systems regarding any vulnerabilities on
the site.All materials accessible on beepboop.systems are
licensed CC0, except where otherwise noted.
All materials on git.beepboop.systems have their own
licenses -- be sure to respect those.