Legal & privacy.

Be decent. Credit people.

Don’t post harassment, threats, private information about others, spam, malicious files or unlawful content. Share only material you have permission to share. AI-assisted work is welcome; you’re still responsible for what you publish and for crediting work you use.

Moderators may review reports, remove content and restrict accounts to protect the community. Release approval doesn’t certify ownership, quality or safety. If you think a decision is wrong, contact the moderation team.

Your work stays yours.

You keep the rights you hold in your uploads and posts. By sharing them here, you give Caulk permission to store, process and display them to provide the site, including thumbnails and link previews. We don’t take ownership of your work.

Posting something here doesn’t automatically give everyone an open-source or commercial-use licence. State the permissions or licence for your release, and respect any third-party assets or game content it contains.

For a copyright or ownership report, send the moderation team the content URL, identify the work and explain your relationship to its rights holder. Don’t post personal evidence publicly.

Downloads come from people.

Hosted downloadable files are ZIPs up to 500 MB each. We validate uploads and control access, but we don’t scan archives for malware or guarantee their contents are safe. Download and run community files at your own risk; inspect them and use appropriate precautions.

Use the file’s report action if something is unsafe or infringes someone’s rights. Moderators can take files down. External links go to services we don’t control, with their own rules and privacy practices.

This is a small community, not a guaranteed backup service. Keep your own copies. These rules don’t remove rights you have under applicable law.

What we keep, and why.

Discord sign-in supplies an account identifier, name, email address and available profile information. We store account and session records, provider credentials needed for sign-in, your profile, posts, comments, reactions, uploads and messages. Your email, sign-in tokens and session records aren’t shown on public profiles.

We use account and content data to provide the features you request. We also process security and moderation information for our legitimate interests in running a safe service: session information may include your IP address and browser details, and abuse protection uses hashed IP-based counters. Hosting logs may contain request and connection information.

Posts, profiles, the guestbook and published images are public. Uploaded images use public URLs; a hard-to-guess URL isn’t a privacy control. Hosted ZIP downloads require authorization. Validated images attached to a release awaiting approval may already be reachable if someone knows their image URL.

Global chat is visible to signed-in members. DMs are restricted to their participants in the site interface, and reported messages can be reviewed by moderators. Messages aren’t end-to-end encrypted; site operators can access stored information where necessary for support, security, moderation or legal obligations.

Cloudflare provides hosting, storage, network and security services; Discord provides sign-in. The site also loads fonts from Google Fonts, which involves requests from your browser to Google. These providers may process information across countries under their own applicable arrangements. See Cloudflare’s privacy policy, Discord’s privacy policy and Google’s privacy policy.

Cookies and retention

Cookies support sign-in and authentication security. We haven’t added advertising trackers or third-party analytics scripts. Signing out ends your session; it doesn’t delete your account or posts.

Published posts show an approximate view count to indicate readership. A visible post open sends a first-party request after two seconds. For signed-in members, we verify the existing sign-in session and keep a keyed hash of the account identifier and post together. For guests, the hash uses the network address and post. These short-lived records are pseudonymous: the counter does not store raw account identifiers or network addresses. They become eligible for bounded cleanup after 30 minutes; aggregate totals remain with the post. Signed-in members sharing a network count separately, while guests on a shared network can be combined. Signing in or out can produce separate guest/member views. No additional tracking cookie is set for this feature.

Deleting a post, comment or message hides it from normal views. Moderation records and snapshots of reported content can remain for review; public image URLs and cached copies may remain accessible.

Account and public content records remain while needed to run the community, unless removed following a request or moderation decision. Chat messages are eligible for cleanup after 90 days, with unresolved reports retained for review; cleanup happens gradually as chat is used. Unattached uploads and temporary security records have shorter expiry periods. Reports and operational records may be kept while needed to resolve issues or prevent abuse. Copies in provider backups or caches can take longer to disappear.

Your information

Contact the team to ask about accessing, correcting or deleting your information, or objecting to or restricting its use. Other rights, including portability, may apply depending on the circumstances. We may need to verify that the account is yours. If a privacy concern isn’t resolved, you can complain to the UK Information Commissioner’s Office or your local data-protection authority.

Talk to a human.

Contact the Caulk moderation team through the Caulk Discord ↗ for privacy requests, copyright reports or moderation questions. Ask to speak privately before sending personal information. The cube cannot process paperwork.