Scope
This policy explains how MATLOGIC handles account data, project records, uploaded project files, derived analysis data, service logs, and social sign-in data for matlogic.kr and related MATLOGIC services.
Information We Process
- Account data such as email address, display name, authentication method, and account status.
- Project data such as project names, workspace settings, uploaded files, edits, analysis records, and generated outputs.
- Usage and security data such as IP address, browser information, session events, timestamps, feature usage, errors, and abuse-prevention logs.
- Support data that you send to MATLOGIC when requesting help.
Google API Usage Disclosure
MATLOGIC uses Google Sign-In only for account authentication and account matching. The Google OAuth scopes requested by MATLOGIC are openid, email, and profile. From those scopes, MATLOGIC may receive your Google account subject identifier, email address, email verification status, and display name.
MATLOGIC does not request access to Gmail, Google Drive, Google Calendar, contacts, files, or other Google product content. MATLOGIC does not sell Google user data, use it for advertising, or transfer it except as needed to provide authentication, protect the service, comply with law, or support a user-directed account request.
MATLOGIC handles Google user data according to the Google API Services User Data Policy, including the Limited Use requirements where applicable.
Naver Sign-In
MATLOGIC uses Naver sign-in only for authentication and account matching, using the profile email/name data returned by Naver for that purpose.
Project Files and Derived Evidence
Uploaded source drawings and project files are customer-provided project materials. MATLOGIC may process them to create derived evidence, redacted review surfaces, metrics, annotations, and decision-support outputs. Official reports and packages must not expose raw editor or debug layers.
Sharing
MATLOGIC does not sell personal information. Data may be shared with service providers, when required by law, to protect the service, or when you direct MATLOGIC to share a project, workspace, report, or output.
Payment and Billing Data
Paid subscriptions are processed by Paddle.com acting as the Merchant of Record (seller of record) for those transactions. MATLOGIC does not receive or store full payment card numbers. Paddle processes your payment, billing, and tax data as the seller of record to charge your subscription, calculate and remit applicable taxes, and issue invoices and receipts.
From this process MATLOGIC stores only the billing identifiers needed to grant and manage your subscription, such as the Paddle subscription id and customer id. MATLOGIC uses these identifiers to match a payment to your account and to enable or disable paid features.
As the payment processor, Paddle handles your payment information under its own privacy notice. See the Paddle Privacy Notice for details on how Paddle processes payment and billing data.
Retention and Deletion
MATLOGIC retains account and project data while your account or workspace remains active, unless a longer period is required for security, billing, dispute, backup, or legal records. You may request account or data deletion through MATLOGIC support.
Contact
Questions can be sent to yangjaejun@segment.im.