Privacy policy

1. CSV files and information on your device

The App reads CSV files you select and text you enter. For viewing, editing and searching, it stores their contents, imported data, indexes and display settings in its private storage on your device. It has no feature that uploads these CSV data to the Operator’s server.

The App does not send CSV contents as advertising or usage analytics events or custom logs. If a CSV file contains personal information, that information is also processed as part of the file.

The App has no account registration and does not ask you to register your name, address or phone number.

2. External services and purposes of use

The App uses, or plans to use, the following Google services. The information actually transmitted depends on your app version, service settings, device settings and consent choices. Through their consoles, the Operator may view diagnostic and usage reports and, after advertising is introduced, advertising reports.

Firebase Crashlytics: crash analysis

We use Crashlytics to investigate crashes and unresponsive states and improve stability. Google receives information such as crash times, stack traces, exception types and messages, app version, device model, OS and memory, and identifiers that distinguish app installations or sessions. Exception messages may include the path of a file being processed.

See Firebase Privacy and Security.

Google Analytics for Firebase: usage analytics

We use Analytics to understand usage and improve features. On first launch, you can choose whether to allow transmission. Only with your consent does the public release send Google automatic events such as first launch, sessions, screen views, engagement time and app updates, along with device, OS and app information, language, approximate location and identifiers such as the app instance ID.

The App does not send CSV contents, file names, search terms or entered URLs as custom analytics events. Advertising ID collection and use of analytics data for personalized advertising are disabled. All CSV features remain available if you decline. You can allow or decline at any time in Settings → Usage analytics. Withdrawing consent stops collection and resets Analytics data and the app instance ID on your device; it does not immediately delete data already sent to Google. Your choice, its date and the notice version are stored on your device. This choice applies to Analytics separately from Crashlytics crash reporting. See Google Analytics data collection information.

Google AdMob: advertising (planned)

We plan to use AdMob to display ads, measure their effectiveness and prevent fraud. Once introduced, information such as IP address, approximate location, identifiers such as the advertising ID, device information, ad impressions and clicks, and diagnostics may be sent to or shared with Google.

As of this policy’s update date, the Android app has no advertising feature. When introducing it, we will provide explanations, consent and choice mechanisms appropriate to the advertising settings and regions served, and update this policy. Even non-personalized ads may involve information needed for delivery and fraud prevention. See Google Mobile Ads SDK data disclosures.

Also see the Google Privacy Policy and how Google uses information from sites or apps that use its services.

3. URL downloads, image display and sharing

When you download a CSV from a URL or use the feature to display image URLs in a CSV, your device connects directly to that URL’s server. That server receives your IP address and requested URL. Personal information or authentication text embedded in the URL is also sent to that server.

Exporting or sharing passes the file to the destination, app or service you choose. A cloud storage service, for example, may store it on its servers. Consult the privacy policies of those destinations and recipients.

4. Contacting us

If you contact us by email, the Operator receives your email address, name if provided, message and attachments. We use them to reply, investigate issues and retain necessary support records. Please avoid sending confidential information or CSV files containing personal information that is unnecessary for the investigation.

5. Retention and deletion

• You can delete imported CSV data and indexes from the App’s file list. You can also erase app data by clearing the App’s storage in Android settings.
• Deleting from the App’s list does not delete original CSV files, exported files or copies saved by recipients. Delete them separately where necessary.
• Google Analytics event-level and user-level data are retained and deleted according to its data retention settings. The same retention period may not apply to aggregated reports. Uninstalling the App does not immediately delete data already sent to Google.
• Temporary files created for sharing are deleted on a subsequent app launch or sharing operation once seven days have elapsed since creation. The OS may remove cached files sooner.
• Google states that Crashlytics crash information and associated identifiers are retained for 90 days before deletion from live and backup systems begins.
• Support information is retained only as long as needed to handle inquiries and keep necessary records, then deleted. Any legally required retention is observed.

Deleting local app data or uninstalling does not immediately delete information already sent to Google or recipients. Contact us below about access or deletion. We will respond within the scope of information we control and the capabilities of each service.

6. Information management and processing abroad

Local app data are managed in the app-specific storage provided by Android. We seek to protect support information and external service consoles by measures such as limiting access to what is necessary.

Information sent to Firebase and other external services may be stored or processed at facilities operated by Google or its contractors, including outside Japan. Communications with Firebase are encrypted. Encryption of connections to URLs you specify depends on whether they use HTTPS or HTTP.

7. Payments

As of this policy’s update date, the App has no in-app purchases and does not obtain payment information such as credit card details. If future payment features change how information is handled, we will update this policy.

8. Changes to this policy

We update this policy when features, services or information practices change. We will announce important changes in the App or by other means and, where required by law or service provider requirements, explain and seek consent before collecting or using information.

9. Operator and contact