Privacy

Akiwaki Privacy Policy

Effective Date: May 6, 2026

Quick Summary

This summary explains our privacy posture. The full policy below provides more detail.

Akiwaki AssistWe send only strict scheduling context to Akiwaki Core: date, time, town/city, and related timezone context needed to produce a scheduling result.
Akiwaki InsightCalendar reading and calendar access stay in your browser where possible. The API receives only minimal scheduling context plus free/busy availability windows, not full calendar contents.
What we avoidWe do not intentionally collect names, contacts, event titles, attendees, notes, descriptions, locations, full calendar exports, inbox content, or unrelated page content for scheduling analysis.
IdentityThe scheduling engine is designed not to require information that directly identifies a person or belongs to a specific person. Some operational data may still be processed for security, billing, support, or legal reasons.
PaymentsAkiwaki does not store raw payment card numbers or card security codes. Payment information is processed by third-party payment providers.
No sellingWe do not sell scheduling inputs, calendar signals, or free/busy availability information.

1. Scope

This Privacy Policy explains how Akiwaki collects, uses, shares, retains, and protects information when you use Akiwaki, Akiwaki Assist, Akiwaki Insight, Akiwaki Core API, our websites, apps, browser extensions, APIs, beta features, support, and related services.

This policy should be read together with our Terms of Service. If a separate written agreement, data processing agreement, or enterprise agreement applies, that agreement may contain additional privacy and security terms.

2. Our Core Privacy Principle

Akiwaki is built around data minimization. We aim to collect and process only what is needed to provide scheduling intelligence, protect the Services, support users, operate accounts and billing, comply with law, and improve reliability.

For scheduling analysis, Akiwaki is designed not to require personal identifiers. We do not need to know who a person is in order to convert a time, detect a timezone, flag a holiday, or suggest a better scheduling window.

3. Information Processed by Akiwaki Assist

Akiwaki Assist is designed for scheduling help while you write. When Akiwaki Assist needs Akiwaki Core to produce a scheduling result, the strict scheduling information sent to Core is limited to:

Akiwaki Assist is not designed to send your full message, inbox, contacts, email history, calendar, files, unrelated webpage content, or hidden page content for scheduling analysis. If a surface requires selected or typed text to detect date, time, or town/city context, the product should minimize that text before sending it to Core wherever technically feasible.

4. Information Processed by Akiwaki Insight

Akiwaki Insight may provide deeper scheduling and availability intelligence. Calendar reading, calendar access, and mapping calendar events back to your real calendar should stay in your browser or device where possible.

When Akiwaki Insight needs Akiwaki Core or our API to return suggestions, the API should receive only the strict minimum information needed:

Akiwaki Insight is not designed to send event titles, attendee names, email addresses, contact lists, event descriptions, locations, notes, attachments, full calendar exports, or full calendar content to the API for scheduling analysis unless a future product clearly discloses that change and obtains the required authorization.

5. Information Processed by Akiwaki Core API

Akiwaki Core API receives structured scheduling inputs from Akiwaki products or approved developers. The API is designed for scheduling intelligence, not identity collection. API customers and developers are responsible for minimizing what they send and for providing their own user-facing disclosures where required.

Akiwaki may reject, filter, limit, or delete inputs that appear unnecessary, excessive, sensitive, unlawful, abusive, or outside the intended scheduling purpose.

6. Information We Do Not Intentionally Collect for Scheduling Analysis

For scheduling analysis, Akiwaki is designed not to intentionally collect:

Please do not enter or send sensitive personal information unless a specific Akiwaki feature expressly asks for it and explains why it is needed.

7. Operational Information

Even when scheduling analysis does not require identity, we may process limited operational information needed to run a secure and reliable service. This may include device/browser type, app or extension version, timestamps, request identifiers, approximate region or timezone, error logs, security logs, rate-limit information, account status, billing status, and similar technical metadata.

