Privacy Policy
This is an English reference translation. The Japanese version is the official version, and it prevails if there is any difference.
How we handle your data
Email is sensitive, so we keep to these four rules.
We don't store email bodies on our servers
They're used only while posting to Slack and drafting with AI, and deleted as soon as that's done (what's posted to Slack stays in Slack).
Set up so it isn't used to train AI
The OpenAI API doesn't use what we send for training. We also ask OpenAI not to keep the exchanges (store: false). OpenAI may still keep records for up to 30 days to monitor abuse.
Draft bodies are deleted after 30 days
The body of a draft you edit in Slack is deleted 30 days after its last edit. Drafts saved to Gmail stay in Gmail.
Never used for ads or sold
Following Google's API Services User Data Policy, email bodies are used only to show them in Slack and draft replies with AI (and, for rules with article summaries on, to summarize the linked articles), and our staff do not read them (except in the cases set out in our privacy policy).
STUDIO SPOON Inc. (“we”, “us”) has established this Privacy Policy (this “Policy”) to explain how we handle users’ personal and usage information in connection with our service SuccocoPon (the “Service”).
1. Information we collect
The Service collects the following information to provide its features.
1.1 From your Google account
- Email address, name and profile picture (for sign-in)
- Gmail message headers, bodies and attachments (only for emails with the labels you choose)
- Your list of Gmail labels (for setting up forwarding rules)
- Profile information of contacts (the sender’s picture and display name) (obtained through the Google People API scope
contacts.other.readonlyand used to show the sender’s icon in Slack notifications) - OAuth refresh tokens (for continued API access)
1.2 From your Slack workspace
- Workspace ID, list of channels, and basic user information (display name, email address)
- Bot token
- The language settings of users and channels (looked up to choose the language of the buttons and messages we show in Slack; not stored)
1.3 Generated through use of the Service
- Identifiers of ingested messages (Gmail message ID, thread ID)
- Subject and sender of messages (as a record of forwarding)
- Draft bodies and the back-and-forth of your instructions to the AI (for up to 30 days after the last edit)
- The list of links in an email, kept to summarize the linked articles (only when article summaries are turned on for a forwarding rule; for up to 30 days after creation)
- Identifiers of created Gmail drafts
- Your display language and AI draft language settings (your browser's language when you signed up, or the language you chose in settings)
- Subscription and payment information (Stripe customer ID, subscription status and period, number of seats, billing cycle). We do not hold card numbers or other payment details; Stripe manages them
- Operation logs and audit logs (who did what and when)
- Where you came from when you signed up (on your first visit to our public website: the referring site, the name of the ad or campaign, the first page you viewed, and the date)
- If you came from an ad on X, the ad click ID (an identifier X adds to ad links; see Section 8)
2. How we use information
We use the information only for the following purposes:
- Showing incoming emails in Slack channels
- Generating reply drafts with AI and saving them as Gmail drafts
- Summarizing articles linked from newsletters (only when turned on for a forwarding rule: we fetch the linked articles, summarize them with AI and post the summaries to Slack)
- Configuring forwarding rules and understanding how the Service is used
- Detecting abuse and keeping the Service secure
- Incident response and customer support for the Service
- Improving the Service (creating statistics that do not identify individuals)
- Understanding and improving how our public website is used, and measuring the effect of our announcements and ads (we count which pages are viewed and where visitors come from, and where people who signed up or subscribed came from; see Section 8)
3. Compliance with the Google API Services User Data Policy (Limited Use)
SuccocoPon’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:
- Data obtained from Google APIs (Gmail and Google Contacts) is used only to provide the user-facing features listed in Section 2 of this Policy.
- We do not transfer or sell this data to third parties, except for showing it in Slack at your instruction and sending it temporarily to our AI model provider (see Section 4).
- We do not use this data for advertising.
- We do not send this data to analytics or advertising tools. We use web analytics only on our public website, not in the app (see Section 8).
- We do not use this data to develop, train, or improve AI or machine-learning models. The OpenAI API we use for AI processing does not use submitted content for training by default, and we additionally use the
store: falsesetting to minimize the history stored by OpenAI. - No human reads this data unless (a) you have given explicit consent, or (b) it is necessary for security investigations, responding to violations, or complying with applicable law. In either case, access follows appropriate procedures and is limited to the minimum necessary.
Data received from Slack, including your instructions to the AI, is likewise not used to train AI or machine-learning models.
4. Service providers (sub-processors)
We use the following external services to provide the Service. Each provider handles user data under its own privacy policy and data processing agreement.
| Provider | Purpose | Location |
|---|---|---|
| Vercel Inc. | Hosting of the Service | United States |
| Neon Inc. | Database of the Service | United States (AWS region) |
| OpenAI, L.L.C. | Generating AI reply drafts and article summaries (not used for training; store: false so exchanges aren't kept by OpenAI, except abuse-monitoring records for up to 30 days) | United States |
| Google LLC | Sign-in and Gmail integration (new-mail notifications / saving drafts) | United States |
| Slack Technologies, LLC | Slack integration | United States |
| Stripe, Inc. | Card payments, invoices and receipts | United States |
5. Retention
- OAuth tokens: until you disconnect. You can disconnect at any time yourself from the “Connections” page of the Service. We delete them at that point and also revoke the access you granted to Google and Slack. The same applies when an organization’s data is deleted.
- Email bodies: never stored permanently. They are held in memory only briefly for posting to Slack and generating AI drafts, and discarded immediately after processing. Attachments and the original HTML of emails are not stored either; they are discarded as soon as they have been posted to Slack.
- Subject and sender of messages: kept as a record of forwarding, for the same period as “forwarding settings and conversation metadata” below. Records of emails that were not delivered by any forwarding rule are deleted after 30 days. We do not store any part of the body (snippets).
- Forwarding settings and conversation metadata: kept while the contract is active, and deleted within 30 days after the contract ends.
- Sender display names and profile-picture URLs: a copy is kept to show icons when posting to Slack, and deleted 90 days after it was last retrieved (messages already posted to Slack are not affected).
- Audit logs: kept for 1 year.
- Where you came from when you signed up, and the X ad click ID: kept until your account is deleted.
- Draft bodies and the back-and-forth of instructions to the AI: kept for editing in Slack and saving to Gmail, and deleted 30 days after the last edit (drafts saved to Gmail remain in your Gmail). Content sent to the AI is kept by OpenAI for up to 30 days for abuse monitoring and then deleted automatically.
- Link lists for article summaries: kept to post the summaries to Slack, and deleted 30 days after creation. The text of fetched articles is not stored.
6. Security measures
- The database, including OAuth tokens, is protected by Neon (Postgres) encryption at rest (AES-256)
- All communication uses HTTPS
- Staff access is limited to what is needed for work, and administrative actions (such as changes to settings and deletions) are recorded in audit logs
- We have appropriate data processing agreements with our service providers
- We have undergone the third-party security assessment (CASA) required by Google
7. Your rights
You may exercise the following rights with respect to the Service:
- Request access to your information
- Request correction of incorrect information
- Request a copy of your information in a portable format
- Disconnect from the Service (revoke OAuth connections; you can do this yourself from the “Connections” page)
- Request deletion of your account and the related data
Please contact us at the address below for these requests. We will generally respond within 30 days.
You can also revoke the Service’s access at any time from your Google account’s third-party app access page.
8. Cookies and data sent to third parties
8.1 Cookies used by the Service
The Service uses authentication cookies to keep you signed in, and cookies to remember your language and time zone choices (up to 1 year).
We also use a cookie (up to 90 days) to remember where you came from on your first visit to our public website (the referring site, the name of the ad or campaign, and the first page you viewed). When you sign up, we save it with your account and use it only to count where people who signed up or subscribed came from. We do not send this information to anyone outside (including Google Analytics).
If you came to our public website from an ad on X, we use a cookie (up to 30 days) to remember the ad click ID (an identifier X adds to ad links) and save it with your account when you sign up. When you sign up and when you make your first payment, we send only this click ID to X (see 8.4).
8.2 Web analytics on our public website
On our public website (www.succocopon.com, including the sign-in page), we use Google Analytics, provided by Google LLC, to understand and improve how the website is used. Google Analytics uses cookies to send the following information to Google.
- Information sent: the URL and title of the pages you view, the referrer (the page or ad you came from), your browser and device type, your approximate region, an identifier stored in a cookie, and your actions on the website (such as scrolling and clicking links)
- Recipient: Google LLC
- Purpose: We use this information as statistics that do not identify individuals, to understand and improve how our public website is used. For how Google uses it, see How Google uses information from sites or apps that use our services.
We do not send information that identifies you, such as your name or email address. We do not use the advertising features of Google Analytics (Google signals and ads personalization).
8.3 Session recordings and heatmaps on our public website
On our public website (excluding the sign-in page), we use Microsoft Clarity, provided by Microsoft Corporation, to make our pages easier to use. Microsoft Clarity uses cookies to send the following information to Microsoft.
- Information sent: your actions on the page (clicks, scrolling and mouse movement), the content shown on the page, the URL of the pages you view, your browser and device type, and an identifier stored in a cookie. The content of input fields and numbers and email addresses shown on the page are masked before sending. The content of the contact page is masked
- Recipient: Microsoft Corporation
- Purpose: We use it to see what is read and clicked, to improve our public website. For how Microsoft uses it, see the Microsoft Privacy Statement
- Retention: 30 days for session recordings and 9 months for heatmaps
8.4 Measuring the results of our ads on X
On our public website (including the sign-in page), we use the X Pixel and the Conversions API, provided by X Corp., to measure how many people who came from our ads on X signed up or subscribed. The X Pixel stores and reads cookies and sends the following information to X. In addition, when someone who came from an ad on X signs up or makes their first payment, our server sends that event and the ad click ID to X.
- Information sent: the URL of the pages you view, the referrer, your browser and device type, your IP address, an identifier stored in a cookie, and the X ad click ID. From our server, we send only the type of event (sign-up or first payment), its date and time, and the ad click ID. We do not send your name or email address
- Recipient: X Corp.
- Purpose: We use it to understand the results of our ads on X (whether people who came from an ad signed up or subscribed). X may use it to measure ad results and to show ads that match the interests of X users. For how X uses it, see the X Privacy Policy
8.5 Not used in the app
We do not use web analytics or ad measurement tools in the app (app.succocopon.com). Information received from Gmail or Slack is never sent to analytics or advertising tools (see Section 3).
8.6 How to opt out
To stop sending information to Google Analytics, use the Google Analytics Opt-out Browser Add-on or block cookies in your browser settings. To stop sending information to Microsoft Clarity, block cookies in your browser settings.
To opt out of interest-based ads from X, turn off "Personalized ads" in your X settings, or use the Digital Advertising Alliance's WebChoices tool (see X Help: Your privacy options for personalized ads). Blocking cookies in your browser settings also stops the X Pixel from sending information. You can still view our public website.
9. Children
The Service is intended for business use and is not intended for use by anyone under 13.
10. Changes to this Policy
We may revise this Policy as the Service changes. We will announce important changes in advance on the Service or by email to your registered address.
11. Contact
For questions about this Policy or data requests, please contact:
STUDIO SPOON Inc.
E-mail: info@succocopon.com
Service URL: https://www.succocopon.com
Effective date: 2026-05-15 / Last updated: 2026-10-07