Skip to content
TryMyDays
  • How it works
  • Support
  • Privacy
  • Terms

Document privacy_policy · ccc263e5-393e-4000-b9a1-e94ba652a5bb · tmd-pp-2026-09-15-obs1 · SHA-256 24403861005e26a4aba8cbfb432df333b098992ea920216d9c5c31d2d8be3a46 · active

# TryMyDays Privacy Policy

Effective: September 15, 2026 (00:00 UTC) · Version: TMD-PP-2026-09-15-OBS1

Geonwoo Park, operating TryMyDays personally (“TMD”, “we”, “us”), is responsible for the personal information described here. Our business/service address is 403-944 East 8th Avenue St, Vancouver, BC V5T 1T8, Canada. Contact Geonwoo Park, our Privacy Officer, at privacy@trymydays.com or, if needed, support@trymydays.com. This policy covers our apps, related websites and support operations.

## 1. Information we handle

| Category | Information and sources | Main purposes |
|---|---|---|
| Account and sign-in | Email, identity-provider identifiers and available account information from you, Apple or Google; authentication/session records | Create and secure an account, sign-in, recovery and service communications |
| Eligibility | Date of birth, country, US state or Canadian province/territory where applicable, eligibility result and correction history | Apply 18+ and availability rules, correct mistakes, prevent circumvention; country may also supply a default currency |
| Profile | Username, display information, avatar, biography and other profile information you choose to provide | Identify your public profile and contributions; do not enter private location or sensitive information into public fields |
| Content and activity | Uploaded video/audio/images/text, Original Days, Steps, Tries, Results, captions, categories, cost/currency, selected times, and processing metadata | Capture, process, publish, display and operate the activities and participant features you use |
| Social and discovery | Likes, follows, saves, comments, blocks, selected filters and search requests, completion and publication information | Operate interactions, search, ranking and discovery; current discovery uses content and activity signals such as completion counts, categories, cost and publication timing |
| Reports and support | Reports, relevant content references, explanations, correspondence and information supplied by users, affected non-users or authorities | Address safety, privacy, IP, eligibility, account and support matters; evidence may include sensitive information needed for that matter |
| Security, legal and operations | Necessary request/IP information, authentication and abuse-prevention records, rate-limit identifiers, admin/security actions, document acceptance and deletion records | Operate and protect the Service, enforce rules, record permissions, comply with law and handle claims |
| Device storage | Secure authentication storage, temporary capture/upload queues, caches and device timezone/settings used by the app | Sign-in, upload reliability, playback and scheduling; some information remains on your device until its relevant lifecycle ends |
| Mobile crash and performance reports | If you allow these reports, limited crash, error, stack, device/OS, app-release, technical-session and bounded interaction-timing information from the app; a random persistent identifier for that app installation; and an approximate city and region derived by Sentry from the connection IP | Diagnose crashes, repeated failures, performance and regional service problems |
| Backend operational monitoring | Service-health and processing-status records, including timestamps, level, service, environment, release, bounded event names and bounded primitive technical values | Monitor reliability, detect worker failures and investigate operational incidents |

We receive information directly from you, automatically from your use and devices, from identity and hosting providers, and from other people who post or report material concerning you. A video, caption, cost/currency or event time may itself reveal something about location or other people. Raw uploads may contain embedded metadata before processing; media processing removes global metadata from canonical outputs but is not a promise that raw uploaded files never contained it.

We request camera or microphone access for recording you initiate. We do not operate a background microphone feature, collect your address book, operate direct messages, or use facial-recognition identity templates. The current Service has no GPS-based Nearby feature or continuous location-history feature. Country, region, timezone, any location you put in Content or a public profile field, and network information are different from a live GPS tracking service.

Locality and Nearby. We use the country and province or state associated with your account to determine service availability and provide regional features. You may choose a home city or primary metro for local discovery and recommendations, and creators may assign a city or metro to a Day. Providing a home locality is optional and you can edit or remove it. If we introduce Nearby, it will request foreground device-location permission when you choose to use the feature. We do not intend to collect continuous precise GPS history or background location for Nearby. Any optional retention of device-derived locality for Product Analytics will also require Product Analytics to be on.

