Processors and Service Providers
Last updated: (to be confirmed at release)
In accordance with Section 11 of the Terms of Use and Section 6 of the Privacy Policy, this page lists the processors and service providers used to operate the Service. For transparency, we also list cloud providers whose role does not involve handling the contents of personal data.
Current processors and service providers
| Provider | Purpose | Processing location | Transfer mechanism |
|---|---|---|---|
| Amazon Web Services (Amazon Web Services Japan G.K.) | Core infrastructure of the Service: delivery of the official website and shared post images (Amazon S3 + Amazon CloudFront), execution of the post API (Amazon API Gateway + AWS Lambda), storage of post data, consent logs and deletion logs (Amazon DynamoDB), operator notifications for deletion requests and inquiries (Amazon SNS), log and metric monitoring (Amazon CloudWatch), and secret management (AWS Secrets Manager) | Tokyo region (ap-northeast-1); CDN is global | The AWS Data Processing Addendum (DPA), with the EU Standard Contractual Clauses (SCC) made available by AWS for transfers from the European Economic Area (EEA) and the United Kingdom |
| GitHub, Inc. (Microsoft Corporation) | Source control and CI/CD pipeline. During website builds, published post data (references to anonymized images and post attributes) is fetched to generate static pages | Global | The GitHub Data Protection Addendum (DPA), with the EU Standard Contractual Clauses (SCC) made available by Microsoft / GitHub for EEA / UK transfers |
Planned processors and service providers
We will add the providers below to this page when we deploy them. Notice of changes follows the "Notice of changes" section below.
| Provider | Purpose | Processing location | Transfer mechanism |
|---|---|---|---|
| Apple Inc. (iCloud key-value storage) | Storing the deletion secret (a secret value that lets you keep the right to delete your posts after switching devices) in your own iCloud; to be added when the iOS app is released | Apple data centers (including the United States) | Apple's Standard Contractual Clauses (SCC) and data processing terms |
| Apple Inc. (App Store / StoreKit, App Attest) | In-app purchase processing and device integrity verification (App Attest); to be added when the iOS app is released | Apple data centers (including the United States) | Apple's Standard Contractual Clauses (SCC) and data processing terms |
| Apple Inc. (iCloud / CloudKit) | Storing a pseudonymous identifier (owner_id) in the user's iCloud private database so that ownership and the right to delete shared Posts can be carried across devices; to be added together with the iOS owner_id continuity implementation | Apple data centers (including the United States) | Apple's Standard Contractual Clauses (SCC) and data processing terms |
| Apple Inc. (Sign in with Apple) | Optional sign-in for owner identification (we receive only the pseudonymous identifier (sub) issued by Apple, not the Apple ID itself or your name); to be added together with the iOS owner_id continuity implementation | Apple data centers (including the United States) | Apple's Standard Contractual Clauses (SCC) and data processing terms |
| Google LLC (Google Analytics 4) | Web analytics for the official website; the tag fires only after Cookie consent has been obtained | Global | The Google Ads Data Processing Terms (DPA) and the EU Standard Contractual Clauses (SCC) made available by Google. IP anonymization will be enabled |
| Google LLC (Firebase Crashlytics) | iOS app crash diagnostics (stack traces, device model, OS version, and similar diagnostic information). Post data, mouth-area images, and owner_id are not sent; to be added when the iOS app is released | Global | The Google data processing terms (DPA) and the EU Standard Contractual Clauses (SCC) made available by Google |
Providers under consideration (no current plan to adopt)
We may consider these as user count or scope grows. If adopted, we will add them to this page following the "Notice of changes" section below.
- Backend-side error aggregation SaaS (for example, Sentry / Datadog). For now, the server side uses Amazon CloudWatch and iOS app crashes use Firebase Crashlytics
How providers are managed
As set out in Section 11 of the Terms of Use, the Service Provider secures the necessary conditions — including no use beyond the purpose of the engagement, confidentiality, appropriate safeguards and management of further delegation — by reviewing and entering into the data processing agreements (DPA) and terms made available by each provider.
Notice of changes
Where a change constitutes a material change to how post data is handled (such as adding a provider that processes a new category of personal data), we will give at least thirty (30) days' notice through the Service and the official website in accordance with Section 8 of the Terms of Use. Other changes (such as additional services within the same provider or renames) are recorded in the change log on this page.
Change log
| Date | Change |
|---|---|
| (to be confirmed at release) | Initial publication (AWS / GitHub listed; Apple / Google Analytics 4 listed as planned) |