Last updated: 2026-10-12
Privacy Policy
Last updated: October 7, 2026
Overview
MiDiccio is a local, personal vocabulary learning app. This policy explains how the app collects, uses, and protects personal data.
1. Data Collection
1.1 Data Stored (User-provided and Automatically Recorded)
Following the principle of minimal data collection, only the following data is stored:
| Data Type | Collection Method | Purpose | Storage |
|---|---|---|---|
| Learned terms and meanings | User input | Learning database management | Hive (local storage) |
| Notes | User input | Supplemental context for learning | Hive (local storage) |
| Tags | User input | Vocabulary categorization and search | Hive (local storage) |
| Metadata (creation time) | Automatically recorded | Learning history management | Hive (local storage) |
1.2 Data We Do Not Collect
We do not collect any of the following:
- ❌ Personally identifiable information such as name, address, or phone number
- ❌ User profile or authentication credentials (no local account/auth)
- ❌ Location information
- ❌ Device IDs (including analytics use)
- ❌ Learning behavior analytics (access frequency, study time, etc.)
- ❌ Cookies or tracking data
2. Data Storage
2.1 Local Storage (On Device)
All learning data is stored in secure local storage on your device.
- Technical method: Hive local persistence
- Location: iOS/Android app sandbox
- Owner: User (removed automatically when the app is uninstalled)
2.2 Cloud Sync
In the current version, cloud sync runs at the following timing:
| Platform | Destination | Status |
|---|---|---|
| iOS | iCloud (CloudKit) | ✅ Implemented (manual + lightweight auto-sync) |
| Android | Google Drive (AppData) | ✅ Implemented (manual + lightweight auto-sync) |
Important:
- While cloud sync is turned on, the app syncs automatically at times such as when words are saved or deleted and when you return to the app. You can also run sync manually
- While cloud sync is turned off, the app does not send or receive data to or from the cloud, whether manually or automatically
- Network transfer occurs only when a sync execution runs (to iCloud on iOS, Google Drive on Android)
2.3 Data Transfer Security
| Item | Method | Status |
|---|---|---|
| Local on-device storage | OS sandbox / device encryption / screen lock | ✅ Automatic (iOS/Android OS) |
| Android Device ↔ Google Drive | SSL/TLS | ✅ Google API |
| iOS Device ↔ iCloud | SSL/TLS | ✅ Apple CloudKit |
: Locally stored data is protected at the OS level via sandboxing, device encryption, and lock-screen protections.
: In the current version, cloud transfer occurs only when sync executes, either by manual sync or lightweight auto-sync triggers.
3. Data Sharing
3.1 Sharing with Third Parties
We do not share personal data with third parties.
Cloud sync transfers data only to the user's own iCloud or Google Drive. The developer has no access to any user data.
3.2 Cloud Provider Privacy Policies
When cloud sync is used, the following privacy policies also apply:
- Google Drive (Android): Google Privacy Policy
- iCloud (iOS): Apple Privacy Policy
MiDiccio integrates these services as a licensee and does not perform secondary data usage.
3.3 Purchase Information
MiDiccio Premium (one-time purchase) is purchased through the App Store (iOS) or Google Play (Android), and payment information (such as credit card numbers) is managed by Apple / Google. The developer does not collect or store the purchaser's personal information such as name or email address within the app.
- iOS: Through App Store Connect, the developer cannot obtain information that identifies individual purchasers (only aggregated sales data is available).
- Android: Due to how Google Play works, for the purpose of handling refunds and order management, the developer may be able to see the purchaser's email address, etc. in the Google Play Console's "Order management" screen.
The respective privacy policies for these payment platforms also apply (see 3.2).
4. User Rights
4.1 Right to Access Data
Users can access data by:
- In-app: View data in learning screens
- Backup file: Complete export available in JSON format
- Cloud sync (iOS / Android): Synced content can be viewed in the app on each device. When you run a manual sync, the app shows whether it completed or failed
4.2 Right to Delete Data (Right to be Forgotten)
Users can delete data by:
| Method | Scope | Timing |
|---|---|---|
| Individual or bulk deletion in app | Moves the selected words to Trash (their content stays on the device) | Immediate |
| Permanent deletion from Trash | Deletes the content of the selected words, or of all words in Trash (if you use cloud sync, it is also deleted from the cloud and your other devices) | Immediate |
| Replace via backup restore | Replaces the data on the device with the backup content, and moves words not in the backup to Trash (if you use cloud sync, this is also reflected in the cloud and on your other devices) | At restore time |
| Uninstall app | Delete all local data | At uninstall |
| Turn off cloud sync (disconnecting your Google account on Android has the same effect) | Stops sending and receiving data to and from the cloud from then on (cloud data is not deleted) | Immediate |
How deleted words are handled:
- Deleted words move to Trash with their content kept, and can be restored from Trash in Settings
- If you use cloud sync, the moved-to-Trash state is synced to iCloud / Google Drive, and the content also stays in the cloud
- Words permanently deleted from Trash have their content (terms, meanings, notes, and tags) deleted from the device and cannot be restored. If you use cloud sync, the content is also deleted from iCloud / Google Drive and your other devices
- To let each device know that a word was permanently deleted, only an identifying ID and timestamps remain on the device and in the cloud
4.3 Right to Data Portability
Users can export data anytime:
[Settings] → [Backup] → [Create Backup]
Export files are JSON and can be processed by other tools.
When restoring from a backup, you can choose either:
- Replace: Replaces current data with the backup content. Words not in the backup are moved to Trash
- Merge: Keeps current data and imports the backup. If the same word exists in both, the more recently updated version is kept
5. Security Measures
5.1 Currently Implemented
- ✅ Local storage: Hive with native sandboxing
- ✅ Input validation: Required UI form validation + Hive type consistency
- ✅ Network communication: SSL/TLS during iOS iCloud sync and Android Google Drive sync
- ✅ Access control: Accessible only by the device owner
- ✅ Offline-first: No server dependency
5.2 Encryption
The app does not implement its own application-level encryption. Data protection relies on the mechanisms provided by the OS and platform:
- Local data: OS sandbox, device encryption, and screen lock (iOS/Android OS)
- Data in transit: SSL/TLS (Apple CloudKit / Google Drive API)
5.3 Security Reporting
If you find a security vulnerability, please report it privately to the following email address instead of a public issue:
support (at) netplan.co.jp
6. Compliance
6.1 Applicable Privacy Regulations
This app aligns with:
| Regulation | Scope | Status |
|---|---|---|
| Act on the Protection of Personal Information (Japan) | Personal data collection/use | ✅ Aligned*1 |
| GDPR | EU users | ✅ Aligned*2 |
| Child protection | Users under 18 | ✅ No personally identifying information collected |
1: Local-only storage and no third-party sharing minimize personal information handling.
2: EU users are protected by the same privacy principles above.
6.2 Regions Covered by This Policy
- Japan
- Other countries/regions (including GDPR-covered regions)
7. Changes to This Privacy Policy
When this policy changes, updates are communicated as follows:
- Major changes: In GitHub release notes and this document
- Minor updates: In GitHub release notes
The update date is always reflected in “Last updated”.
8. Contact
If you have questions or concerns regarding privacy or security, please contact us at the following email address:
support (at) netplan.co.jp
9. Policy Version History
| Version | Date | Changes |
|---|---|---|
| 1.13 | 2026-10-12 | Section 4.2: Added a row for permanent deletion from Trash, stating that the content of permanently deleted words is removed from the device and the cloud. Revised replace via backup restore to state that words not in the backup are moved to Trash, and that this is reflected in the cloud and on other devices if you use cloud sync. Section 4.3: Revised the description of Replace accordingly |
| 1.12 | 2026-10-07 | Section 2.2: Reworded the sync description so it does not depend on where controls appear on screen, and added that no data is sent to or received from the cloud while sync is turned off. Section 4.2: Added a row for turning off cloud sync and merged the Android Google account disconnection row into it |
| 1.11 | 2026-10-06 | Section 2.2: Corrected the location of manual sync to the entry list screen. Section 4.1: Corrected how synced content can be checked. Section 4.2: Reflected that deleted words move to Trash and remain on the device and in the cloud. Section 4.3: Corrected the backup steps and added the Replace / Merge restore options |
| 1.10 | 2026-08-27 | Section 4.1: Removed the "sync logs" wording and corrected it to reflect actual behavior (sync status and completion notifications) |
| 1.9 | 2026-08-12 | Changed the contact channel in Sections 5.3 and 8 from GitHub Issues on the private repository to email |
| 1.8 | 2026-08-12 | Added Section 3.3 clarifying how purchase/payment information is handled for Premium purchases (App Store / Google Play) |
| 1.7 | 2026-03-28 | Updated Section 1.1 title to "Data Stored (locally)"; added Section 5.2 clarifying no app-level encryption (OS-dependent) |
| 1.6 | 2026-03-20 | Simplified Section 3.1: removed exception list; clarified developer has no data access |
| 1.5 | 2026-03-20 | Removed Android Google Drive dedicated backup buttons; added bulk delete |
| 1.4 | 2026-03-15 | Reflected lightweight auto-sync triggers (resume, save, delete) |
| 1.3 | 2026-03-14 | Reflected iOS CloudKit manual sync completion |
| 1.2 | 2026-03-14 | Corrected implementation status descriptions |
| 1.1 | 2026-03-13 | Added iCloud / Google Drive cloud sync descriptions |
| 1.0 | 2026-02-28 | Initial publication |
This policy will be updated as the app evolves.