Akiwaki tracks product usage signals, not personal identity. We do not store what you type. Product analytics are limited to aggregated events such as page views, typing started, conversion generated, city added, Best Times opened, copy clicked, and extension CTA clicked. These analytics do not store raw text, city names, emails, names, account profiles, cookies for identity tracking, or fingerprinting data.

Some operational information, such as IP addresses, account emails, billing records, or support messages, may identify or be linked to a person. We use this information only for the purposes described in this policy, such as security, support, billing, fraud prevention, abuse prevention, legal compliance, and service reliability.

8. Accounts, Support, and Communications

If you create an account, request API access, join a waitlist, contact support, purchase a plan, or communicate with us, we may process the information you provide, such as your email address, organization name, role, support message, product interest, billing status, and communication history.

We may send service-related communications, including security notices, account notices, billing notices, API notices, product updates, incident notices, and legal updates. Marketing communications, if any, will be handled separately where required by law.

9. Payments

If paid plans are offered, payments are processed by third-party payment providers. Akiwaki does not store raw payment card numbers or card security codes. We may receive and store billing metadata such as customer ID, plan, invoice status, payment status, tax information, billing email, and transaction records needed to operate paid services and comply with legal obligations.

10. How We Use Information

We use information to:

11. How We Share Information

We do not sell scheduling inputs, free/busy availability information, or calendar signals. We may share limited information only as needed with:

12. Retention

We retain information only as long as reasonably necessary for the purposes described in this policy, unless a longer period is required or permitted by law, security, fraud prevention, billing, tax, audit, dispute resolution, or legitimate business needs.

Scheduling inputs used for analysis should be retained for the shortest practical period consistent with service reliability, debugging, abuse prevention, and legal obligations. Free/busy availability signals should not be retained longer than needed to provide the requested Insight result unless otherwise disclosed or agreed.

13. Security

We use reasonable administrative, technical, and organizational safeguards designed to protect information. However, no online service, browser extension, API, storage system, or transmission method can be guaranteed to be completely secure.

You are responsible for protecting your devices, browsers, accounts, API keys, integrations, and credentials, and for using trusted networks and up-to-date software.

14. Your Choices and Rights

Depending on where you live and how you use Akiwaki, you may have rights to access, correct, delete, export, restrict, or object to certain processing of personal information. You may also have the right to withdraw consent where processing is based on consent.

To make a privacy request, contact privacy@akiwaki.com. We may need to verify your request and may be unable to fulfill a request where we do not maintain information that identifies you or where retention is required or permitted by law.

15. International Data Transfers

Akiwaki and its service providers may process information in countries other than where you live. Where required, we use appropriate safeguards for international transfers, such as contractual protections or other lawful transfer mechanisms.

16. Children

Akiwaki is not intended for children and is not designed to knowingly collect personal information from children. If you believe a child has provided personal information to us, contact privacy@akiwaki.com.

17. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. If changes are material, we will provide notice by reasonable means, such as posting an updated version, changing the effective date, emailing account holders, or requiring renewed acceptance where appropriate.

18. Contact

Questions or privacy requests may be sent to privacy@akiwaki.com.

Product Data Boundary Reference

Akiwaki AssistWhat Core/API receives: Date, time, town/city, timezone context, and minimal operational metadata.
What stays local or is not sent for scheduling analysis: Full messages, inboxes, contacts, calendars, unrelated page content, hidden page content.
Akiwaki InsightWhat Core/API receives: Date, time, town/city, timezone context, scheduling horizon, duration/preferences if provided, and free/busy availability windows or busy blocks.
What stays local or is not sent for scheduling analysis: Calendar reading and event mapping should stay in browser/device where possible; event titles, attendees, descriptions, notes, locations, attachments, contacts, and full calendar exports are not sent for scheduling analysis.
Akiwaki Core APIWhat Core/API receives: Structured scheduling inputs needed to return scheduling intelligence.
What stays local or is not sent for scheduling analysis: Developers should not send identifiers or sensitive data unless separately disclosed, authorized, and contractually approved.