Privacy Policy

This policy covers the PERPOS services — Flow (the LINE AI assistant), Suite (organization ERP), Books (accounting and tax), and Agent (the AI assistant at agent.perpos.ai) — including connections to external services such as Google and LINE.

Account information: email, user ID, and profile information you set (such as display name and profile picture)

LINE connection information: your LINE user identifier when you link your account to use the bot or related features

Google connection information: tokens for connecting Google Drive and Google Calendar, and calendar event data as described in section 7

Organization data and content you submit: business data you record, files and documents you upload, meeting audio, and messages in your conversations with the AI assistant

Usage information: activity logs related to security, troubleshooting, and service improvement (such as request times and errors)

To provide the services and features you request, such as authentication, LINE connection, processing the work you request, and uploading files to Google Drive

To maintain security, prevent misuse, and verify access rights

For customer support, troubleshooting, and improving service quality

Customer files, audio, and AI assistant conversations are never used to train AI models.

We do not sell or share your personal data with third parties without your consent, except as required by law.

We use external processors only as needed to run the service:

• AI model providers: Google (Gemini), OpenAI, and Anthropic — limited to the content you submit in a conversation or upload yourself
• Meeting-recording provider: Recall.ai
• Cloud and infrastructure providers: Google Cloud, Supabase, Cloudflare, Contabo
• Payment provider: Stripe
• LINE (to communicate through the bot)

These processors are contractually bound to use the data solely to provide their service to us.

We may use cookies or browser storage (such as localStorage/sessionStorage) for system operation, keeping you signed in, and improving your experience. Google Analytics, used to understand how the website is used, runs only if you accept cookies, and you can change this at any time from “Cookie settings” at the bottom of the site.

Meeting audio is not stored permanently — it is deleted once processing completes. Meeting-summary files and transcripts are deleted from our servers within 48 hours.

AI assistant conversations are kept for at most 12 months and then deleted automatically; you can delete a conversation (including its attachments) yourself at any time.

Other information is kept only as long as necessary to provide the service or to comply with applicable laws or requirements. When it is no longer needed, we delete or anonymize it so that it can no longer identify you.

We keep encrypted system backups to recover from failures. Deleted information may remain in these backups for up to 6 months, is used only to restore the system, and is then removed on a rolling basis.

When you choose to connect your Google account to PERPOS, we request access only to the specific Google data required for the features you use:

(1) Google Drive (drive.file scope): we create a folder named “Perpos Assistant” in your Drive and upload only files that PERPOS itself generates, such as meeting-summary reports (PDF) and documents you ask us to save. We can access only the files PERPOS created or opened through the app — we cannot read, modify, or delete any other files in your Drive.

(2) Google Calendar (calendar.events scope): we read events on your primary calendar (such as title, start/end time, location, description, and online-meeting links) to send reminders and to schedule the assistant to join or transcribe meetings, and we create, update, or delete only the calendar events related to tasks you request.

We store your Google access and refresh tokens in encrypted form on our servers solely to call these APIs on your behalf. Your Google data is never sold, never shared with third parties, and never used to train or improve any AI models. You can disconnect at any time from your PERPOS app settings or at myaccount.google.com/permissions, which immediately deletes the tokens we hold.

PERPOS's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

PERPOS does not use, transfer, or sell Google user data to create, train, or improve any foundational or generalized machine learning or artificial intelligence models. This applies to raw, aggregated, anonymized, and derived data alike, and we do not transfer Google user data to any third-party AI service. This is enforced by design:

(a) The only Drive scope we request is drive.file, which we use solely to write files our system generates — we never read the contents of your Drive files, so no Drive content can reach an AI model.

(b) Google Calendar data is used only for reminders and scheduling inside our own infrastructure and is never included in any prompt sent to an AI model — the prompt we send is a fixed, static instruction with no Google data interpolated into it.

(c) Our AI features process only content you submit directly, such as meeting audio you record or upload and documents you upload, which is not data obtained from Google Workspace APIs.

We use AI model providers on paid/enterprise tiers whose terms state that data submitted through the API is not used to train their models — namely Google (Gemini), OpenAI, and Anthropic. The features that connect to your Google account (Drive/Calendar) use Gemini only, and as stated in (a)–(c) above, no data obtained from Google APIs reaches any model. Our multi-model AI assistant service (agent.perpos.ai) has no connection to your Google account at all. For the meeting-recording feature, the only information sent to our meeting-recording provider (Recall.ai) is the meeting link and the bot's display name — never the event title, description, or attendee list from your calendar.

Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including the Limited Use requirements.

We apply technical and organizational measures to protect your data, and in particular sensitive data such as Google account tokens, meeting content, and financial documents:

1. Encryption in transit — all traffic uses HTTPS/TLS only.
2. Encryption at rest — our database and file storage encrypt data at rest, and backups are encrypted before they leave our servers.
3. Access control — the table holding Google tokens has Row Level Security with a deny-all policy; it is reachable only by server-side processes using a service-role credential, and tokens are never exposed to the browser.
4. Tenant isolation — data is partitioned by owner and organization through Row Level Security.
5. Secrets management — keys and API credentials are held server-side in files accessible only to system administrators, not in source code, and internal services authenticate to each other with a shared secret.
6. Retention limits — as described in section 6.
7. Revocation — disconnecting your Google account immediately deletes the stored tokens.
8. Least privilege — we request only the scopes required for the features you use, and staff access to data is limited to what is necessary to operate the service and resolve issues.

You have the right to access, rectify, or delete your personal data through account settings or by contacting our team.

You can disconnect external services (such as Google Drive and Google Calendar) from the “User settings” page within the system.

We may update this policy from time to time. When we do, we will update the “Last updated” date above and publish the latest version on this page.