PRIVACY
Privacy Policy
Updated: November 18, 2026 · Operator: Taegyu Lee
This notice applies to the public beta of rhwp for Slack operated by Taegyu Lee. If your organization hosts the app itself, also consult that organization’s policies.
1. Information processed and why
- Document content: We download the requested HWP/HWPX document to convert it to PDF and images, open it in the editor, or save an edited copy.
- Document links: We retain workspace, channel, user and file identifiers, filenames, document hashes, and links between original messages and edited-copy threads. These support access checks, change detection, reopening in the same thread, and processing-status checks.
- Installation and settings: We retain installer, workspace and bot identifiers, workspace addresses, installation times and permissions, encrypted bot tokens, and channel settings. Editor sign-in uses Slack’s openid and profile permissions to verify user and workspace identity.
- Temporary records: We process sign-in state, single-use tickets, editing sessions, jobs, retries, and duplicate-prevention records. The API host uses security cookies lasting up to 10 minutes to bind installation and sign-in flows.
- Usage records: To operate and improve the service, we retain installation observations, PDF-preparation and Slack-publication event types and times, hashed keys distinguishing workspaces, installation generations and documents, and aggregates. Usage events do not contain document content or filenames. Separate linking records for aggregation and deletion include workspace identifiers and installation-generation paths.
- Operations and support: We use operational logs, including errors, processing times and status, and support inquiries you send to investigate problems.
2. Processing locations and service providers
Original documents, edited copies, PDFs and PNGs are stored in Slack. Google Cloud Run temporarily processes documents for conversion, opening and saving. Document content is not permanently stored in Firestore. Firestore stores the linking, installation, settings, temporary and usage records described above.
Cloudflare Pages delivers the public editor program and website. Document files and Slack secrets are not included in Pages deployments. Editing runs in your browser. Server processing is also necessary, so this is not a service in which all processing takes place solely on your device.
The public beta uses Slack, Google Cloud and Cloudflare. These providers may process connection information, such as IP addresses, for communications, security and operations, subject to their policies and account settings.
3. Website analytics
Web Analytics is connected to the Cloudflare Pages project, and a Cloudflare analytics script (beacon) is inserted into website and editor HTML. It measures page views and loading performance. Browser and site security policies may restrict execution and transmission.
See Cloudflare’s official explanation. Cloudflare retains received analytics data without sampling for 7 days, then uses sampled aggregates for longer-term statistics. Its analytics interface provides access to the previous 6 months of data. This access window does not specify when every raw record is deleted. See Cloudflare’s retention and access information.
4. Retention and expiry
Active document links, channel settings and installation information are retained while providing the service. Single-use editor tickets are valid for 1 minute; sign-in state for 10 minutes. Editing sessions become unusable after 10 minutes of inactivity or a maximum of 1 hour. Temporary event and completed-job records have expiry times of up to 7 days. In-progress jobs may remain until completion.
Expiry restricts access and is distinct from physical deletion. A Firestore TTL policy is active for the records collection group using the expiresAt field. Records with an expiry timestamp are deleted in the background, not immediately at expiry. These expiry periods do not apply to active links without an expiry timestamp or to separate usage records.
Workspace usage records have no separate automatic expiry. Deletion requests are handled after verifying authority and scope. Google Cloud Logging is configured to retain general operational logs for 30 days and required audit logs for 400 days. Support inquiries are received by email and used to handle the inquiry and follow-up responses. Contact us below with retention or deletion requests.
Removing the app blocks use of that installation and removes its stored encrypted token, but does not immediately erase all installation metadata, previous links, usage or operational records. Retention and deletion of files in Slack follow the workspace’s policies.
5. Access, transfer and deletion requests
Email meleeisdeveloping@gmail.com with your workspace address and the scope of your request. After verifying your authority, we handle requests to access, transfer or delete information retained on our servers. Linking records and usage aggregates are checked separately. Do not send passwords, bot tokens or sensitive original documents. Contact your workspace administrator as well if Slack files need to be deleted.
6. Contact and changes
Operator: Taegyu Lee · meleeisdeveloping@gmail.com. When processing practices change, this page and its updated date will be revised.