Privacy Policy | Sakuraseisai Co., Ltd

P01 — Service and operator

Sakuraseisai Co., Ltd. (桜星彩株式会社, the Company) operates AI営業ロープレ｜Sales Roleplay for fictional Japanese/English sales practice in ChatGPT. This addendum covers ordinary practice, explicitly selected OAuth-authenticated personal-scenario functions, and support inquiries. Ordinary practice, feedback, Retry and report export require no Sakuraseisai SaaS sign-in. Personal-scenario functions authenticate an existing Sakuraseisai SaaS account through Clerk OAuth. This does not include the independent AI Sales Coach SaaS's paid, voice or training-management functions. Read this addendum together with the existing website Privacy Policy.

P02 — Information entered into ChatGPT

Scenarios, product information, salesperson and buyer statements, practice conversations and feedback are processed within ChatGPT. OpenAI’s processing, storage, model-improvement use, access and deletion practices depend on the policies applicable to your region, agreement, account settings and service. Practice without a SaaS sign-in does not mean that OpenAI does not process or retain information. Do not enter real customers’ personal information, confidential sales materials, trade secrets, credentials or payment information. Use fictional or appropriately anonymized examples.

P03 — Boundary between the plugin and our systems

Listing, loading and saving personal scenarios use MCP only in response to the user's explicit request. Clerk handles sign-in and OAuth authentication. Our SaaS/MCP backend checks the verified account identifier, allowed scopes and trusted owner binding. We process the necessary account identifier, selected scenario identifiers and definitions, identifiers and outcomes for save requests, approvals and writes, and metadata needed for authentication and operation.

Our backend uses Supabase to read and save scenario definitions. Users do not separately connect or sign in to Supabase. The architecture does not give ChatGPT a database Key or let ChatGPT operate Supabase directly. An OAuth access token authenticates the MCP request; it is separate from a browser sign-in session and database credentials.

Saving creates a new record only. After Prepare previews the request, the owner must approve it in a separate authenticated browser page, and Confirm must actually succeed before a saved result is returned. Chat consent cannot replace that approval. These operations concern the selected scenario definition. Training dialogue, feedback, scores, reports, attachments and training history are not automatically synchronized.

P04 — OpenAI platform and our information processing

Ordinary free practice alone is not designed to invoke our private scenario tools or automatically save conversations to our database. When a user explicitly requests a personal-scenario action, we receive the OAuth-authenticated MCP request within the scope described in P03. OpenAI's platform-side processing, retention, statistics and settings remain governed by the descriptions and policies applicable to the user. We do not make representations about OpenAI's processing on OpenAI's behalf. New uses of information require any necessary notice or separate consent before that use.

P05 — Restrictions on use of training conversations

Without separate explicit consent, the Company does not use sales-training conversations—including conversations or excerpts that a user voluntarily sends to us—for:

training or fine-tuning the Company’s AI models;
developing or improving the Company’s products;
academic research, papers or experimental analysis;
marketing, public examples or demonstrations; or
sharing with other customers.

An ordinary inquiry, privacy-policy acknowledgment or support request is not consent for those separate purposes. The first public release will not provide a consent workflow for those secondary uses. Authorized internal personnel will handle necessary support processing on a minimum-necessary basis. This policy does not change OpenAI’s own data-use rules.

P06 — Word and other reports

A DOCX report is generated and provided in ChatGPT only on an explicit user request and when the actual host environment provides file-generation tools. It may contain the available scenario, dialogue, quotations, feedback and Retry information. The plugin does not automatically transfer reports to a Sakuraseisai storage server. ChatGPT file storage or Library handling is separate from copies you download to your device or a storage location you choose. Manage downloading, sharing, storage and deletion through each relevant service or device.

P07 — Voluntary support inquiries

When you use our contact forms or email, we may receive your name, email address, subject, inquiry text and any conversation excerpts you voluntarily attach. The public support address is info@sakuraseisai.com. Depending on the form configuration, submission date and time, submitting-page URL, source IP address and similar submission information may also be processed. The absence of a field from one language form does not establish that the information is absent from other logs.

We use this information only as necessary to answer the inquiry, investigate a reported fault, and handle reasonable service or security requests. Fault descriptions and general issue categories that do not contain training conversations may be used for necessary maintenance and quality management under the published policy. Using an included training conversation for a purpose listed in P05 requires separate explicit consent. Send the minimum needed explanation with personal and customer information removed.

P08 — Support recipients, retention and deletion

Support inquiries are received at info@sakuraseisai.com through business email services and may be forwarded to another mailbox on the Company’s domain and to a Company business Gmail mailbox. These recipient mailboxes are used for Company business and managed by authorized personnel. Email, attachments, forwarding destinations, backups and system logs are handled according to actual configurations, provider policies, access permissions and applicable law.

We determine retention by the purpose of the inquiry, applicable legal requirements and periodic necessity review. When a purpose for retention ends, we delete or anonymize information subject to legal exceptions and available authority. We do not promise an unverified fixed automatic period, immediate, permanent and synchronized deletion of every copy, or deletion of all data controlled by OpenAI, a user device, a third party or a service provider.

Saved personal-scenario definitions and operational records such as pending requests, approvals and write outcomes are handled by our backend separately from support email. This notice does not promise a fixed number of retention days, automatic deletion when a Pilot ends, or immediate removal of every backup. Contact the channel below about retention and individual handling. An approval expiry or a service access deadline is not a deletion deadline for saved scenarios.

P09 — Your controls and requests

For personal information held by us, use the existing policy’s contact process to request access, correction, suspension of use or deletion as applicable under law. Our process cannot be represented as deleting all OpenAI data or copies on your devices or held by others. ChatGPT conversations, saved files and Memory may require separate management. Consult your actual account controls and OpenAI’s current instructions and exceptions.

Contact: Sakuraseisai Co., Ltd., info@sakuraseisai.com. Use the Japanese contact form or English contact form. We do not promise a fixed number of days for processing requests across systems or for removal from backups or third-party services.

Send personal-scenario access, correction or deletion requests to info@sakuraseisai.com or the existing Japanese/English contact forms. Include the relevant scenario identifier if available; do not send passwords, tokens, cookies, authorization codes or database Keys. We check the necessary identity verification and the handling available to us. This version has no MCP update or delete tool; a chat request alone does not complete an update or deletion. Unlinking, logging out or service closure must not be equated with deletion of saved data.

P10 — External policies, version, effective date and notice

See the OpenAI privacy-policy entry point, terms entry point, Data Controls, chat and file retention and Library. Confirm the version applicable to your region, individual or business agreement and account.

The plugin is intended primarily for professionals seeking to improve their individual sales abilities. The Company does not impose an additional “18+” access restriction for this plugin. Actual eligibility and any minimum age follow the OpenAI Terms of Use, platform policies, and laws applicable where the user is located. Follow applicable requirements when parental permission is required. The Company does not independently verify age and does not actively market the plugin to children under 13. OpenAI determines access, review, and age-related controls for its own platform under its platform rules. This does not give OpenAI final authority to interpret all Company services, the Company’s legal liability, or applicable law.

Document version: 1.1 (Skills + MCP). Effective date: October 19, 2026. Last updated: October 19, 2026. Changes will be posted on this page. Where applicable law requires notice, notice will be provided through an appropriate method.