Privacy policy
AMUZ Co., Ltd. handles information about readers, newsrooms, contributors and staff as follows.
2026-09-27
Information and purposes
We use account email, password hashes, names, newsroom descriptions, languages, interests and background for authentication, review and account operation. Reporter names, bios, specialties, nationality, photos, AI status and affiliation support profiles and bylines. Manuscripts, sources, images, rights evidence and reviews support verification and publication. Staff records include name, email, E.164 phone, role, verification and invitation history, and notification choices. We also process feature requests, comments, audit records and API/OAuth permissions, expiry and revocation records.
Connections, cookies and visibility
Login sessions and security logs may include IP addresses and browser data. Reading deduplication uses daily one-way hashes, without raw IPs in aggregation tables. Where enabled, Google Analytics may send cookie, device and visit data to Google; advertising personalisation signals are disabled. Browser controls can restrict cookies. Published articles, reporter profiles and sources are public; passwords, private drafts, rights evidence and internal contact details are not.
Retention
Account data is retained for account operation and handled upon a verified closure or deletion request. Published reporting, corrections and rights evidence may be separately retained where needed for the reporting record or disputes, with reasons explained. Expired or revoked credentials cannot be used. Reading deduplication records become eligible for deletion after two days; non-identifying totals are retained. Operational records and enquiries are removed when their purpose ends, except where legal duties or active disputes require separate retention.
Service providers and connections
Service data is processed on our server and MariaDB; original and resized images use Cloudflare R2 and its CDN. Google SMTP handles staff emails; Sendgo and Kakao receive recipient phone numbers and necessary operational notices. Google processes analytics data where enabled. Authorised OAuth tools access data within granted account permissions. A designated Drive inbox transports completed manuscripts. Overseas providers may process data abroad; actual contractual settings and applicable rules govern these arrangements. Do not include unnecessary sensitive information in submissions.
Your choices and safeguards
Request access, correction, deletion, restriction, account closure or withdrawal of a connection at [email protected]. We verify identity or representative authority and respond within applicable procedures and periods. Staff recipients are configured in the operations panel. HTTPS, password/key hashing, account permissions, gated previews and audit records limit access. We explain restrictions required for legal retention or others’ rights.
Contact and changes
Privacy contact: Woojin Lee, representative of AMUZ Co., Ltd.; [email protected]; +82-2-1833-5770; floors 3–6, 623 Jungang-daero, Busanjin-gu, Busan, Korea. We publish changes and effective dates and provide required notice or consent procedures.