Privacy policy
inerit blog is the official INERIT publication. Reading and likes are available without signing in; comments require an account. This policy describes information processed on blog.inerit.dev and your choices.
1. Operator and scope
The controller is Codemonkey Shin, operator of inerit blog. Contact codemonkeyshin@gmail.com for access, correction, deletion, restriction or account-data removal.
This policy covers blog reading, sign-in, comments, likes and feedback. Shared identity infrastructure is also described in the INERIT privacy policy.
2. Information, purposes and retention
| Activity | Information | Purpose and retention |
|---|---|---|
| Google sign-in | Identity-provider account identifier, Google name and photo URL, permissions and creation time | Identify members and show authors; until an account-deletion request is completed |
| Identity verification | Email and verification status supplied by Google | Sign-in and owner verification at the identity service; email is not separately stored in the blog member database |
| Comments and likes | Account association, comment text, reply relationships, timestamps and liked post | Participation; until you delete or unlike it, or account removal is completed |
| Authentication | Random session ID, CSRF value and sign-in verification state | Sessions valid up to seven days; login state valid ten minutes; expired records periodically removed |
| Rate limiting | Request IP and request count | Abuse prevention; Redis rate-limit entries expire within one hour |
| Error records | Request path, time, error type and diagnostic details | Troubleshooting; thirty days, then periodic removal |
| Feedback | Message and any contact details you include | Handle requests; at most 180 days, or earlier upon a completed deletion request |
The blog never receives or stores your Google password. Shared identity and infrastructure access logs follow the INERIT policy. Avoid unnecessary sensitive or third-party personal information in feedback.
3. What appears publicly
Comments display your account name, available profile photo, text and posting time. Google sign-in uses the name/photo provided by Google; INERIT accounts use their account details. Email and session information are not public. Sign in again after updating your profile to refresh it. Search engines or third parties may retain copies of public comments.
4. Cookies and browser storage
inerit_blog_session: necessary Secure, HttpOnly, SameSite=Lax session cookie, valid up to seven days.inerit_login_state: necessary sign-in verification cookie, valid ten minutes.- Local storage remembers your theme. Session storage remembers viewed posts for the current tab session to avoid repeated view increments.
You can remove or block storage in your browser. Blocking necessary cookies prevents reliable sign-in, comments and likes; public articles remain readable. The blog does not use advertising-tracking cookies.
5. Guest likes and sharing
To reduce duplicate guest likes, we store a random browser identifier and the liked post. The Secure, HttpOnly, SameSite=Lax cookie __Host-inerit_reaction lasts up to 365 days. Like records remain until unliked or the post is deleted. When you sign in, a like from the same browser can be merged with your account vote. Clearing cookies or using another device cannot reliably be recognized as the same person. Hashed browser/IP rate-limit identifiers and request counts expire within one hour.
Share buttons open your chosen platform or the device share menu. You decide whether to publish. The blog does not post for you or receive social-platform passwords.
6. External services and international connections
Choosing Google sign-in connects to Google and the INERIT identity service. Google LLC authentication and profile-image servers may process authentication and connection details, including IP addresses. Server locations and Google retention practices are described in the Google privacy policy. You can read without connecting a Google account.
External images and links may send connection details to their providers. We do not sell member data for advertising. The commenting feature does not use visitor comments as input to article-writing AI. Information is not provided externally except for lawful requirements or a separate request from you.
Articles containing KLIPY media load previews and media directly from its servers, which may receive IP and connection information. Reaction media plays automatically in a silent loop. The blog does not rehost the media or send member/comment data as GIF search input. External sharing screens follow their respective platform policies.
7. Deletion and backups
After verifying an account-removal request, the operator deletes its member records, sessions, comments and likes. If law requires retention, the relevant grounds, items and duration will be explained and use restricted.
Expired authentication data and error or feedback records past their retention period are periodically removed from the operational database. Recovery volume backups rotate through the latest seven daily backups and are not used to serve the site. Copies of deleted data leave with that rotation; confirmed deletion requests are reapplied following a restore.
8. Your rights
Edit or delete your own comments and remove likes after signing in. Email the operator to request access, correction, deletion, restriction, withdrawal or account removal. Proportionate identity checks may be needed to prevent unauthorized deletion.
Manage Google profile changes at Google. Disconnecting Google and deleting blog data are separate actions. Any lawful reason preventing a request will be explained. Korean privacy guidance is available from the Privacy Portal.
9. Protection
Browser-to-site HTTPS, secure sign-in cookies, server authorization and CSRF checks protect member activity. Editorial access is restricted separately. Authentication, comment and feedback request bodies are redacted from error diagnostics.
10. Effective date and updates
Effective 3 November 2026. Important changes to purposes, data categories or retention will be posted here with their effective date before taking effect. Contact: codemonkeyshin@gmail.com.