Privacy Policy

Last updated: November 2, 2026

1. Overview

Riano is operated by HunyDev (후니데브), a sole proprietorship in the Republic of Korea. This Privacy Policy describes how HunyDev ("Company", "we", "us") collects, uses, and protects your personal information when you use our Service.

2. Information We Collect

Account Information

When you sign in with Google, we receive your stable Google account identifier, name, email address, and profile picture. This information is used for authentication and account management.

Organization accounts also include organization and contact names, email addresses, account status, salted password hashes, invitation or verification tokens, and purchased and assigned seats. We do not store plaintext account passwords. Invitation and verification links expire after 24 hours and are invalidated when used.

Purchases and Access Rights

We store internal buyer IDs, checkout and order references, product IDs, quantity, price, currency, payment and refund status, and personal or organization access-right records. These verify lifetime purchases, prevent duplicate grants and support refunds and recovery. Older or manually assigned rights are recorded separately from confirmed Polar purchases. Polar handles checkout and payment infrastructure, including Stripe services. Riano does not store full payment card numbers or card security codes.

Usage Data

We collect anonymous usage data such as page kinds, modules opened, interaction flags, foreground time and broad device categories to improve the Service. A temporary identifier groups activity in one browser tab; it is not linked to your account. Account identity, IP addresses, search queries and module input values are not recorded in usage analytics.

Signed-in foreground activity is also recorded separately under your account: its first and last observed activity times and the Korean calendar dates on which you return. Administrators use these records for last-active times and aggregate account return rates. Daily records are kept for up to 90 days; first/last observation times remain until account deletion. These records contain no page, module, device or anonymous analytics identifiers and are never joined to anonymous sessions. The same analytics opt-out, Do Not Track and Global Privacy Control apply; turning collection off does not erase earlier observations.

Anonymous analytics may also record trial starts, login prompts and clicks, confirmed login completion, resumed interaction, daily-limit prompts and upgrade clicks. Trial duration, daily module allowance and whether a free-access event is active provide context for these aggregate reports. These analytics records are not linked to your account.

Traffic analytics records only the referring website hostname and a recognized source tag, never the referring page URL or its search query. A session retains its first source. Public app and blog requests are counted in hourly groups by page, source and broad browser or bot classification, including crawlers that do not run JavaScript. Raw IP addresses, raw User-Agent strings and per-request identifiers are not stored in these analytics. Browser-like signals do not prove a human visitor. We respect Do Not Track, Global Privacy Control and the analytics opt-out preference cookie.

Interactive Access Records

To enforce your account's daily allowance, we store the dates and canonical IDs of the interactive modules you choose, linked to your account. These essential access records are separate from anonymous usage analytics and contain no slider values or module inputs. Guest trial progress is kept in this browser tab's session storage, separately for each module.

Access dates older than seven days are removed during routine cleanup. Deleting your account also deletes its interactive access records.

Feedback Data

If you submit feedback or bug reports through the Service, your email address (if provided) and the content of your message are collected to respond to your inquiry.

Feedback, an optional reply address and the page path are stored in our private Cloudflare database and reviewed through our Admin inbox. Internal notes and status changes help track follow-up. We may turn an administrator-reviewed summary into a development request; reply addresses are not automatically copied into development instructions. Short-lived, keyed IP hashes limit repeated submissions and are separate from analytics. Older feedback originally submitted through GitHub may be retained there and imported into this inbox. Use email for private account, payment or privacy matters.

Security and Administration

Security records include account and rights changes, the operator or system that made them, internal references and timestamps. Failed-login limits use a keyed hash of the client IP address rather than storing the raw address in the limit table. Hosting and email providers may process request, network and delivery information under their own service terms; this is separate from our usage analytics dataset.

3. How We Use Your Information

  • To provide and maintain the Service
  • To manage your account and one-time lifetime or organization access rights
  • To preserve valid purchases, recover service and prevent fraud or unauthorized access
  • To respond to support requests and feedback
  • To improve the Service based on aggregated usage patterns

Necessary account and purchase processing fulfills the service and access contract. Applicable transaction recordkeeping meets legal duties. Limited security records protect accounts and the service. Optional analytics can be disabled without changing required account or purchase processing.

