Japan sales terms · Published September 29, 2026. Sales are not yet open.
ONEAORA Privacy Policy
Version 1.0-jp-20260929
Scope: VELORA v1.0.0 / LUMINA v1.1.0, each JPY ¥5,980 including tax, one-time payment. These conditions apply to sales to customers located in Japan. Overseas / EU purchases are not accepted. They do not apply to ONEAORA Jobs or external shops.
Site inquiries
The Contact form collects your name, email address, optional company name, inquiry category and message to respond, make necessary contact and prevent abuse or spam. Contact messages use Resend; the external-processing, retention and rights provisions below apply. External linked sites follow their own policies.
1. Operator and contact
The operator responsible for personal information is 髙岡 優子, trading under the ONEAORA brand. Contact support@mail.oneaora.com. Operator information, including the business address, will be provided without delay upon request. Requests for a purchaser's own order information are distinct from requests for seller information before purchase. A seller-information request does not require a purchase, registration or identity document.
2. Information and purposes
| Information | Purpose |
|---|---|
| Purchase email, order, product, version, price, currency, payment status, Stripe payment identifiers and first payment-confirmation timestamp | Verify payment, supply products, manage transactions, handle refunds/support and prevent duplicate processing |
| Purchase conditions and consent records, applicable policy versions and snapshots or hashes | Establish the conditions presented at purchase and handle inquiries/disputes |
| Declared country, explicit Japan confirmation, confirmation time and Stripe billing country when available | Check eligibility for Japan sales; distinguish declaration from billing information. Neither is treated as conclusive proof of tax residence |
| Entitlements; access-token identifiers/hashes, issuance, expiry, first use, revocation and reissue records | Secure purchase access, authorization, reissue and abuse prevention |
| Email recipients, contents and delivery status; Store outbox state, attempts, send times, provider identifiers and limited error information | Purchase instructions, reissue, replies and fault resolution. Not storing message bodies in the Store DB is distinct from email-provider storage and necessary transaction-evidence retention |
| Inquiry, refund and seller-disclosure requests, receipt and response records | Respond, verify relevant information and manage cases |
| Latest file-URL issuance timestamp for each entitlement and product file | Investigate delivery issues and assist with repeat access and inquiries |
ONEAORA does not store full card numbers or CVCs in the Store DB. Card details are entered in Stripe's payment interface. Stripe may process names and billing information, and the ONEAORA server may receive them in responses; the current Store DB does not persist full names or postal addresses. Do not send card secrets, passwords or private keys in inquiries.
First use of purchase access or issuance of a file URL does not mean the file was saved on the purchaser's device. Absence of a record does not prove that no download occurred, and records alone will not automatically determine refusal of a refund.
3. File-URL issuance records
For each entitlement and product file, we record the latest time a file URL was successfully generated after authentication and authorization (download_access_issued_at). Repeat issuance updates that same pair; no issuance history or count is added. This is a server-side record after URL generation, not proof of response receipt, completed transfer from R2 or saving on a device. A record may exist even if the response never reaches the purchaser. A missing record is treated as unknown, not as proof of non-download.
No IP address, device fingerprint, browsing history, advertising identifier, complete signed URL or raw purchase token is added to this record. It is not used for behavioral analysis or advertising outside purchase/delivery assistance. First or last completed-download times and download counts are not inferred or recorded.
4. External services and international processing
The planned sales architecture uses Stripe for payments, Neon for the order database, Cloudflare R2 for private product files and delivery, Resend for transactional email, and Vercel for hosting/server execution. Existing support-operation records describe Cloudflare Email Routing, an operator-managed Gmail inbox and an authenticated reply path. Email providers process recipients, contents and purchase links where relevant. Product files in R2 do not contain the order database or purchaser email addresses.
Providers may process connection information, IP addresses and operational/security logs separately from the application's minimal records. Processing or storage solely in Japan is not guaranteed. Processing on ONEAORA's instructions is distinguished from independent provider processing, such as payment fraud prevention and legal compliance. International processing is managed on the applicable legal basis, with review and ongoing management of processing countries, subprocessors, safeguards and required information disclosures. Purchase is not treated as blanket consent to overseas disclosure.
No sales advertising-tracking addition was found in the reviewed site code. This does not mean that external services have no cookies or logs. Purchase is not treated as consent to marketing messages.
5. Retention, security and rights
Information is retained only to the extent and for the period needed for supply, accounting/legal records, support, refunds, disputes and other stated purposes. The baseline operation is a monthly necessity review by 髙岡 優子. Retention of orders/entitlements is distinguished from supplementary file-URL issuance timestamps. Neither the 14-day refund-request period nor access expiry is a deletion deadline. Unneeded information without a legal hold or continuing purpose will be deleted appropriately or rendered non-reidentifiable. Hashing alone is not treated as anonymization.
Original electronic transaction records that must be retained as evidence are held in restricted private storage. Mailboxes, databases, providers and backups have separate retention arrangements; immediate deletion of every copy is not guaranteed. The necessity of file-URL issuance timestamps is reviewed monthly, and unnecessary records are deleted for the relevant entitlement and product file. Reasons for continued retention, such as support or a dispute, are managed with restricted access. An automatic deletion deadline is not represented as implemented.
The architecture uses a dedicated database, access controls, signature verification, private storage, short-lived URLs, token hashes and suppression of secrets in logs, together with provider supervision and incident-response arrangements. Requests for notification of purposes, access, correction, deletion or suspension of use under applicable law can be sent to the contact above. Necessary and proportionate identity checks apply. Reasons will be explained where information must be retained or another part of a request cannot be fulfilled under applicable law.
6. Updates
Material changes are reflected after reviewing applicable notice and consent requirements. Conditions applicable at purchase remain traceable through that purchase record.