Your information & choices
Privacy Policy
Last updated:
AmandaMade LLC, doing business as AmandaMade Digital Studio ("we," "our," or "us"), operates Snap2Cal. This policy explains how we handle information when you use our website, web app, iOS app, beta signup, and support services.
1. Information we collect
- Uploads and extracted events. Photos, screenshots, images, and PDFs you select, their filenames and file types, and the event details extracted from them. These may include names, dates, times, locations, and other personal information in the file.
- Google account information. When you connect Google, we receive your name, email address, profile picture, and Google account identifier. We keep account and sign-in records, including activity dates and sign-in counts.
- Calendar connection. We access your calendar list so you can choose a destination, and send the event details you approve to Google Calendar. We remember your selected calendar on your device. Legacy usage logs also retain destination calendar identifiers.
- Usage records. Account or anonymous session identifiers, processing timestamps, file types, processing outcomes, event counts and broad categories (such as school events or travel), and whether or how many events were added to a calendar. Signed-in activity can be linked to your account; anonymous processing can be linked when you sign in to save those events. Our account and analytics databases do not store raw files, filenames, event titles, descriptions, or locations.
- Beta signups and email preferences. Information you submit, such as your name, email, iPhone and Google Calendar eligibility answers, other survey responses, and email preferences. Beta records may also include device or iOS details supplied in earlier forms, participation status, and TestFlight invitation status.
- Support information. Messages and problem descriptions you send us. When you submit an in-app problem report, the selected upload may be attached and stored with the report. Check the attachment shown before sending.
- Technical information. Our hosting and service providers may process IP addresses, browser or device information, request logs, and error information to deliver, secure, and troubleshoot the service.
2. How we use information
We use information to extract event details, connect your Google account, add the events you approve, remember your calendar choice, maintain sessions, and provide support. We use account and processing metadata to understand usage and reliability and improve Snap2Cal.
For beta participants, we use signup information to manage eligibility, invitations, and beta communications according to your email choices. Signing in to the app does not itself subscribe you to marketing emails.
We do not sell your personal information or use your Google account or calendar data for targeted advertising.
3. Uploads and AI processing
Before your first upload on a device, we ask your permission to share the photos and PDFs you choose with Claude, including personal information in those files. Your choice is remembered on that device only and covers future uploads there until you reset it, sign out, or we change who receives your files, what we send, or why. We do not store this choice on our servers.
When you select a file for processing, Snap2Cal sends it through our Netlify-hosted service to the Anthropic Claude API. The request includes the file content, filename, and your device's current date and year to help interpret event dates. This also happens in the try-before-sign-in flow.
Claude returns suggested event details for you to review and edit. We do not save the file or extracted event text in our account or analytics databases. A file sent with a problem report is retained separately for support.
Anthropic's published API policy provides for deletion of inputs and outputs within 30 days by default, with exceptions including safety, legal requirements, or a different agreement. Anthropic states that commercial API inputs and outputs are not used to train its models by default. See Anthropic's data retention policy and model training policy.
Only upload files you have permission to share. Avoid including sensitive information that is not needed to create your events.
4. Google Calendar access
You can try processing before connecting Google. Connecting Google allows Snap2Cal to identify your account, show the calendars available to you, and add the events you approve to your chosen calendar.
The requested event permission allows access to and management of calendar events. Snap2Cal uses it to create events you choose and, when checking a retried save, to retrieve the specific event it attempted to create. We do not scan your existing calendar events to infer interests or personalize the app.
Google credentials are stored on your device and sent to Google for authorized requests. Our server handles authorization-code exchanges and token refreshes; it receives the code or refresh token needed for those operations. Google identity tokens are sent to our service to verify app sessions. Credentials are not part of our usage analytics.
Snap2Cal's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
5. Service providers
We use these services to provide Snap2Cal:
- Google: Sign-in, Calendar, and beta signup forms and response storage. Google privacy policy.
- Anthropic: AI processing of selected photos and PDFs. Anthropic privacy policy.
- Netlify: Website and function hosting, legacy account and usage storage in Netlify Blobs, and submitted problem reports and attachments. Netlify privacy policy.
- Supabase: Account, session, processing metadata, and beta contact storage. Imported historical activity and legacy Netlify records may both be retained. Supabase privacy policy.
- Loops: Beta contacts, email preferences, and email delivery for signup communications. Loops privacy policy.
- Apple: iOS app distribution and TestFlight beta invitations, which may use your email and name. Apple privacy policy.
Information may be processed in the United States and other countries where these providers operate. Their policies describe their own data handling and retention practices.
6. Storage and retention
On your device
Browser or app storage holds Google credentials, profile information, calendar preferences, session identifiers, your AI processing permission, and pending usage-reporting records. Event review drafts and recent add details are kept in session storage so you can continue after a refresh or sign-in. Signing out clears credentials, review drafts, and AI processing permission. Clearing website or app data removes other locally stored records; it does not delete server records or events already saved to Google Calendar.
Records we keep
We retain account, usage, beta signup, and support records to operate and improve Snap2Cal. These records are not automatically deleted after a fixed period. To request deletion, choose Delete account in the signed-in account menu. We complete accepted requests within 30 days and email you when deletion is complete. The app shows the completion window before you confirm and the deadline after acceptance. Email hello@snap2cal.ai if you cannot access your account or need help.
Deletion requests cover records we hold in our databases and legacy logs, as well as associated beta, email, and support records where applicable. We may need to verify your identity to locate the right records. Some information may need to be retained to meet legal obligations or resolve security issues, and copies in provider backups may remain until those backups expire.
When we accept an in-app request, we revoke Snap2Cal sessions, begin revoking our Google access, and clear account data from that device. An encrypted Google credential may be held only while revocation is retried. The request email is held until the completion notice is sent. We retain a minimal request receipt and hashed suppression identifiers to prevent old logs or imports restoring deleted data. These hashes are not treated as anonymous information. Deleting Snap2Cal data does not delete your Google account or events already saved in Google Calendar.
Uploaded files follow the processing and support distinctions in section 3. Events saved to Google Calendar remain there until you remove them through Google.
Security
Snap2Cal uses HTTPS for data sent to its services and providers, keeps service credentials on the server, and restricts database access. No method of transmission or storage is completely secure.
7. Your rights and choices
- Access, correction, or deletion. Choose Delete account in the app to initiate account deletion. Email hello@snap2cal.ai to request access, corrections, or help with deletion. Signing out alone does not delete server records.
- Google access. Disconnect Snap2Cal through your Google Account connections. Revoking access stops future authorized Calendar requests but does not remove previously created events or our records.
- AI permission. Choose Reset AI permission in the account menu, or at the bottom of the home screen when signed out, and we will ask again before your next upload. This does not recall files already sent for processing.
- Local data. Sign out to clear credentials, review drafts, and AI permission. Use browser or device settings to clear remaining website or app data, including remembered preferences.
- Email choices. Use the unsubscribe option in our emails or contact us to change your email preferences or stop beta communications.
- Uploads and calendar writes. Choose which files to process and which suggested events to add. If you do not want a file sent for AI processing, do not select it for processing.
Depending on where you live and which laws apply, you may have additional privacy rights, including rights to know, access, correct, or delete personal information. California residents may exercise applicable rights by contacting us. We do not sell personal information or share it for cross-context behavioral advertising.
8. Children's privacy
Snap2Cal is intended for adults managing their schedules, including family events. It is not intended for use by children under 13, and we do not knowingly collect account information directly from children under 13. Files adults choose to upload may contain information about children, such as a school or activity schedule. Contact us if you believe a child under 13 has provided information directly to us.
9. Changes to this policy
We will update the date at the top when this policy changes. Where required, we will provide additional notice or obtain consent before using information in a new way.
10. Contact us
For privacy questions or to request deletion, contact AmandaMade LLC at hello@snap2cal.ai.