Terms of use
mcpg.cloud/configs stores encrypted blobs on your behalf and serves them back to anyone who presents the address. It is offered as-is, with no availability commitment.
What is stored
An encrypted payload, its public encryption parameters, digests of the tokens that authorise changing it, and timestamps. The service cannot read the payload and does not attempt to.
Lifetime
Every config expires. The default is seven days and the maximum is thirty; renewals cannot extend a config beyond one hundred and eighty days from when it was first published. Expired ciphertext is deleted.
Limits
Publishing is rate limited per source address, and a config may not exceed 256 KiB encrypted. The service may refuse a publish when its storage quota is exhausted.
Acceptable use
The payload is opaque by construction, so its contents cannot be inspected or moderated. Do not use the service to store or distribute anything other than configuration. Suspected abuse is addressed through rate limits and address-level blocks, which are the only tools that work against content nobody can read.
No warranty
The service may lose a stored config. Keep the plaintext you published; a downloaded copy is the only backup that exists, since nobody here can reconstruct one.