Privacy Policy
Sunagawa (hereinafter "the Developer") hereby establishes this Privacy Policy (hereinafter "this Policy") regarding the handling of User personal information in connection with the iOS/iPadOS application "Logo Maker" (hereinafter "the App") and all related websites and services (hereinafter collectively "the Service").
The Developer respects User privacy and complies with the Act on the Protection of Personal Information (Japan) and other applicable laws and guidelines.
Article 1 (Fundamental Policy on Data Collection)
The App is designed to operate as a "local-first, serverless" application.
[Fundamental Principle] All design data created by Users within the App, placed images, entered text, project names, and User Content are processed and stored entirely within the User's device (local storage). The Developer does not collect, transmit, or store any of this content on external servers.
The App does not operate any proprietary backend servers. Templates, fonts, and assets are all bundled within the App, and no network communication is performed for content retrieval.
Article 2 (Classification of Collected Information and Purposes of Use)
The Developer collects and uses the following information only within the scope of the purposes described in this article.
2.1 Information Processed Locally on the Device (Not Sent to Servers)
The following information is processed and stored solely on the User's device and is not transmitted to any external party, including the Developer.
| Type of Information | Collection Method / Processing |
|---|---|
| Design data (text, shapes, layer structure, color settings, etc.) | Saved in local storage as .logomaker package files. Contains JSON document data, preview images (.jpg), and image assets. |
| User-imported images | Images selected through PhotosPicker (iOS standard) are copied into the project package's assets/ directory. Large images are downsampled on-device during import. |
| Freehand drawing stroke data | Strokes recorded by PencilKit are converted to transparent PNG image layers upon completion and stored locally. The stroke data itself is not retained. |
| Project management metadata | Project names, creation dates, folder structure, and favorites are stored locally as a library-index.json file. |
| App settings (language selection, etc.) | App preferences such as display language (Japanese/English) are saved in UserDefaults. |
2.2 Information Processed Through Third Parties
The following information is processed through third parties necessary for providing the Service.
(a) Subscription Payment Information
The following information is processed in connection with the purchase, renewal, and restoration of the paid service "Logo Maker Pro":
- App Store transaction IDs, purchase dates, subscription status, and expiration dates
- Anonymous app user IDs assigned by RevenueCat
- Subscription plan type (monthly/annual) and renewal status
Important: Payment information such as credit card numbers, bank account details, and Apple ID passwords is processed directly by Apple and payment processors. The Developer does not access, view, or store any such information.
[Purpose of Use] Verification of subscription status, feature unlock control, and purchase restoration processing.
(b) Contact Information
When Users contact the Developer through Google Forms or other contact channels, the following information is collected based on User input:
- Email address
- Name (nickname acceptable)
- Inquiry content (bug reports, feature requests, questions, etc.)
- Optionally attached screenshots or other images
[Purpose of Use] Used solely for investigating and responding to inquiries, reproducing and fixing bugs, and improving the Service.
2.3 Anonymous Analytics and Crash Data (Planned)
To improve App quality and enable early detection of issues, a future update may introduce a mechanism for collecting anonymous statistical information that cannot identify specific individuals. If introduced, the following information may be collected:
- Device model name, OS version, and App version
- Crash logs (stack traces and error information from abnormal App terminations)
- Anonymous feature usage statistics (e.g., screen transition frequency, feature usage counts, export format selection trends)
[Guaranteed Non-Collection] Even with the introduction of analytics features, User Content-related information — including design content, entered text, imported images, and project names — will never be collected.
[Purpose of Use] Crash and bug fixes, UX improvement, and prioritization analysis for new features.
Article 3 (Device Features and Permissions)
The App may use the following device permissions to provide its features. All permissions are requested through iOS system dialogs only when needed, and Users can change permissions at any time through device "Settings."
3.1 Photo Library Access
Used when importing images from the device as "image layers" in the App.
- Image import: Uses iOS standard
PhotosPicker(PHPickerViewController). This mechanism provides the App access only to images selected by the User, without accessing the entire photo library. - Export: Designs are exported through the iOS share sheet (
UIActivityViewController). If the User chooses a destination such as Photos, iOS may request the permission needed for that save. The App does not obtain ongoing access to the entire photo library.
Selected images and exported files are processed locally on the device and are not transmitted to external servers.
3.2 File System (Document Storage)
Project files (.logomaker packages) are stored in the Documents directory within the App's sandbox. File writing uses an atomic replacement method — writing to a temporary directory first, then replacing the entire package — to reduce the risk of file corruption from crashes during save operations.
Article 4 (Advertising and Tracking)
- The App does not display advertisements. No advertising network SDKs are integrated.
- The App does not request App Tracking Transparency (ATT) permission. Cross-app tracking (tracking User behavior across other apps or websites) is not performed.
- The App does not collect or use the IDFA (Identifier for Advertisers).
Article 5 (Cookies and Web Tracking Technologies)
The App is a native iOS application and does not use cookies, web beacons, pixel tags, or other web tracking technologies.
This official website (including this page) consists of static HTML files and does not set or read cookies. However, the linked Google Forms contact page may use cookies in accordance with Google's Privacy Policy.
Article 6 (Third-Party SDKs and Tools)
The App and Service use the following third-party tools necessary for service delivery. Each tool processes data in accordance with its own privacy policy.
| Tool | Provider | Purpose | Information Processed |
|---|---|---|---|
| RevenueCat | RevenueCat, Inc. | Subscription verification, management, and purchase restoration | Anonymous app user IDs, App Store transaction information, subscription status |
| StoreKit 2 | Apple Inc. | App Store payment processing | Purchase information linked to Apple ID (processed directly by Apple; the Developer does not access payment information) |
| Google Forms | Google LLC | Contact form submission and management | User-provided email address, name, and inquiry content |
Please refer to each third party's privacy policy for details:
Future updates may introduce third-party SDKs for quality management and crash monitoring (such as TelemetryDeck or Sentry). If introduced, this Policy will be updated to include the name, processed information, and purpose of use of such tools.
Article 7 (Disclosure of Personal Information to Third Parties)
The Developer will not provide or disclose collected personal information to third parties except in the following cases:
- With the User's consent
- When required by law, or when requested by a court, police, prosecutors, or other public authority
- When necessary for the protection of life, bodily safety, or property, and obtaining the individual's consent is difficult
- When particularly necessary for improving public health or promoting the sound development of children
- When necessary to cooperate with a national or local government body or its delegate in executing affairs prescribed by law
- When data processing is entrusted to the aforementioned third-party tools (RevenueCat, Google Forms, etc.) within the scope of the purposes stated in this Policy
Article 8 (Data Retention and Deletion)
- Locally stored data: Project data, app settings, and other device data are automatically deleted by the device OS when the User deletes (uninstalls) the App.
- Contact-acquired information: Email addresses, inquiry content, and other information obtained through inquiries will be deleted using secure methods within a reasonable period (generally within 6 months of issue resolution). However, this does not apply where retention is required by law.
- RevenueCat-stored information: Subscription information is retained in accordance with RevenueCat's data retention policy. For details, see the RevenueCat Privacy Policy.
Article 9 (Security Measures)
The Developer implements appropriate security measures to prevent leakage, loss, or damage of collected information, including:
- Restricting access to contact form response data to the Developer only
- Isolating Project data within the App's device sandbox
- Entrusting subscription information processing to RevenueCat and Apple's encrypted infrastructure
- Promptly deleting personal information that is no longer needed
Article 10 (Right to Request Disclosure, Correction, and Suspension of Use)
- Users may request disclosure, correction, addition, deletion, suspension of use, or cessation of third-party provision of personal information held by the Developer, in accordance with the Act on the Protection of Personal Information (Japan).
- To make such requests, please contact us through the contact channel at the end of this Policy. After identity verification, we will respond within a reasonable period.
- However, information stored only locally on the User's device (such as Project data) cannot be accessed by the Developer and is therefore excluded from disclosure, correction, or deletion requests. Users should manage such data themselves through the App's project management features or by deleting the App.
Article 11 (Children's Privacy)
The App is not targeted at any specific age group and is available for Users of all ages. The Developer does not intentionally collect personal information from children under the age of 13.
If it becomes known that a child under 13 has submitted personal information (such as through the contact form) to the Developer without parental consent, the Developer will promptly take measures to delete the relevant information.
Article 12 (International Data Transfers)
Information provided through the contact form (Google Forms) and subscription information processed through RevenueCat may be processed and stored on servers located outside Japan. The respective service providers (Google LLC, RevenueCat, Inc.) implement appropriate data protection measures.
Users accessing the Service from outside Japan should be aware that data protection standards different from those in their region of residence may apply.
Article 13 (Consistency with Apple's App Privacy — Nutrition Label)
The "App Privacy" display (Nutrition Label) shown on the App Store is configured based on this Policy. If analytics SDKs or other tools are introduced in future updates, both the App Store Nutrition Label and this Policy will be updated simultaneously to maintain consistency.
Additionally, the App will maintain a privacy manifest (PrivacyInfo.xcprivacy) as required by Apple for App Store submission and corresponding to the SDKs and APIs used.
Article 14 (Future Cloud Sync Features)
A future update to the App may introduce a cloud sync feature using iCloud (CloudKit). If provided, the feature will operate based on the following principles:
- Synced data (project files, etc.) will be stored end-to-end in iCloud storage associated with the User's Apple ID, and the Developer will not access its contents.
- Cloud sync will be optional, and Users will be able to choose to keep data local only.
- When cloud sync is introduced, this Policy will be updated to describe the scope of data handled and the processing methods.
Article 15 (Amendments to This Policy)
- The Developer may amend this Policy in connection with App updates, changes to related services, introduction of new third-party SDKs, or amendments to applicable laws.
- For significant changes (such as the introduction of new data collection or additional third-party data recipients), the Developer will make reasonable efforts to provide advance notice through in-app notifications or website postings.
- Amended Privacy Policies shall take effect upon posting on this website. The last updated date is indicated at the top of this page.
Article 16 (Contact)
For questions about this Policy, inquiries about personal information handling, or requests for disclosure, correction, or suspension of use, please contact us through the following:
We will respond within a reasonable period after receiving your inquiry.