This policy includes the processing of personal information for account sign-in and cloud features. You may choose whether to use these features.
JaMo (the “App”) values your privacy. This policy explains the information processed, the purposes of processing, and how information is retained and deleted. The App’s basic editing features can be used locally on your device. If you use account sign-in or cloud features, information needed for those features is processed on servers.
When you choose Sign in with Apple or Google, your account is created or authenticated through the selected authentication service and Supabase. This involves processing your email address, user account identifier, sign-in provider information, and authentication and session information. If you use Apple’s Hide My Email feature, an Apple relay email address may be used.
The App does not directly ask for or store your Apple or Google account password. Authentication information needed to maintain your sign-in session is stored in your device’s Keychain.
During Google sign-in, the authentication provider may pass your name and profile picture URL to Supabase. JaMo does not use this information to display your account or provide project features. The authentication database is configured to remove names and profile picture URLs when account metadata is stored or updated. These fields have also been removed from existing authentication account metadata. Email addresses, user account identifiers, and information needed for authentication are retained.
This measure applies to JaMo’s operational database. It does not establish immediate deletion of information temporarily processed by Google or Supabase during authentication, previously issued authentication tokens, or provider-internal logs and recovery copies. The App does not use this information for advertising targeting.
For projects you choose to upload or synchronize automatically, the following information is transmitted to servers and stored in association with your account:
Local projects for which you do not use cloud features are not transmitted to servers for cloud storage or synchronization.
Authentication and server operations may generate service-provider logs containing authentication events such as sign-in and sign-out, access times, IP addresses, and technical information about requests and errors. This information is processed for service operation, security, and troubleshooting.
Operational logs include request times, request paths, response statuses, and technical information about the App and operating system. Under the current Supabase Free plan, the retention period for API and database logs is one day, and the period for external authentication audit logs is one hour. Additional database storage of authentication audit logs is disabled. These periods apply to the specified log types provided by Supabase; they do not establish when all internal operational records are deleted.
If you contact the developer directly by email or another method, your email address, inquiry contents, and materials you voluntarily attach are processed. Attachments may include device information, work files, screenshots, or screen recordings.