## 2. Public and private information

Published Content, public profile information and public interactions may be seen, copied or shared by other people, including through links or authorized exports. Do not publish material you are not entitled to share. Eligibility details such as your full date of birth and private country/region fields are not public profile fields. Private Tries, unpublished materials, reports and support messages are handled for their relevant functions and are not made public merely because your profile is public.

A person who appears in a post may not have an account. You can report a privacy or recording concern using Privacy and Unauthorized Recording Reports (https://trymydays.com/privacy-recording-removal/). Where law requires an additional notice about indirect collection, we provide it unless an applicable exception permits otherwise. We may limit disclosure of a reporter's identity or evidence to protect others or an investigation, as permitted by law.

## 3. How we use information and obtain permission

We use information for the stated Service, communication, safety, security, legal and business-operation purposes. Where consent is required, we obtain it in a manner appropriate to the sensitivity and use; in other cases law permits or requires processing without consent, such as responding to a qualifying emergency, investigating abuse or complying with legal process. Agreement to the Terms is not blanket consent to every possible data use.

You can withdraw consent where applicable by contacting us or changing available settings. We will explain material consequences, such as a feature no longer working, and any lawful reasons we need to retain limited information. We do not require you to waive mandatory rights to receive support.

Mobile crash and performance reporting follows the separate diagnostics choice you make in the app. You can use TryMyDays without allowing these reports and can change your choice at any time in Settings → Privacy → Crash and performance reports. If you withdraw, new Sentry collection and transmission stop, including later transmission of reports queued while permission was absent or withdrawn. Reports previously sent with permission ordinarily remain until their applicable retention period ends, unless earlier deletion is required. This diagnostics choice is separate from optional Product Analytics and from agreement to our Terms.

## 4. Providers, disclosures and international processing

We use Supabase for authentication, databases, storage and backend functions. Its primary database, authentication and storage hosting for this Beta is in Oregon, United States. Railway processes media and background jobs in California, United States, and Amsterdam, Netherlands. Supabase Edge Functions execute regionally near callers; their processing is not confined to the primary database region.

We use Resend to deliver authentication and account-related email through Supabase. Resend's primary processing and customer-data storage are in the United States, including message content, delivery logs, webhook payloads and account records. Email sending and routing locations may differ from stored-data locations; a sending-region selection does not change that US storage location.

Cloudflare provides web/edge services and Email Routing. Our public contact aliases forward through Cloudflare to a personal Google/Gmail account, not Google Workspace. Cloudflare edge and Email Routing and Google/Gmail use distributed international processing; we do not represent them as having a Canada-only or other fixed-country residency guarantee. Apple and Google process sign-in information when you select their sign-in services, including under their own international-processing policies. The named US and Netherlands core hosting locations are not an exhaustive list of countries in which distributed providers may process information. Hosting, email and identity providers process necessary account, Content, communications, device/request or operational data according to their role.

We use Functional Software, Inc., doing business as Sentry, for optional mobile crash, error and bounded performance reporting, and Better Stack, Inc. for bounded backend operational logging and uptime/worker monitoring. Their selected service data regions are in the United States. Supporting infrastructure, service and support processing may also occur in Canada, Austria, the Netherlands and other European or global locations described in the providers' Sentry subprocessor list (https://sentry.io/legal/subprocessors/) and Better Stack subprocessor schedule (https://betterstack.com/dpa/schedules).

Information processed outside Canada may be accessible to courts, law enforcement or other authorities under local law. We use contractual and other safeguards appropriate to applicable law. Our Privacy Officer at privacy@trymydays.com can answer questions and provide information about our foreign-service-provider policies and practices.

Personal information may be processed in Canada and in the countries identified above and may be accessible to authorities there under local law. We use contractual and other safeguards appropriate to applicable transfer rules. Where a provider acts on our behalf, we remain responsible to the extent applicable law requires. Ask the Privacy Officer for information about foreign-service-provider policies and safeguards, including for Alberta inquiries.

We may disclose information to other users or recipients as you direct through publication, sharing or exports; to providers supporting the Service under appropriate restrictions; to an authorized rights holder or affected person as reasonably necessary to resolve a complaint and as permitted by law; to competent authorities where legally required or permitted; or for establishing, exercising or defending legal claims. We assess emergency requests and do not provide unrestricted account access to anyone merely because they ask.

In a financing, merger, acquisition, restructuring or asset transfer, information may be reviewed or transferred with safeguards and subject to applicable legal conditions. A successor must handle the information consistently with applicable law. We provide any required notice; a transaction does not authorize unrelated uses without the permission or other basis required by law.

## 5. Current analytics, advertising and payments

The current Beta has no Ads, personalized advertising profiles, subscriptions or payment processing.

Optional Product Analytics. Product Analytics is off by default. If you choose to enable it, we collect account-linked information about how you use TryMyDays. This may include posts and Days shown or opened; videos played and watch duration; saves, follows, comments and profile opens; Try starts, step progress, skips and completion; results; creator draft and publishing steps; search length ranges, selected categories, filters and scope, and result counts; recommendation impressions and feedback; coarse account or user-selected locality; and related timestamps, session and analytics identifiers, app version, platform and environment. We use this information to understand activation and retention, measure and improve feature, creator and Try funnels, evaluate playback and search, improve local discovery, and personalize recommendations.

We do not put passwords, authentication credentials, tokens, signed media links, arbitrary request or response bodies, raw search queries, private report or moderation text, or the contents of your posts into Product Analytics. We do not use Product Analytics for advertising, cross-service tracking or sale. During this Beta, Product Analytics remains in our first-party systems and is not sent to an external analytics provider. Specific video and content history remains first-party.

Identifiable raw Product Analytics is kept for no more than 90 days and is removed or irreversibly deidentified sooner when it is no longer needed. Turning Product Analytics off stops new optional analytics collection when your choice is saved, clears pending optional events, and causes earlier identifiable Product Analytics to be removed or irreversibly deidentified through our deletion process. Turning it off does not delete content, saves, follows, comments, Try progress or other records needed to provide features you choose to use. We may retain statistics that have been aggregated and deidentified so they cannot reasonably be linked back to you.

Even when Product Analytics is off, direct product choices such as the creators you follow, items you save and Trys you undertake may affect what the service shows you because those records are used to provide the features you requested. We do not create or backfill separate optional Product Analytics events from those records while Product Analytics is off.

You can use TryMyDays without Product Analytics and change your choice at any time in Settings > Privacy > Product Analytics. Product Analytics is separate from crash diagnostics, operational and security logs, and any future advertising choice.

The Service is free and does not currently use advertising, subscriptions or payment processing. We do not currently use PostHog, and no Product Analytics is enabled by your diagnostics choice.

Mobile crash and performance reporting. If you allow crash and performance reports, TryMyDays uses Functional Software, Inc., doing business as Sentry, to receive limited crash, error, session and performance information. Reports may include exception and stack information, a bounded error code, device model and operating-system class, app environment and release when available, session start/end, and the names and durations of a limited set of technical interactions. Native reports also include a random identifier assigned to that app installation and may include an approximate city and region that Sentry derives from the connection IP. We use these records to diagnose crashes, repeated failures, performance and regional service problems.

We do not intentionally send your TryMyDays account ID, name, email address, device name, screenshots, replay, view hierarchy, console contents, request or response bodies, arbitrary URLs, content, video-viewing history or Product Analytics events to Sentry. We configure Sentry not to retain the source IP address in the event record. The app-installation identifier can link diagnostic reports from the same installation, but we do not intentionally link it to your TryMyDays account or use it for advertising or tracking. Native HTTP and network breadcrumbs are disabled.

Backend operational monitoring. We use Better Stack for structured backend operational logs and worker heartbeat or uptime monitoring. Authorized records are limited to timestamp, level, service, environment, release, bounded operational event name and bounded primitive technical fields. We do not intentionally send user IDs, content or media locations, request or response bodies, report or moderation text, credentials, tokens, Product Analytics payloads or arbitrary URLs to Better Stack. These records are used for service reliability and incident handling, not Product Analytics or advertising.

Our current website does not deploy advertising cookies or application analytics cookies. Hosting and edge services still process request information. Essential app storage supports sign-in and Service functions. We do not currently track your activities across unrelated services for targeted advertising, and do not sell personal information or share it for cross-context behavioral advertising. We therefore do not change that practice in response to a browser Do Not Track signal. Where a legally applicable opt-out preference signal is received, we honor it for any processing to which it applies.

If we activate analytics, additional observability, platform age signals, locality features, sponsorship measurement or payment services, we will update the relevant notices before the new processing begins and provide any legally required consent or choice. This statement does not mean those features are currently collecting data. Raw safety, legal-hold, deletion and security evidence is not used for ordinary product analytics or ad targeting.

## 6. Retention and deletion

We retain personal information for as long as reasonably necessary for the stated purpose, then delete or deidentify it unless law permits or requires further retention. Active account and Content records generally remain while needed for the account or publication. Incomplete signup information normally expires after 24 hours. A deleted username may be reserved for 30 days. Moderation records normally remain for 12 months after a case is finalized; privacy-request and Strong Removal records for 24 months after completion; and ordinary acceptance/download-rights evidence for 24 months after deletion is accepted.

General security records are retained for up to 90 days from the event that generated the record. Account deletion does not restart or extend that period. A specific legal requirement, valid legal hold, or other narrowly documented lawful preservation requirement may require limited records to be kept longer. Unlinked feedback is normally kept for 12 months.

Where an already-published lawful use continues, we may retain a minimal record of the relevant content grant while relying on it and for 24 months afterward. This does not authorize retention of a whole deleted account. Legal decision-record floors, breach records, safety reporting requirements, court orders or a specific dispute can require different periods. Records retained for these purposes are limited to what the purpose requires, with restricted access; pseudonymous records are not necessarily anonymous.

Account deletion defaults to Strong Removal of creator Content: creator audiovisual and TMD-supplied attribution/profile links are removed from dependent outputs under our control; lawful participant-only Results may remain. Ordinary Removal of an Original Day has different consequences for already-published Syncs. See Account and Data Deletion (https://trymydays.com/account-deletion/) and the Creator and Content Licence (https://trymydays.com/creator-licence/).

Deletion is a process across account systems, media outputs, providers, caches and backups. Backup copies may remain until normal rotation and are not restored to ordinary use without applying relevant deletion controls. Applicable statutory deletion requirements, including any rules for archived copies, take priority. We cannot erase copies another person independently controls. We do not promise instantaneous worldwide deletion or keep an active authentication account solely as an evidence archive.

Under the current configurations, Sentry error and event records normally remain available for up to 90 days, and bounded performance spans and metrics for up to 30 days. Better Stack operational logs normally remain available for up to 3 days and metrics for up to 30 days. We may remove information sooner where it is no longer needed or applicable law requires. Relevant incident, security or legal evidence may be retained separately under the periods and safeguards described in this policy. Provider backup and deletion handling remains subject to applicable contract and law.

A Sentry installation identifier is not intentionally mapped to a TryMyDays account. Account deletion therefore may not identify Sentry records by account. If you provide a diagnostic reference, or we can otherwise reasonably locate a report without creating a new identity map, we apply our ordinary verified rights-request process and available provider assistance. Otherwise, the report expires under the retention period above. We do not call these pseudonymous reports anonymous or promise immediate deletion from every backup.

## 7. Security

We use safeguards appropriate to the information and risks, including access controls and separation of ordinary use from restricted case handling. No system can guarantee complete security. Please secure your device and sign-in methods and report a suspected security issue to support@trymydays.com without sending unnecessary sensitive information.

## 8. Your requests and complaints

Depending on applicable law, you may request access, a copy, correction, deletion, withdrawal of consent, information about disclosures, or review of a decision on a privacy request. Where applicable, you may opt out of sale, targeted advertising or certain consequential profiling, or limit specified sensitive-data uses. Rights, lawful exceptions and response periods vary. We do not currently sell/share for targeted advertising or use consequential automated profiling.

Email privacy@trymydays.com, with support@trymydays.com as an alternative, or use the account-deletion control in the app. Tell us the request and enough information to locate the relevant account or material. We verify identity and any agent's authority proportionately using the available account and request evidence. The current Beta has no government-ID or selfie verification system. Do not send government identification or selfies to support. We respond within the applicable legal period and explain a lawful refusal, extension or available appeal. We do not discriminate against you for exercising a protected right. Fees apply only where law allows and after any required notice.

You may complain to the relevant authority, including the Office of the Privacy Commissioner of Canada, the BC or Alberta privacy commissioner, the OAIC where Australian privacy law applies, New Zealand's Office of the Privacy Commissioner, Singapore's PDPC, or the relevant US state regulator. Applicable local details are in the Country Addenda included below. Contacting us first is helpful but does not remove any right to complain directly.

## 9. Age and changes

Accounts are for people 18 and older. The current Beta is available only in Canada excluding Quebec, and the United States excluding Texas, Mississippi, Tennessee, Florida and all US territories; the District of Columbia is included. Australia, New Zealand, Singapore and other countries are not in this Beta. We do not knowingly provide accounts to children. If we learn an account is underage, we restrict ordinary access and address deletion or limited lawful preservation. A parent, guardian or affected person may contact us about a child's information even without an account.

We may revise this policy to reflect changes in the Service or law. The effective date identifies the current version. We provide material-change notice and obtain additional consent when law requires. An update does not retroactively authorize an incompatible use of previously collected information.

## 10. Country Addenda for this Beta

## United States

Where an applicable state privacy law covers our processing, you may exercise the rights described in the Privacy Policy, including authorized-agent requests and applicable appeals. To appeal a denied request, email privacy@trymydays.com or support@trymydays.com, identify the decision, and say that you seek an appeal. If an appeal is denied, we provide the applicable regulator complaint route as required. We do not sell personal data, use cross-context behavioral advertising, or conduct consequential automated profiling in the initial Service.

For California, our Privacy Policy describes the categories collected, sources, purposes, recipient categories and retention. Where the CCPA applies, rights may include access/portability, correction, deletion, and opt-out or limitation rights applicable to our actual processing, without unlawful discrimination. A right may be subject to lawful verification and exceptions. Our current no-sale/no-sharing practice also applies to information of people under 16; we do not knowingly admit under 18 accounts. For Rhode Island, no third party is currently identified as a recipient to whom we sell or may sell personal data under an active sale arrangement because no such arrangement exists; a new practice requires an updated notice before activation.

For New Jersey consumers, the Terms' warranty exclusions, damages exclusions, cap and indemnity apply only to the extent New Jersey law permits. They do not exclude statutory consumer remedies or liability that such law makes non-excludable. For all US users, legal minority and contractual-capacity protections remain applicable even if TMD's account-age requirement is met.

## Canada excluding Quebec

The Service is not offered in Quebec. Applicable federal and provincial privacy rights may include access, correction, withdrawal of consent subject to legal/contractual limits, and a complaint to the responsible commissioner. A deletion request is assessed against the purposes and retention obligations applicable to the information; this policy does not invent a universal statutory erasure right. Our Privacy Officer can explain foreign-service-provider policies and practices, including for Alberta residents.

The Terms do not waive a consumer's statutory remedies, a non-waivable local court right or an applicable privacy right. Being 18 does not eliminate contractual-minority protections that apply in a province or territory. No compulsory arbitration or class-action waiver is imposed.
TryMyDays Don’t just watch. Try it.

Legal

  • Terms of Service
  • Privacy Policy
  • Community Guidelines
  • Creator and Content Licence
  • Copyright and IP

Safety and privacy

  • Safety Center
  • Privacy requests
  • Recording removal
  • Intimate imagery removal
  • Child safety

Account

  • Account and data deletion
  • Support

TryMyDays is for adults 18 and older. Support: support@trymydays.com. © 2026 TryMyDays.