We did a fucky wucky UwU! A real bingo bango! Ouw engineews awe working VEWY hawd to fix it :3! Why don't you join ouw RP Discord server so we can help you OwO
Enable the blackbox to verbosely log all events into LocalStorage for debugging purposes! Note that these logs are *very big* and it's not recommended you share them with anyone outside the development team.
Hewwo! Dis should be included in youw error repowt.
The official GDPR text can be found here.
An interactive version of it can be found here.
The Service reserves the right to update this document as the Service owners see fit. Major updates to this document will be communicated to the Users of the Service via their primary communication channel (Email).
Snowflake: A standard for unique identifier numbers first developed by Twitter. Snowflakes are generated by the service.
shortname: An identifier generated by the service composed of letters and numbers.
object: Depending on the context, means both a file and a shorten.
The Service owners are located in Turkey, Brazil, and the United States.
The Service's servers are located in United States and Germany.
The Service uses Cloudflare, a US-based company. More information here.
The Service uses Backblaze, a US-based company. More information here.
The Service does not run advertisements. Because of that, the Service will not run tracking to run advertisements for the User.
The Service will not sell User information.
Other than the actual file data being stored to fulfill the purpose of the Service, the service stores this metadata about it:
Other than the actual URL the shorten is redirecting to, the service stores the following metadata:
The service does not want to risk having incorrect images be displayed on links to deleted images, so, to counteract that, we store objects' metadata even when the actual object information is deleted (and inaccessible from anyone, including the Service owners).
The deleted metadata is moved to a dummy account for anonymization.
To decrease the probability of malicious users brute-forcing all possible shortnames on the Service to have a mapping from shortname to file data, the User can opt-in to what is called "Paranoid Mode" where every generated shortname for their file will be longer.
"extrapolated" in this context means data that isn't directly stored but can be acquired by manual intervention.
The Service owners reserve the right to manually look into a User's personal information and object data/metadata for maintenance or ToS enforcing purposes, the second purpose is to maintain a positive image of the Service.
Users who break the ToS will have their Personal Data opened for the Service owners only. The Service owners might announce the account checking with the User IDs.
To keep the technical security and positive reputation of the Service, we collect metrics which may or may not be published to the general public, as described below:
Public metrics that are not tied to any User, or are generated by the Service:
Metrics the Service collects and will not be publicized:
This is the personal data the service directly accesses:
The Service uses Cloudflare to provide resilience against DDoS attacks. Because of every interaction through the Service passing through Cloudflare, Cloudflare may run tracking or analytics which we (the Service) can't disable.
The Service owners agreed to the GDPR Data Processing Addendum on Cloudflare on official domains on May 22, 2018.
We allow unofficial domains to be used in the Service. Unofficial domains are owned by third parties which are not the Service owners.
Usernames of these third parties may be publicly tied to their domains.
The most Service owners know is that third parties can look on their Cloudflare accounts' analytics and see aggregated information on who is using their unofficial domains.
The Service does its best to keep bad third party actors away by:
The Service owners backup all images sent in the Service every 12 hours automatically. The Service owners backup the Service's database every 30 minutes automatically.
Both of those backups are stored on the B2 service provided by Backblaze (which is a US-based company). Database backups are encrypted with all the Service owners' PGP keys. Image folder backups are encrypted using a strong passphrase available to some owners of the Service.