4. Data Sharing

We do not sell, trade, or rent your personal information to third parties. We may share data only with third-party service providers necessary for operating the Service (e.g., payment processing, hosting), and only to the extent required.

  • Google: authentication and, where used, font delivery.
  • Cloudflare: hosting, database processing, network protection and private encrypted backup storage.
  • Polar: checkout, merchant payment operations and transaction support, including Stripe payment infrastructure. Polar also processes buyer information under its own privacy policy.
  • GitHub: legacy feedback records, private development and operational workflows, and encrypted backup copies.
  • Zoho: support and privacy email delivery and storage.

These providers may process information outside the Republic of Korea, including in the United States and other locations in their published processing and subprocessor information. Transfers occur electronically during sign-in, checkout, feedback, email, hosting and backup operations. We use encrypted connections and provider protections, and obtain separate consent where required. Provider processing locations and independent legal retention duties may differ from Riano's own schedule.

5. Data Storage and Security

Your data is stored securely and we implement appropriate technical and organizational measures to protect against unauthorized access, alteration, or destruction. However, no method of transmission over the Internet is 100% secure.

Private database snapshots are encrypted and stored in Cloudflare R2 and the workflow storage of our private GitHub repository. The snapshot decryption key is held separately from R2. Full snapshots expire after 28 days; D1 separately provides its short-term recovery history, currently within a 30-day window. Restorations are verified in an isolated database and current deletion instructions are reapplied before recovered data is used.

6. Data Retention

Account profiles and organization management data are retained while the account and service relationship are active. Minimum purchase and rights records are retained while needed to honor an active lifetime or organization entitlement.

  • Contract, cancellation, payment and supply records: generally five years where Korean electronic-commerce recordkeeping rules apply; minimum records can remain necessary for a longer active access contract or other legal obligation.
  • Consumer complaint or dispute correspondence: up to three years where required; other correspondence is removed when no longer needed.
  • Usage analytics: up to 90 days in the operational database. Account-linked daily access records are removed after seven days during routine cleanup.
  • Administration audit records: a rolling year. Failed-login counters expire after a 15-minute window and are cleared during routine cleanup.
  • Minimal deletion instructions: 90 days for recovery safety; contract cancellation evidence is kept for the applicable five-year period.

Deleting an account removes its live profile promptly, ends personal and assigned organization access, and permanently abandons purchased lifetime rights. Rejoining with the same Google account does not restore those rights. Deletion does not automatically refund a purchase. If processing is temporarily unavailable, accepted deletion instructions are retained for completion. Required transaction records remain with restricted use.

A short-lived backup can retain a previous version until its rolling retention period expires. It is not used to reactivate a deleted profile or abandoned rights. A separate deletion journal uses a hashed internal subject reference and timestamp rather than the deleted Google profile and expires after 90 days. Feedback or correspondence not linked to an account may require you to identify the message in a separate privacy request.

7. Cookies

The Service uses an essential session cookie for authentication and tab-scoped session storage for anonymous usage analytics. Your analytics preference is stored on your browser. We do not use third-party tracking cookies for analytics. You can disable anonymous analytics on the Cookie Policy page; browser Do Not Track and Global Privacy Control signals are also honored.

Advertising on public articles

When advertising is enabled on Riano Blog, Google and other third-party vendors may use cookies or similar technologies to serve, measure and personalize ads based on visits to this and other websites. Google's advertising cookies enable Google and its partners to serve ads based on those visits. These advertising services are separate from Riano's anonymous usage analytics.

You can manage personalized advertising in Google My Ad Center and opt out of some other vendors' personalized advertising through YourAdChoices. Learn how Google uses data on sites that use its services. Where an advertising consent message is shown, use its privacy settings to change or withdraw your choice. Disabling Riano's usage analytics does not change your advertising preferences.

8. Your Rights

  • Access the personal data we hold about you
  • Request correction of inaccurate data
  • Request deletion of your account and associated data
  • Withdraw consent for data processing at any time

To exercise these rights, contact us at jang@huny.dev.

9. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated revision date. We notify users of material changes where required and request additional consent when the law requires it. Continued use alone does not replace required consent.

10. Contact

For privacy-related inquiries, contact us at jang@huny.dev.