This Privacy Policy explains how Multibook Philippines Inc. ("we", "us", or "ANTE") — a Philippine corporation and a subsidiary of Multibook (Tokyo, Japan) — collects, uses, and shares information when you use ANTE, the ERP software available at ante.work and related domains. Our Philippine office is at Unit 405 Cattleya Condominium, 235 Salcedo Street, Legaspi Village, San Lorenzo, Makati City, Philippines.
This policy is designed to comply with the Philippine Data Privacy Act of 2012 (Republic Act 10173), the EU General Data Protection Regulation (GDPR) where applicable, and the Google API Services User Data Policy (including its Limited Use requirements) for the Google services you choose to connect.
1. What we collect
- Account data: your name, work email, employer, role, and password hash.
- Workspace data: the operational data you enter into ANTE — employees, payroll, projects, customers, invoices, attendance records, and similar. You own this data.
- Usage data: aggregated, anonymized telemetry (feature usage, performance metrics, error reports) used to operate and improve the product.
- Communications: emails, support tickets, and chat messages you send us.
- Google account data: when you choose to connect a Google service to your ANTE workspace, we receive data from that Google service under the scopes you authorize. See Section 4 — Google user data below.
2. How we use it
- To provide the ANTE service and the features you have configured.
- To send transactional notifications (e.g., payroll completion, approval requests, attendance alerts).
- To improve product quality based on aggregated, anonymized usage.
- To respond to your support and sales inquiries.
- To meet legal, tax, and audit obligations under Philippine law.
3. Legal basis
We process personal data on the legal bases of (a) performance of the contract under which we provide ANTE, (b) your consent for optional integrations such as Google services, (c) our legitimate interest in operating and improving the product, and (d) compliance with applicable law.
4. Google user data
ANTE integrates with several Google services to deliver specific features. You choose which (if any) services to connect; nothing below applies unless you initiate the connection from your ANTE workspace and consent on Google's OAuth screen.
4.1 Google Sign-In (openid, profile, email)
- Why: to let you sign in to ANTE with your Google account instead of a separate password.
- What we access: your Google account ID, name, profile picture URL, and primary email address.
- How we store it: mapped to your ANTE user record so subsequent sign-ins resolve to the same account.
- Retention: for as long as your ANTE account exists. Removed on account deletion (see Data deletion).
4.2 Gmail (gmail.send, gmail.readonly)
- Why: to send transactional ANTE emails (payslips, invoices, approval notifications) from your own Gmail address so recipients see them as coming from you, and to read replies to those messages for in-app threading.
- What we access: permission to send mail on your behalf, and read access scoped to messages relevant to the threads ANTE creates.
- How we store it: we store OAuth refresh tokens encrypted at rest, plus minimal message metadata (message IDs, thread IDs, subject lines) needed for threading. We do not store full message bodies beyond the active processing window.
- Retention: tokens are retained while the integration is connected. Cached metadata is purged when you disconnect the integration or delete the related ANTE record.
4.3 Google Drive (drive.file)
- Why: to attach Drive files to ANTE records (e.g., contracts to a project, receipts to an expense) and to export ANTE reports back to your Drive.
- What we access: only files you explicitly select via Google's file picker, or files ANTE itself creates in your Drive. ANTE does not browse your wider Drive.
- How we store it: file IDs and basic metadata (name, MIME type, link) are stored alongside the ANTE record they are attached to. File contents remain in Drive.
- Retention: while the connection is active and the linked ANTE record exists. Removed on disconnect or record deletion.
4.4 Google Calendar (calendar.events)
- Why: to sync ANTE-scheduled items (interviews, leave windows, project milestones, meetings) into your calendar, and to read events you create that ANTE should reflect.
- What we access: read and write access to events on the calendar you authorize.
- How we store it: we store event IDs and a minimal mirror (start, end, title, attendee count) tied to the ANTE record. We do not store private notes or attendee email addresses beyond what's needed for the linked ANTE flow.
- Retention: while the connection is active. Mirrored events are removed on disconnect.
4.5 Limited Use commitment
ANTE's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically, ANTE does not:
- Use Google user data to train, develop, or improve generalized or non-personalized AI/ML models.
- Transfer or sell Google user data to third parties for advertising, data brokerage, or marketing purposes.
- Allow humans to read Google user data, except (a) with your explicit consent for a specific support ticket, (b) for security investigations or to comply with applicable law, or (c) where the data has been aggregated and anonymized.
You may revoke ANTE's access to your Google data at any time. See Data deletion for instructions.
5. Subprocessors
We use a small number of vetted third-party services to operate ANTE (cloud hosting, email delivery, error monitoring, payment processing). The current list is published on our Trust Center and updated when it changes. When you connect Google services, Google LLC is also a subprocessor for that data.
6. Data residency
Your workspace data is stored on servers in the Asia-Pacific region (Singapore primary). Enterprise customers may self-host ANTE on their own infrastructure — in which case the data never leaves your network and the residency clauses above do not apply to your installation.
7. Retention
- Workspace data: retained while your subscription is active and for 30 days after termination (read-only export window), after which it is permanently deleted.
- Google-sourced data: retained only while the corresponding Google integration is connected to your workspace, and purged within 30 days of disconnection.
- Anonymized aggregate analytics: retained indefinitely; cannot be linked back to you.
- Legal/financial records: retained as long as required by Philippine law (typically 10 years for accounting records).
8. Your rights
Under the Philippine Data Privacy Act and, where applicable, the GDPR, you may request to access, correct, port, restrict, or delete your personal data, and to withdraw consent for optional processing such as Google integrations. To exercise any of these rights, email privacy@ante.work. We will respond within 30 days.
9. Security
We encrypt data in transit (TLS 1.2+) and at rest. Google OAuth tokens are stored using authenticated symmetric encryption. Access to production data is restricted to a small number of authorized engineers and logged. Details on our security posture live in the Trust Center.
10. Children
ANTE is a workplace tool for businesses and is not directed to anyone under the age of 18. We do not knowingly collect personal data from children.
11. Changes to this policy
We will post any material changes to this policy on this page and update the "Last updated" date above. For changes that meaningfully affect how we use Google user data, we will provide at least 30 days' advance notice by email to workspace administrators before the change takes effect.
12. Contact
Questions about this policy or to exercise your data rights: privacy@ante.work.
Postal: Data Protection Officer, Multibook Philippines Inc., Unit 405 Cattleya Condominium, 235 Salcedo Street, Legaspi Village, San Lorenzo, Makati City, Philippines.