Effective date: October 4, 2026
Who we are
Scuffed Network LLC operates blog.scuffed.pink. This policy explains how we handle personal information when you browse the blog, create an account, comment, or contact us. For privacy questions or requests, email [email protected].
Information we collect
You can read the blog without an account. If you register, we store your username, email address, protected password information, and any profile details you choose to provide. Registration creates a subscriber account; ordinary subscribers cannot publish posts or upload media.
You must be logged in to comment. We store your comment, its author and account information, submission time, IP address, browser user-agent information, and moderation information. Approved comments, your display name, any public website link you provide, and your avatar may be visible to everyone. Your account email address is not published as part of the normal comment display. Avoid putting private or sensitive information in comments or public profile fields.
Our server and security services process technical information such as IP addresses, requested pages, request times, response codes, browser information, and referring pages when supplied. If you email us, we receive your email address, message, and any attachments you send.
How we use information
We use information to operate accounts and comments, send account and password-reset emails, respond to requests, prevent spam and abuse, maintain security, and troubleshoot the site. Password-reset emails may include the IP address associated with the request. We do not use this blog for advertising, marketing newsletters, or additional visitor analytics, and we do not sell personal information.
Spam checks and avatars
We use Akismet, provided by Automattic, to check comments for spam. Comment information, including comment text, author details, IP address, browser information, and related technical information, may be sent to Akismet. See Automattic’s privacy notice for visitors to sites using its services.
Gravatar is enabled for profile pictures. Your browser may contact Gravatar to load an avatar, and a hash derived from your email address may be used to find it. Hashing does not make an email identifier necessarily anonymous. Gravatar may also receive your IP address and browser information when an image is requested. See Automattic’s privacy policy.
AI-assisted comment moderation and replies
The blog has AI-assisted comment moderation and suggested-reply features enabled, using the OpenAI provider integration. When these features run, comment text and the commenter’s name can be sent to OpenAI to analyze the comment or help prepare a reply. Reply assistance can also include the related post’s title and excerpt. Any personal information you include in the comment itself may therefore be processed by the provider.
We store moderation results with comments. AI request logging is enabled and can store prompt and response previews, request details, and usage information for administration and troubleshooting. These records currently have no automatic deletion deadline. Provider processing is governed separately by its applicable terms and data controls; see OpenAI’s API data-handling documentation. We do not promise zero retention or a particular provider-account training setting. Contact us if you have a concern about AI processing or a moderation decision.
Cookies
WordPress uses cookies for login, security checks, and preferences. A login-page test cookie checks whether your browser accepts cookies and normally disappears when the browser closes. Login cookies normally last two days, or two weeks if you choose “Remember Me”; logging out removes login cookies. Screen-preference cookies can last a year.
Where WordPress offers an option to remember comment-form details, choosing it can store your name, email address, and website in your browser for one year. Author and editor accounts may also receive a one-day cookie identifying the post being edited. You can clear or block cookies in your browser, but doing so may prevent login or other features from working.
Cloudflare protects and delivers the site and may set security and challenge cookies, including a clearance cookie after a browser verification. These are separate from WordPress cookies. See Cloudflare’s cookie information and Cloudflare’s privacy policy.
Embedded content and links
A post may contain content hosted by another service, such as a video or image. When that content loads, the provider may receive technical information, use cookies, and associate activity with an account you hold with it. Its own privacy policy applies to that processing. Following an external link takes you to a separately operated website.
Service providers and other disclosures
Our hosting provider, OVHcloud, and Cloudflare process information needed to host, deliver, and protect the blog. Akismet, Gravatar, and the AI provider process information as described above. Email delivery involves the mail services used by us and the recipient. See OVHcloud’s personal-data information.
Authorized administrators can access information needed to operate the site and handle requests. We may also disclose information when reasonably necessary to comply with applicable law, respond to valid legal process, protect rights and safety, or investigate abuse. The blog is hosted in the United States; service providers may process information in other countries.
How long we keep information
Account information is kept while the account exists and until it is removed, subject to legitimate security or legal needs. Comments and related moderation information can remain indefinitely unless removed. AI request logs currently have no automatic expiry. You can ask us to review or delete information associated with you.
Routine web-server logs are configured for daily rotation with 14 rotated copies. Routine WordPress backups are scheduled to age out after approximately one week. These are operational schedules, not guarantees that every copy disappears on that exact date: manual recovery copies, correspondence, security investigations, and records required by law may remain longer. Deleted information may persist in restricted backups until those copies are replaced or removed. Provider retention is governed by the provider’s applicable practices.
Your choices and privacy requests
You can edit available profile fields after signing in. Standard account settings do not provide a self-service account-deletion function. To request access, an export, correction, account deletion, or removal of comments or related information, email [email protected]. Tell us enough to locate the account or comment, but do not send your password or login/reset codes.
We may ask for proportionate verification before disclosing or changing personal information. We will consider requests and respond as required by applicable law. Some information may need to be retained for security, legal obligations, or the rights of others. Removing information from this blog does not necessarily remove copies other people have saved or that independent services control. Depending on where you live, you may have additional privacy rights, including the right to complain to a relevant regulator.
Changes to this policy
We will update this page and its effective date when our practices change. New services or uses of visitor information should be reflected here before they are introduced. Contact [email protected] with questions about this policy.