unkrypt Amend — Privacy Policy
Version 1.2 — 25 October 2026.
Effective date: 25 October 2026
Operator: Ryohei Mizuno, trading as unkrypt, at 3-7-3 Azuma, Kashiwa-shi, Chiba 277-0014, Japan (see Operator notice). Legal form: sole proprietor; unkrypt is a trading name.
Privacy contact: support@unkrypt.com. Time zone: Asia/Tokyo (JST). Email is accepted at any time; ordinary support has no fixed hours or guaranteed response time. Privacy questions receive reasonably prompt attention and statutory response deadlines still apply.
Privacy responsibility: Ryohei Mizuno. The initial offering excludes EEA/UK businesses and targeting/monitoring of individuals there. No EEA/UK representative is appointed for this offering. We do not conduct large-scale sensitive-data processing or systematic monitoring as a core activity; we have not designated a statutory DPO. We reassess these positions before changing the scope; statutory rights and duties remain applicable where the law requires them.
1. Scope and our role
This Policy explains personal-data processing in unkrypt Amend and related support. For our account administration, security, business correspondence and legal obligations, we determine the purposes of processing and act as controller or equivalent business operator. For personal data a merchant entrusts to us in documents and store records, we normally process it on the merchant’s instructions as processor, service provider or equivalent entrusted operator. The actual relationship and applicable law determine these roles; labels do not override them.
If you are a supplier contact, merchant employee or another person whose data appears in a merchant document, contact that merchant first where it controls the processing. You may also contact us and we will identify the responsible party where possible and assist appropriately. Shopify’s own services are governed by its policies.
2. Data we process and where it comes from
| Category | Examples and source |
|---|---|
| Store and authorization | Shopify shop domain and identifiers, store settings including business country and its verification time, scopes, API access and refresh credentials, authenticated session information; supplied by Shopify and the merchant |
| Contract and notices | Legal business name and service-notice email submitted by the merchant, authenticated acceptance actor, regional eligibility confirmation, accepted document snapshot, version, content hash and time; used to administer and evidence the agreement and send necessary service or legal notices, not marketing |
| Authorized staff | Staff identifier used for actions; Shopify session fields may include associated staff name, email or account details. Session content is encrypted when stored |
| Product and supplier records | Product/variant identifiers, SKU, descriptions, image references, reference and actual unit costs, selling-price proposals, purchase/invoice references, receipt allocations, adjustments, relevant inventory information, mappings, supplier names and source URLs |
| Documents and derived content | Uploaded or fetched originals, filenames, extracted text/tables/notes, OCR results, coordinates, corrected values, correction reasons, dates and audit history. These may include supplier contact names, business contact details, sole-trader information, or other personal data present in the document |
| Usage and billing status | Plan/subscription status, billing reference identifiers, processing counts and limits; we do not collect payment-card details through the app |
| Technical and support records | Authentication events, operation/error records, support-grant metadata and correspondence. Our infrastructure and platform providers may process IP addresses, browser/device information and request logs to operate and secure their services |
The current app does not request Shopify customer or order read scopes. That does not mean we process no personal data: documents, staff sessions and support messages may contain it. Do not upload unnecessary customer lists, payment credentials, identity documents, health records or other sensitive information. Tell us if such information was included unintentionally so that we can assess appropriate handling with the merchant.
3. Purposes and legal grounds
We use data to authenticate stores and users; read and structure supplier documents; prepare and carry out permitted product/reference-cost and separately approved selling-price changes, purchase evidence and receipt matching; remember mappings and settings; maintain records and exports; manage subscriptions and usage; provide requested support; prevent abuse; troubleshoot faults; handle rights requests; and comply with legal obligations or resolve disputes.
Where a legal-basis framework such as the GDPR applies to our controller processing, we rely, as appropriate, on performance of a contract with the individual, legitimate interests in providing and securing a business service and communicating with its representatives after considering their rights, and legal obligations. A contract with an employer is not automatically a contractual basis for all processing of its employees. We use consent only where it is required or appropriately chosen, and provide a way to withdraw it. Withdrawal does not affect prior lawful processing. Entrusted document processing follows the merchant’s lawful instructions and basis under the applicable DPA.
We do not use merchant documents to train general-purpose AI models. External OCR is optional and limited to price lists containing no personal information. Before confirming each file, inspect every page and remove personal names, individual contact details, signatures and sole-trader identifiers. Confirm that you are authorized to transmit the remaining content to Z.AI. The confirmation is tied to that file; automated source downloads do not provide it. We do not automatically anonymize documents. Without confirmation, local CSV, Excel and readable-PDF parsing remains available; files requiring OCR are held for manual recovery without transmission to Z.AI. Purchase documents and files with personal information must use local parsing or manual entry. If vendor conditions become unsuitable, we may stop external OCR and retain local/manual workflows; a material loss of agreed functionality is handled under the notice, cancellation and unused-fee provisions, not an unconditional disclaimer. CSV, Excel and directly readable PDFs are parsed on our Railway infrastructure, not solely on your device. Z.AI receives confirmed image/page content; it does not receive Shopify credentials. OCR results require review. We do not sell personal data or share it for cross-context behavioral advertising; the current app has no advertising analytics integration.
The per-file OCR confirmation also records the exact authorization and provider-limit notice displayed, alongside its policy version, file hash, actor and time. Non-personal prices can still be confidential: supplier permissions and disclosure restrictions remain relevant. Our notice and the merchant’s instruction do not replace safeguards or permissions required by law. See Terms section 3.1.
4. Access and recipients
Access is limited to authorized people and providers with a service, security, support or legal need. Categories include Shopify for authentication, store APIs and billing; contracted hosting, database, storage, backup, network and communications providers; and professional advisers where necessary and subject to confidentiality. We may disclose information where legally required or necessary to establish or defend rights, subject to applicable safeguards. A business succession must preserve applicable protections and required notice.
A merchant can authorize time-limited, document-specific support and revoke it at any time. The app shows a non-secret reference ID; that ID alone cannot access data. An authorized infrastructure operator uses private administrative access to review only the permitted extracted content, corrections and proposal while the grant is active, with an access audit record. This support view does not expose Shopify credentials or the original file. Do not email support tokens. Separately, infrastructure administration may require controlled access for security or legal duties.
Production hosting and backup services are provided by Railway under an executed DPA. Optional Z.AI OCR is restricted to non-personal price lists. Details and actual processing locations are in Service providers and processing locations. Support email is sent and received through Google Workspace Gmail. support@unkrypt.com is an alias of the operator’s business account, mizunoryohei@unkrypt.com; either business address may be used for replies. Only minimal direct business correspondence is permitted: contact details, store domain, non-secret support reference, time and a description without document content. Do not email originals, tables, screenshots, exports, third-party personal data or credentials. Google Workspace is used only for this limited correspondence, under the applicable Workspace terms. Email is not an authorized intake or support channel for entrusted documents. Unsolicited content is restricted, assessed and deleted under the applicable duties. Library authors do not receive content merely because their code is used.
5. International processing
Configured app, database, original-file, backup and deletion-journal resources are in Singapore; operator access is from Japan. Railway and its onward providers can process data in the United States and other disclosed regions. We do not promise single-country processing. Our executed Railway DPA governs entrusted-data processing and includes applicable transfer safeguards. Before any additional restricted transfer, we assess and establish the necessary mechanism and safeguards. The initial Service is available only to businesses established and operating outside the European Economic Area (EEA) and United Kingdom. You must confirm this eligibility and notify us before it changes. Shopify business-country checks and listing restrictions support this limit; a different currency, VPN or address entered to bypass it does not establish eligibility. Do not use the Service for personal-data processing related to offering goods or services to, or monitoring, people in those regions. Non-personal supplier price lists can originate elsewhere. We do not target individuals in the EEA/UK or monitor storefront visitors. A regional restriction does not remove any statutory rights that otherwise apply. If availability changes, new processing stops; exports, cancellation assistance and applicable unused-fee remedies remain available.
Japan-related adequacy arrangements do not automatically cover every provider, onward transfer or category of processing. Details of the applicable safeguards and a copy or summary, with necessary confidential information removed, may be requested at the privacy contact. Any legally required consent, representative or local restriction must be addressed before the affected processing begins.
6. Retention and deletion
We retain data only for the disclosed purpose and period, subject to legal obligations and justified, limited holds. The following schedule applies to originals and other copies according to their type.
| Data | Retention rule |
|---|---|
| Original documents | A retention job uses the shorter of the store setting and applicable plan limit; the default is 90 days and the store setting can be 7–365 days, subject to the plan. Documents needed by queued or unfinished processing may be retained longer. The current implementation allows up to 30 additional days for unfinished work, then cancels it and deletes the original after any short active-processing lease ends. This is the configured production limit |
| Extracted records, mappings, corrections and audit history | Kept while the app remains installed and needed for the merchant workflow; there is no independent age-based purge of these records. Uninstallation disables processing immediately. Store redaction deletes active records; a seven-day uninstallation backstop also purges them. Valid earlier deletion instructions are handled through verified support. Deleting an original alone does not delete derived records |
| Shopify sessions and credentials | Removed from the active session store when the uninstall or shop-deletion event is processed. Tokens may also expire or be revoked through Shopify. Backup handling must follow the separate schedule |
| Store deletion | A processed Shopify shop-deletion request removes tenant business records and original files in the active environment. If the store remains uninstalled, a retention job schedules active business records and original files for deletion after 7 days even if the shop-deletion webhook is absent. Reinstallation before that deletion cancels the scheduled purge. Backups follow the separate schedule; this is not an immediate deletion promise for all copies. Independent verified rights requests are also handled as required by law |
| Technical logs, support correspondence, grant metadata and billing records | Normal application access logs omit URL query strings, request bodies and document identifiers; Railway Pro currently exposes a 30-day log window, which is not a guarantee of permanent deletion by the provider. Ordinary support correspondence is manually deleted 90 days after the final response, excluding justified legal holds. Entrusted content received accidentally follows the shorter applicable deletion deadline. Support-grant metadata and in-app billing/usage records follow the store-record deletion rules above. Separate records required for accounting or legal compliance are restricted to that purpose for the applicable statutory period |
| Backups | Production app/database volume backups are configured daily with six-day retention. Recovery uses a separate, current deletion journal so that deleted records are not restored. The journal contains a store-domain hash and deletion time, not document content, and is retained while relevant recoverable copies may remain. Backup copies and any manual support/recovery copies remain subject to applicable deletion obligations; this does not describe unlimited retention or a certified recovery SLA |
Where a specific law requires retention, we restrict the retained data to that purpose and delete it when the requirement ends. We do not keep all documents indefinitely merely because some billing or legal records must be retained. A legitimate dispute hold must be proportionate, recorded and reviewed.
7. Security and incidents
Controls include tenant checks, authenticated original/export access, AES-256-GCM encryption of stored Shopify sessions, limited and revocable support grants, HTTPS and private database networking, input validation, minimal operational logs, and daily six-day backups. Railway’s executed DPA describes database encryption at rest and provider access/security controls. The app does not provide end-to-end encryption with keys held only by the merchant. See the security schedule in the DPA. These controls reduce risk without guaranteeing absolute security.
We maintain and review the stated hosting, access, recovery and incident procedures. If we discover a personal-data breach, we will investigate, mitigate and provide notifications and assistance required by law and the DPA without undue delay. We do not wait for complete certainty about every detail before making a notification that is already legally due.
8. Your choices and rights
Depending on applicable law and our role, you may request access or disclosure, correction, deletion, restriction, portability, information about recipients or transfers, or object to certain processing. Where processing relies on consent, you may withdraw it. Applicable rights to opt out of sale, sharing, targeted advertising or certain sensitive-data uses are preserved; our current service does not undertake sale or advertising sharing. We do not make decisions solely by automated processing that produce legal or similarly significant effects about individuals; product/reference-cost automation concerns merchant records.
Send requests to support@unkrypt.com, describing the relationship and data concerned without sending unnecessary identity documents. We use proportionate verification, respect authorized-agent rights where applicable, and respond within applicable statutory deadlines. If we decline or limit a request, we will explain lawful grounds and available review or appeal routes where required. We will not discriminate for exercising protected rights.
For entrusted merchant data, we assist the merchant and do not independently alter its records without instructions unless law requires it. Contacting us still enables routing and assistance; the absence of a Shopify customer API record does not by itself settle a request about uploaded documents. You may complain to the competent authority, including Japan’s Personal Information Protection Commission, an applicable EEA supervisory authority, the UK ICO or the relevant authority in your jurisdiction. Contract terms do not restrict that right.
9. Browser technologies and children
The app and Shopify use authentication and other necessary browser mechanisms to maintain access and protect sessions. The app code currently has no advertising-cookie integration. Hosting, Shopify and other independently provided services may use their own technologies. The embedded app uses Shopify App Bridge session tokens for authenticated requests. The installed Shopify SDK may use shopify_app_state and its signature cookie for a fallback OAuth flow, with a one-minute state expiry; this protects the authentication callback. Our app has no application-defined advertising cookies or persistent browser storage for supplier documents. Shopify-admin cookies are controlled by Shopify. Any optional tracking added later requires a separate assessment and applicable consent before activation.
The Service is intended for authorized business users and does not target children. If we learn that a child’s information was inappropriately collected, we will assess and address it under applicable law and, for entrusted data, with the merchant.
10. Changes and contact
We will publish the effective date and give appropriate advance notice of material changes. Where a change requires consent or another legal step, updating this page alone is not sufficient. The English and Japanese versions are intended to convey the same information; translation discrepancies do not reduce statutory rights.
Contact support@unkrypt.com, or write to Ryohei Mizuno, 3-7-3 Azuma, Kashiwa-shi, Chiba 277-0014, Japan (see Operator notice). Version: 1.0.