Plan My C-Day Beta Privacy Policy
US Beta | Effective November 7, 2026
Nora Im, an individual, operates Plan My C-Day. This Policy explains the information used by the app and its related account and support pages during the US beta, for invited participants residing in the United States who are age 13 or older, including teens ages 13–17 and adults ages 18 and over. For privacy questions, access, correction, or deletion requests, contact support@mycday.com.
1 Your information and choices
Your plans and reflections are private to your account rather than public Community content. Authorized developers, support personnel, moderators, and service providers may access information as needed for operations, support, security, or legal obligations. A private account is not a promise that no one operating the service can access its information.
Plans, reflections, and app activity can reveal health-related needs, routines, relationships, or locations. Enter only what you need for the feature. We do not require medical records or proof of a diagnosis. Do not include another person’s identifying or health information unnecessarily.
The app is intended for people age 13 and older, not children under 13. We do not knowingly collect personal information from children under 13. If we learn that an account belongs to a child under 13, we will take steps to close the account and delete its personal information, subject to applicable legal requirements. Contact support@mycday.com if you believe we have collected information from a child under 13.
Teens should avoid putting their real name, school, contact details, precise location, or private health details in a public username or recipe. Plans and reflections are not automatically shared with parents or guardians. A parent or guardian may contact us about a teen’s participation or information; we verify identity and authority as appropriate and handle requests under applicable law. There is no linked parent account or automatic parent access.
For participants ages 13–17, registration asks the teen to confirm that a parent or guardian approved participation after reviewing the Terms and this Policy. We record that confirmation with the account acknowledgment and timestamp. This is the teen’s statement, not independently verified parental consent. We do not ask a parent to create an account or provide a parent’s contact information for this confirmation.
2 Information you provide
Registration collects first and last name, email, date of birth, username, and authentication information. These support account creation, eligibility checks, access, and profile management. Email is used for verification, recovery, and service messages. Our authentication provider handles passwords.
A US phone number is optional. If supplied, it is stored with your account using the +1 country code and may be used to contact you about support you request. Providing a number does not enroll you in marketing calls or texts. It is not currently used for SMS verification, sign-in, or password recovery. You can leave it blank without losing access to the beta. Contact support if you want a stored number removed.
We store the plans and activity you save, including event titles and types, dates, times, time zones, venue details, preparation actions, custom text, completion states, ratings, reflection notes and tags, and learning and challenge progress. These records support planning, history, and progress features.
Community records include submitted recipes, their account association and review status, saved recipes, likes, hidden-recipe preferences, reports, and moderation actions. Support messages may include your contact details, screenshots, and other information you choose to send.
The signup process records Terms agreement and Privacy Policy acknowledgment, a timestamp, and policy references with account metadata. A policy acknowledgment is not consent to unrelated uses.
3 Device storage and technical information
The app stores session credentials and operational preferences on your device. Saved Help Me Explain message drafts, avatar and Leaf accessory choices, accessory unlock progress, and calendar-link information are stored locally on that device. Message drafts and Leaf collection settings do not sync between devices. When you choose Copy message, the draft is placed on your device clipboard; the app does not send it to anyone. Your device’s clipboard and sharing settings may make copied text available outside the app. You can restore a message to the original app draft to remove the saved edit. Account-linked progress is not anonymous analytics.
Requests to our services and providers can include IP addresses, request times, device or browser details, and authentication or error information. Such information supports delivery, troubleshooting, and security. An IP address can suggest approximate location; it is not GPS tracking. Locations you type into plans are stored with those plans.
When you use TestFlight, Apple collects beta usage and crash information and makes testing information available to the developer. Feedback you submit can include screenshots and diagnostic details. Invitation method affects the identifying information shared. We use beta feedback and diagnostics to investigate problems and improve the app. Review Apple’s TestFlight privacy notice at https://www.apple.com/legal/privacy/data/en/test-flight/ and avoid including unnecessary private information in screenshots.
4 Calendar camera and product lookup
Calendar integration is optional. On iPhone, it requests calendar access, selects a writable calendar, and creates or updates preparation entries. It may inspect events around the relevant date and existing linked entries to avoid duplication. Calendar identifiers and synchronization status are stored to maintain the link. This workflow does not upload unrelated calendar entries to our database.
Calendar titles, times, and any included location are handled by the calendar provider and may synchronize to other devices. People with calendar access may see them. Revoking permission does not necessarily remove entries already created.
Camera access is optional and reads product barcodes on your device. The scanner does not save or upload photographs or video. Manual barcode entry is available.
Barcode requests go directly to Open Food Facts to retrieve product information and images. The feature does not send your account identifier, plans, or reflections with that request and does not currently save scan history. Open Food Facts and its image service receive the requested barcode or image and network information such as IP address. External resources you open receive information through your browser under their own privacy practices.
5 Community visibility and moderation
Recipes submitted for sharing enter a moderation queue and require approval before appearing in Community Discover. Published recipe content and the author’s public username are visible to people who can access Community. Aggregate like counts are displayed; account-linked reaction records support that feature. Your registration names, email, phone number, birthday, private plans, and reflections are not automatically published.
Recipe content and its identifier are emailed through our email provider to support@mycday.com for review. Report notifications contain the recipe title and recipe/report identifiers; report text and reporter identity remain in the authenticated moderation workflow rather than the notification email.
Reports are not public posts. We do not intentionally identify a reporter to the reported author, except when disclosure is legally required or necessary for a legal claim. Moderation records support review and enforcement. Approval does not certify medical or food safety.
Other people may copy published content. Deletion cannot remove copies outside our control. This beta does not include forums, comments, direct messaging, or linked parent access.
6 Providers and other disclosures
Supabase provides authentication and database services for account and saved-feature information. Resend handles app email delivery, including recipe-review and report notifications. Email providers process addresses, message contents, and delivery records; the support mailbox provider handles messages sent to our inbox. Apple provides TestFlight distribution, testing information, and feedback services.
The account-return page at https://mycday.com/auth/ helps account email links return to the app. GitHub Pages hosts this page and our policy pages and may receive normal web-request information. Account links can contain credentials; do not forward them or include them in screenshots.
Service providers process information to deliver their services. Access by people operating the app is limited to legitimate operational, support, moderation, security, and legal purposes. Calendar providers, Open Food Facts, and external websites also handle information when you use those features.
Information may be disclosed when required by law or reasonably necessary to address serious harm, misuse, or legal claims, or at your direction. We seek to limit disclosures to what is appropriate. Any business transfer involving information remains subject to applicable privacy requirements.
Although participation in this beta is limited to US residents, service providers may process or store information in the United States or other countries. Limiting participation to US residents does not mean all information stays in the United States.
7 Purposes and sensitive information
We use information to provide accounts, plans, progress, product requests, calendar functions, recipe sharing, support, moderation, testing, and security, and to meet legal obligations. Optional device permissions are requested for their specific functions.
We do not sell personal information or authorize use of private plans and reflections for advertising or general-purpose AI training. Beta participation is not research enrollment. Any future research or materially different data use requires its own explanation and any legally required permission.
Where applicable law requires separate consent, a general Privacy Policy acknowledgment does not replace it. You may contact us about withdrawing consent or limiting processing; withdrawal may affect features that need the information.
8 Retention and account deletion
Beta accounts are not automatically deleted when this beta round ends. You may keep your account while the service remains available, or request deletion at any time. We retain account and saved-feature information to provide the account and its features, subject to deletion requests and applicable legal requirements.
Use Me → Settings → Delete account, or email support@mycday.com, preferably from your account email. We may verify your request. In-app deletion requests remove the authentication account and associated profile, plans, reflections, learning progress, authored recipes, and related Community records from the live app database. If the request fails, the app displays a failure message.
Deleting the app account does not automatically erase support or moderation emails, delivery logs, backups, Apple-held TestFlight records, or entries already written to an external calendar. Those records require separate handling. Limited records may be retained where needed for an unresolved support or safety matter, security, a legal obligation, or a dispute; retention must be limited to the relevant purpose and applicable law. Contact us about copies held by us outside the live database and the scope of your request.
Local device copies require separate handling from server records. In-app account deletion attempts to clear saved message drafts and avatar preferences on that device; this does not clear another device or clipboard copies. Contact support if you need help with remaining local information.
Signing out, uninstalling, or choosing Stop Testing in TestFlight does not delete your app account. Copies made by other users or external services may remain outside our control.
9 Access correction and other rights
Contact support@mycday.com to request access to or a copy of your information, correction, or deletion. Some profile fields can be edited in the app. We may verify identity proportionately and will respond under applicable law. Where relevant, rights may also include withdrawal of consent, restrictions or objections to processing, portability, and review of a denied request.
Your rights depend on applicable US federal and state law and may include access, correction, deletion, and an appeal of a denied request where provided by law. Contact support@mycday.com to make a request or ask us to reconsider a decision. You may also raise concerns with your state attorney general or the Federal Trade Commission. We do not penalize the exercise of protected privacy rights.
If you are under 18, you can ask us to remove a recipe or other content you posted by identifying it in a message to support@mycday.com. Removal from our service cannot erase copies other people have made or information that must be retained by law.
You can change camera and calendar permissions in device settings. Calendar or notification previews may expose information on shared or locked devices. Apple’s privacy controls apply to information Apple holds through TestFlight; deleting an app account is a separate action.
10 Security and policy changes
We use authentication and access controls to help protect information. No system can be guaranteed secure. Protect your device, password, and account links, and report suspected privacy or security issues to support@mycday.com. We will investigate and provide legally required incident notices.
When practices materially change, we will update this Policy and provide appropriate notice through the app or email. We will obtain consent where required before a new use. Questions and requests can be sent to Nora Im at support@mycday.com.
Mailing address: Nora Im, 450 Sutter Street, Suite 2118, San Francisco, CA 94108, United States.