App privacy policies
These apps have their own privacy policy, which applies to that app in place of this general policy where the two differ.
1. Introduction and scope
This Privacy Policy (“Policy”) describes the privacy and data protection practices of Zoe Wilpon (“Developer,” “we,” “us,” or “our”) in connection with mobile applications, software products, and related services developed, maintained, operated, or published by the Developer (collectively, the “Applications”).
This Policy applies to all current and future Applications that reference or link to this Policy, unless an Application expressly provides a separate privacy policy.
We recognize the importance of protecting personal information and are committed to transparency, data minimization, and providing users with appropriate control over their information.
Different Applications may provide different functionality and use different data-processing technologies. Accordingly, certain provisions of this Policy apply only when the relevant functionality or service is available or enabled.
2. Categories of information
Depending on the particular Application and the features used, information processed may include the following categories.
2.1 User-provided content
Information voluntarily created, selected, entered, uploaded, or maintained by users, including:
- Photographs, images, and media attachments;
- Notes, descriptions, lists, and user-generated documents;
- Collections, organizational records, categories, and custom fields;
- Tasks, reminders, and preferences;
- Game progress, scores, achievements, and saved states;
- Backup files and application-specific content.
Users determine what content they provide to an Application through its available features.
2.2 Account and cloud service information
Where an Application offers optional cloud storage, synchronization, or account functionality, information may include an account identifier, authentication information handled by the authentication provider, synchronization metadata, and content selected or configured for remote storage.
The categories of information processed depend upon the particular service and the features enabled by the user.
2.3 Diagnostic and technical information
Where diagnostic, crash-reporting, or analytics services are implemented, certain technical information may be collected, including:
- Device model, hardware characteristics, and operating-system version;
- Application version and configuration;
- Crash reports, error messages, and stack traces;
- Application installation or session identifiers;
- Performance and stability measurements;
- Application usage events and interactions, where analytics is enabled;
- Technical timestamps and related diagnostic metadata.
Such information is used for legitimate application functionality, diagnostics, maintenance, and improvement, as described in this Policy.
2.4 Data minimization
We endeavor to limit the information accessed or processed to that which is reasonably necessary for the functions and services provided.
The existence of a category in this Policy does not indicate that every Application collects or processes that category of information.
3. User control and device permissions
3.1 User-initiated access
Our Applications are designed, where practicable, to allow users to choose the information and device resources they wish to make available.
For example, an Application that supports image attachments may allow users to select specific photographs through an operating-system-provided photo selection interface.
Selecting an image authorizes the Application to access that selected content for the requested functionality. Such access does not, by itself, authorize unrestricted access to other photographs or files on the device.
3.2 Permission requests
Depending on an Application’s functionality, permissions or user authorizations may be requested for capabilities such as:
- Camera access;
- Selected photographs and media;
- Files and documents;
- Notifications and reminders;
- Other device resources reasonably necessary for enabled features.
Where Android provides a system selection interface that does not require a broad runtime permission, the Application may use that interface instead.
Permissions may be granted, denied, limited, or revoked through the mechanisms provided by the operating system.
3.3 Optional features
Certain functionality may require additional access or the processing of additional information.
Where a feature is optional, users may choose whether to enable it, subject to the technical requirements of that feature.
Declining an optional permission may prevent use of the associated feature without necessarily preventing use of unrelated Application functionality.
4. Local storage
Certain Applications may store information within application-specific storage, local databases, or other storage locations made available by the operating system.
Where an Application supports offline operation, locally stored information may remain available without an active internet connection.
Information stored locally is not necessarily transmitted to the Developer or a third-party service merely because the user creates or maintains it.
However, information may be transmitted when a user enables a cloud feature, initiates a transfer, or uses Application functionality that requires remote processing.
Diagnostic or technical information may also be transmitted where the relevant reporting service is enabled.
5. Optional cloud storage, backup, and synchronization
5.1 Availability of cloud features
Certain Applications may offer cloud-based backup, storage, restoration, or synchronization functionality.
Where such features are optional, users may choose whether to enable or utilize them.
Cloud features may require authentication, network access, or the use of third-party infrastructure.
5.2 Information transmitted to cloud services
When cloud storage or synchronization is enabled, information necessary to provide the selected functionality may be transmitted to remote infrastructure.
Depending on the Application and configuration, this may include:
- User-generated records and associated metadata;
- Photographs and other selected attachments;
- Settings or preferences designated for synchronization;
- Backup archives;
- Account identifiers and synchronization status information.
If an Application provides automatic synchronization after a user enables that feature, subsequent changes to synchronized information may be transmitted automatically while the feature remains active.
5.3 Cloud service providers
Cloud features may be implemented using established third-party infrastructure, including services provided by Google Firebase or Google Cloud.
Such providers may process or store information as necessary to deliver the applicable service, subject to their contractual obligations, security controls, and relevant privacy policies.
Cloud information may be processed or stored in jurisdictions different from the user’s place of residence.
5.4 User control
Where supported by the Application, users may manage cloud functionality through available account, backup, synchronization, or application settings.
Disabling future synchronization may stop subsequent uploads but does not necessarily delete information already stored remotely.
The procedures for deleting remotely stored information, including any account-associated content, will be made available in accordance with the Application’s functionality and applicable requirements.
5.5 User-directed exports
Applications may allow users to export information to files or storage destinations of their choosing.
When a user initiates an export or transfer, the receiving service or storage location may be subject to its own security practices and privacy policy.
6. Diagnostics, crash reporting, and analytics
6.1 Application reliability
Certain Applications may use diagnostic or monitoring technologies to identify software defects, investigate crashes, assess application performance, and improve reliability.
These technologies may transmit technical information from a user’s device to a diagnostic service provider.
6.2 Firebase Crashlytics
Applications may incorporate Firebase Crashlytics, a crash-reporting service provided by Google.
Where implemented and enabled, Crashlytics may process information such as:
- Crash and exception reports;
- Stack traces and diagnostic messages;
- Device characteristics and operating-system information;
- Application version and runtime state;
- Installation, session, or crash-related identifiers;
- Other technical metadata relevant to diagnosing errors.
This information is used to investigate defects, improve application stability, and maintain software functionality.
Crash reports are not collected for the purpose of selling users’ personal information.
6.3 Firebase Analytics
Certain Applications may also use Google Analytics for Firebase to understand Application usage and functionality.
Where enabled, analytics may process information concerning application interactions, usage events, device characteristics, application-instance identifiers, and related technical information.
We may use resulting measurements, reports, and statistical information to evaluate functionality, identify issues, and improve the user experience.
The availability and configuration of analytics may vary by Application.
6.4 Restrictions on diagnostic content
We endeavor to avoid deliberately including user-created notes, private photographs, authentication credentials, or other unnecessary personal content in custom diagnostic messages or analytics events.
Nevertheless, technical reports may contain information included in exception messages, logs, or other diagnostic contexts.
Such information will be handled in accordance with applicable requirements and the practices of the service provider.
6.5 Diagnostic and analytics controls
Where an Application provides controls for optional diagnostic reporting or analytics, those controls will govern the relevant collection as implemented by that Application.
Certain diagnostic technologies may collect information automatically when enabled. The absence of an account or a cloud-backup selection does not necessarily disable diagnostic reporting.
7. Purposes of information processing
Information may be processed for the following purposes, where applicable:
- Providing Application functionality and maintaining user-created content;
- Saving local information, preferences, and configuration settings;
- Performing user-requested cloud backups, restoration, or synchronization;
- Authenticating accounts and maintaining associated services;
- Identifying crashes, correcting defects, and improving reliability;
- Evaluating Application functionality and performance;
- Maintaining security and preventing misuse of associated services;
- Responding to user support inquiries;
- Complying with applicable legal obligations.
Processing is limited to purposes reasonably connected with the relevant Application and disclosed functionality.
8. Disclosure to third parties
We do not sell personal information or user-generated content to data brokers, and we do not use personal information for targeted advertising.
Information may be processed by third-party service providers where reasonably necessary for the provision of cloud storage, authentication, diagnostics, analytics, security, or other expressly supported functionality.
Information may also be disclosed when directed by a user, required by applicable law, or otherwise permitted by applicable legal requirements.
Third-party service providers may include Google and Firebase services where integrated into an Application.
Our use of service providers does not remove our responsibility to accurately disclose applicable collection, transmission, and processing activities.
9. Data security
We endeavor to implement reasonable administrative, technical, and organizational safeguards appropriate to the nature of the information processed.
Depending upon the service and Application, these may include:
- Operating-system application isolation;
- Controlled access to application-specific storage;
- Access management for remotely stored information;
- Secure network communications;
- Authentication and authorization mechanisms;
- Security controls provided by applicable cloud service providers.
No electronic storage or transmission system can guarantee absolute security.
Users are encouraged to maintain appropriate device security, safeguard authentication credentials, and protect exported backup files.
10. Data retention, deletion, and account management
10.1 Locally stored information
Locally stored Application information may generally be deleted using available in-app functionality, clearing Application data, or uninstalling the Application.
10.2 Remotely stored information
Information maintained through cloud functionality may remain remotely stored until deleted pursuant to the applicable service’s retention and deletion mechanisms.
Where an Application offers cloud accounts, account-associated content and deletion procedures will be governed by its supported functionality and applicable legal and platform requirements.
10.3 Backup copies
Deleting an item from an Application does not necessarily delete copies previously exported, backed up, or transferred to independently controlled destinations.
Remote backups and service-provider retention mechanisms may be subject to additional retention periods.
10.4 Data and account deletion requests
Users may submit privacy-related inquiries and deletion requests to apps@zoewilpon.dev.
Where an Application supports account creation, the applicable account and associated-data deletion options will be made available in accordance with Google Play requirements and applicable law.
We will review and respond to applicable requests as legally required.
11. Children’s privacy
Our Applications are intended for general audiences and are not specifically directed toward children.
We do not intentionally design our Applications for the collection of children’s personal information.
If we become aware that personal information from a child has been collected in violation of applicable law, we will take appropriate measures as required by law.
Parents or guardians with concerns may contact apps@zoewilpon.dev.
12. International data processing
Applications and their integrated services may be accessible from multiple jurisdictions.
Where cloud or third-party services are used, information may be processed or stored in countries other than the user’s country of residence.
Where applicable law requires additional safeguards, notices, or protections for international transfers, we will take appropriate measures to comply with those requirements.
13. Privacy rights
Depending on applicable law and the nature of the information processed, users may have rights to request access to, correction of, deletion of, or information concerning the processing of personal data.
Certain rights may be subject to lawful exceptions or limitations.
Requests may be submitted to apps@zoewilpon.dev.
We will evaluate and respond to requests as required by applicable law.
14. Third-party websites and services
Applications may provide access to third-party websites, platforms, or services outside the Developer’s control.
Such services may be governed by their own terms, privacy policies, and security practices.
Users are encouraged to review those policies before transferring information to third-party services.
15. Changes to this privacy policy
We reserve the right to modify this Policy periodically to reflect changes in our Applications, technologies, data practices, and applicable legal requirements.
Revisions will be published at the designated Privacy Policy URL with an updated revision date.
Where required by law, we will provide additional notice or obtain appropriate consent before materially changing how personal information is processed.
16. Interpretation and applicability
This Policy applies to Applications that expressly reference it.
Descriptions of optional features, potential categories of information, or third-party technologies shall not be interpreted to mean that every Application implements those features or technologies.
Where an Application requires additional or more specific disclosures, those disclosures will supplement this Policy.
Nothing in this Policy is intended to limit rights or protections that cannot lawfully be waived.
17. Contact information
Questions, requests, or concerns regarding this Policy or the privacy practices of our Applications may be directed to:
- Developer
- Zoe Wilpon
- apps@zoewilpon.dev
- Website
- zoewilpon.dev