TryMyDays Privacy Policy

Effective: 2026-10-20 · Version: TMD-BETA-2026-10-20-1

Geonwoo Park, doing business as TryMyDays (“TMD”, “we”, “us”), is responsible for the personal information described here. Our Privacy Officer is Geonwoo Park, reachable at privacy@trymydays.com or support@trymydays.com. This policy covers the TryMyDays app, related website and support operations during the Closed Beta.

Account, eligibility and location

We collect your account email, sign-in provider identifiers and information supplied by your chosen sign-in provider, authentication and session records, and the profile information you provide. Your profile may show your username, display name, avatar, biography, public city, approved external creator link, selected pinned posts and social counts to eligible signed-in members, subject to access and block controls.

The Service is for adults aged 18 or older in the supported Canadian and US regions listed in our Terms. We ask you to enter your date of birth and country and province, territory or state of residence. These eligibility fields are private. We use them to check eligibility, apply regional rules and handle corrections. Correction records can include the previous and new values and the time and policy applied. We do not require a government ID or selfie in the ordinary eligibility flow and do not infer residence from GPS or your connection IP. We do not represent that every member’s identity or age has been independently verified.

You may choose an optional private Home city for local discovery, put a city in your public profile, or select a locality for a Day, Story or Result. A Day or Story location is shown with the relevant content; the current Result locality field is visible only to its owner. These are user-selected labels. The app does not request GPS location or run background location tracking. A recording, caption or place label may itself reveal where someone is or has been. Providers may also receive network information when you connect.

Content, Tries and social features

We process the photos, video, audio, text, captions, instructions, categories and other content you provide, along with upload, rendering and publication information. We use camera, microphone and photo access for the features you initiate and the permissions you grant. Creator and participant source clips stay in private storage. We create the finished renditions needed for your posts, Results, Stories and authorized exports. A public finished rendition does not give other members access to your raw clips. Raw uploads may contain embedded metadata before processing; metadata removal from a finished rendition is not a claim that the original upload contained no metadata.

We store your Tries, Step progress, explicit skips, completion states, source-version references, scheduling/timezone information and Results so those features work. Saves, Likes, Follows, comments, replies, blocks, mutes, pins and related settings support the social features and access controls you use. A Day’s creator may receive a private Activity notification identifying a member who tried that Day; this does not make the participant’s private clips or private Result public. We store in-app relationships, but do not upload your phone address book.

Original Days are public within the Service’s eligible, signed-in audience. Results may be public or private to their owner. “Everyone” remains subject to sign-in, eligibility, source availability and block or moderation controls. Eligible members may reshare an active public Original, Sync or Chill to a Story where the applicable content grants authorize that use. The reshare identifies the sharer and source and references the source rendition; it cannot bypass a private or removed source. See the Creator and Content Licence for the rights and removal rules.

Search terms and filters are sent to our systems to return results. The Beta Product Analytics events described below can associate a shown or opened search result with a random search-request identifier; they do not include the search text. This is distinct from a stored list of raw search queries. Network, security and provider logging are described below.

Public link previews

In the current signup flow, public link previews are on by default when you complete signup. An older app version may still ask you to choose ON or OFF during signup. You can turn them off or on later in Settings. Existing accounts keep their recorded choice. An older account without a recorded account-wide choice does not automatically enable new previews; an earlier finite grant may still serve an eligible preview already approved under that grant. When on, your eligible public Profile, Days, Results and Stories may be represented outside the app by your name, username, content type, approved cover or profile image and limited title information. The setting covers the current and future content you own described there. These previews may be fetched by people who are not signed in and by messaging services and their link-preview crawlers. A preview is a still image, not access to private clips or automatic video playback. Sharing a link and allowing its public preview are separate choices.

We check current eligibility before serving new preview information or images. Private or restricted content, deleted or hidden content and expired live Stories do not receive identifying public previews. An independent Chill preview does not reveal an unavailable Original. Turning public previews off stops new identifying previews. These controls do not guarantee that another service will remove an image it already fetched or cached; a previously public preview may remain in a message or external cache after you turn the setting off, remove content or a Story expires. Access inside TryMyDays continues to follow the Service's sign-in and content-access rules. Member-specific blocks apply inside TMD; an anonymous preview request does not identify its viewer.

We retain minimal records of the preview setting, including the new-account default, later ON/OFF choices and the notice version when a choice is made, for the account's lifetime and for 24 months from an accepted account-deletion request, subject to applicable legal preservation requirements. This rights-permission evidence is separate from Product Analytics consent.

Stories, Archives and Highlights

A live Story normally expires after 24 hours. New Stories use the Everyone audience described above; older Followers-only Stories retain their stored audience. Story owners can see viewer identities and completion information for a limited period. Viewer identity records are deleted seven days after the Story ends, even if the Story remains in an Archive or Highlight. An aggregate view count may remain.

An owner’s private Story Archive can keep the Story and its media until the owner removes it, deletes the account, or the source becomes unavailable. Highlights make selected archived Stories visible through the profile until removed, subject to current access and source checks. A source-backed Story cannot use an Archive or Highlight to retain access to removed or private source content. Standalone Story media not kept in an Archive is scheduled for cleanup seven days after the Story ends; its Story record is scheduled for cleanup after 30 days. Deleting an archived Story starts the corresponding cleanup process. Reports can preserve a restricted evidence copy under the rules below.

Story replies and reactions use private Messaging and can be turned off by the Story author. Muting a Story changes your own Story tray.

Messaging

We store one-to-one and group messages to provide the conversations you use. A group has up to 16 members. Message information includes text, photos, videos, voice messages, in-app post, profile, Story and Step references, the sender and conversation, replies, reactions, read status, edit history and conversation settings. For a group, we also store its name, current and former membership, and when members join or leave. Every current eligible group member may invite people within the group limit; members cannot remove another member or assign a member Admin role. Typing indicators are shown to the conversation’s current members and are not kept as message content. Mutual follows can message directly; other one-to-one messages use the recipient’s message-request settings. Photos, videos, voice messages and calls are available in a one-to-one conversation only after its message request is accepted. Someone added to a group sees messages sent after they join. In accepted one-to-one and group conversations, the current app records each member’s read position when they actually view eligible messages or successfully send a message, and shows it to current authorized participants. An older app version may not advance the visible position merely by viewing during the transition; successful sends still advance it. Sending a message counts as reading the preceding accessible conversation through that send, but does not mark later messages as read. Push delivery alone does not mark messages as read. Read receipts cannot be turned off. Message Requests do not show read receipts.

Message photos, videos and voice messages are kept in private storage. We convert each upload for delivery and remove embedded metadata during that conversion; the original upload is deleted after processing. Before issuing a delivery link, our servers check that the viewer can currently see the message, and each link expires within five minutes. A link already issued can keep working until it expires. Sending media in a message does not publish it.

In a shared group, a Block hides each person’s messages from the other; it does not remove either person from the group. You can leave a group at any time. Leaving a group ends your access to it; messages you already sent remain visible to the other members unless they are unsent, removed or deleted with your account. Platform moderation may separately end a member’s access.

You may edit a text message within 15 minutes, up to five times, or unsend a message within one hour. Prior edited text is stored with the message. Unsend removes the live content, related references, reactions and edit history, leaving a tombstone. Delete for me hides an individual message from your view. Clear conversation hides earlier messages only from your own view while keeping the conversation in your Inbox; it does not delete other members’ copies or end membership. Messages have no automatic short retention limit and normally remain until the applicable message, moderation or account-deletion action removes them. Account deletion removes the deleting member’s authored message contents and edit histories from the live conversation, including other members’ views.

A message report preserves the reported message and up to 19 preceding messages. A conversation report can preserve up to the latest 30 messages, with relevant edit history. This report copy does not change later. For a reported message, an authorized reviewer may separately request a case-linked, audited view of up to 10 messages before and 10 after it in the same conversation. That limited context can include messages sent after the report and is not part of the original report copy. A reviewer may open a separate moderation case for one message in that context without another member filing a new report. Photos, videos and voice messages in a report copy or authorized context view are available only while retained and may be held from deletion when attached to a moderation case. Review access is restricted to the particular case, checked and recorded. A restricted report or case has additional access controls. A report or case copy may remain after a message is unsent or an account is deleted. Case-linked context copies and access records follow the moderation-evidence retention and preservation rules below; expiry of a viewing link does not erase retained evidence. Private means limited audience. Messages and calls are not end-to-end encrypted.

Calls

You can make one-to-one voice and video calls with the other member of an accepted conversation who is allowed to call you. Group calls are not available in this Beta; group messaging remains available. Call audio and video are relayed in real time by Stream.io, Inc. (“Stream”). Stream receives a random calling identifier for your account, not your name, username, profile image or messages. TryMyDays does not record or transcribe calls. Stream also receives technical call-quality information such as SDK/OS/device details, connection and audio/video performance, and session information to operate calls. This is separate from optional Sentry reports and Product Analytics.

A call appears in its conversation with its outcome and duration. Our call record contains the conversation, who started the call and who was invited, whether it was a voice or video call, ring, answer, join, leave and end times, and the outcome, such as completed, missed or declined. Call records are kept with the conversation and are deleted with it. When an account is deleted, its call participation records are deleted and it is no longer identified as a call’s initiator.

Incoming calls on iPhone use Apple’s VoIP push service and CallKit. An incoming call shows the caller’s display name and carries internal call and conversation identifiers; it never contains a message body, media link or Stream credential. A missed call can send an ordinary notification with the caller’s display name.

TryMyDays cannot place 911 or other emergency calls. For an emergency, use your phone’s emergency calling or contact local emergency services.

Activity and notifications

We keep private Activity items about relevant follows, Tries and publications for up to 90 days after their last update; hidden items are removed after seven days. Push notifications require device permission and use your account-linked Apple push token and notification preferences. Incoming calls use a separate account-linked Apple VoIP push token for each signed-in device; signing out revokes it. You can manage the available notification categories and device permission separately.

Push delivery uses limited information such as a name, notification title and an in-app destination. We do not put private message bodies or media URLs in push payloads. This Beta does not send marketing push notifications. Push and VoIP tokens stop being used for delivery after 60 days without being seen and are removed after 90 days without being seen or 30 days after revocation. Settled delivery-job and delivery-failure records, including call notification jobs, are kept for seven days.

Recommendations on Home

To choose and order posts on Home, TryMyDays collects and uses your activity in the app: posts shown to you, what you watch or skip, Days you open or share, posts you save, accounts you follow, and Days you try. Personalized recommendations are separate from Product Analytics. You can turn them off in Settings → Privacy → Personalized recommendations.

Personalized recommendations are on by default after the recommendation notice is completed, unless you turn them off. We do not collect optional Recommendation viewing and interaction signals while that notice is pending. Continue acknowledges the notice; it is not an express-consent button. Manage provides access to the control before you proceed. The information is used to choose posts, estimate interests, reduce repetition and assess item quality for Home. It is not used for advertisements, Product Analytics, general-purpose model training or ordinary business reporting.

Turning personalization off stops the optional Recommendation signal collection, removes the operational viewing-signal history and exposure history, and retires Personalized Home sessions. It does not delete your core Saves, Follows, Likes, Tries or posts. Home falls back to a non-behavioral ranking that uses follows, public Result relationships, recency, variety and recent served-opportunity counts. This is still ranked Home; it is not a promise of chronological order or of no personal information use.

If you turn personalization back on, new viewing-signal and exposure history starts from that point. Existing Saves and Tries can again contribute to recommendations, including eligible activity from the preceding 365 days. That lookback does not impose a 365-day deletion deadline on your core Saves or Try history.

Operational Home sessions are kept for eight days, raw Recommendation signals for up to 90 days from the activity, and exposure history for a 30-day horizon. Item-quality calculations use a rolling 30-day window. Interests inferred for ranking are computed during a build rather than kept as an ongoing operational taste profile. Intermediate quality records can still be linked to an individual through their source event. Turning the feature off or deleting the account removes those source records, with affected quality totals refreshed through the scheduled rebuild, normally within 24 hours. A per-post total is not necessarily anonymous about its creator.

Restricted Home decision records

Separately, we preserve limited records of ranked Home decisions for privacy access and applicable legal obligations. These include baseline ranked Home as well as Personalized Home, including a baseline decision made while personalization is off. The record can include the decision time and configuration, the ordered set of posts selected for the ranked part of Home, relevant relationships and block state, Save/Try information, used viewing and exposure information, and inferred interests used in that decision. It is a decision record, not a recording of everything you do in the app.

These records are kept for one year after the recorded decision use of the personal information, or longer when a specific preservation duty or legal hold requires it. Information reused for a later qualifying decision has a retention period for that later use. Merely reading a legal record does not restart the period. A restricted copy can remain after you turn personalization off or delete your account. It cannot be read by Recommendation, Product Analytics, advertising, model-training, business-reporting, mobile or ordinary product API systems. Authorized privacy or legal review is restricted and audited; information about other people is protected when responding to access requests. Expired records are deleted when no applicable hold or preservation duty remains.

Optional Product Analytics

Product Analytics is off unless you choose to share usage. It is account-linked and separate from Personalized recommendations and crash/performance reports. During this Beta, it stays in our first-party systems and is not sent to an external product-analytics provider.

It records eight kinds of activity: a post shown, a Day opened, a tap to start a Try, a Try started, a Step completed, a Step skipped, a Try completed, and a Result published. Associated data includes account and event identifiers, time, app version and environment, the relevant post/Day/Try/Step identifiers, screen or source, and bounded progress or publication details. A shown/opened result can include a search-request identifier without the search text. Configured capture information can distinguish camera recording from imported media; it does not include the media itself.

We use these records to understand feature use, Try progress and completion, and usage over time so we can improve the app. This Beta’s Product Analytics does not collect video-watch duration, Save events, separate search-submission events, creator-flow events, locality events, message bodies or uploaded media. A similar activity can separately be used by Recommendation when that independent setting permits it; Product Analytics does not authorize Recommendation use.

Raw Analytics records and account-derived reporting records have a 90-day limit measured from their relevant activity. A settled delivery/deduplication record expires at the earlier of 30 days after settlement or 90 days after the activity; pending records expire after 90 days from the activity. Turning Product Analytics off or deleting your account removes account-linked Analytics records sooner. Aggregate reporting applies small-group suppression. We do not treat retained account-linked source data as anonymous merely because a report shows totals. Change your choice in Settings → Privacy → Product Analytics.

Optional crash and performance reports

Crash and performance reports are off by default and are controlled separately on each device. If you allow them, the app sends limited technical error, crash, session and interaction-timing information to Sentry. Reports can include app version, operating system and device details, technical stack information and a random identifier for the app installation or session. They are not described as anonymous merely because they do not use your TMD account ID.

The diagnostic configuration is designed to exclude account names and email addresses, uploaded content, private message contents, screenshots, session replay, request/response bodies and viewing history. The connection itself necessarily exposes network information to the receiving service. Sentry processing is in the configured US project. Diagnostic event retention is 30 days for error events and event attachments under the current Developer plan. Sentry assigns retention when data is ingested; a later plan change does not change the retention already assigned to existing data. Retention expiry ends access to that data and does not promise immediate erasure of every provider storage copy.

Turning reports off stops future optional reporting on that device and clears queued local reports. Reports already received by Sentry expire under the project’s retention settings; we do not have an account-linked deletion lookup for them. This setting does not turn off the necessary server reliability, security, deletion and legal-audit records described in this policy.

Reports, support and necessary operations

We receive support and privacy correspondence, moderation reports and information from affected non-members, rights holders or authorities. Case evidence may include relevant content, limited message context, contact information and sensitive information needed to address that particular report. We limit its use and access to the case, safety, legal obligations and permitted claims handling. We do not use raw safety or legal evidence for ordinary Product Analytics or advertising.

We process authentication, request/network, abuse-prevention, security, service-error, worker and delivery information needed to operate and protect the Service. Application operational logs are designed to exclude member content and account identifiers; hosting and network providers can separately process request metadata. These operational functions are not optional Product Analytics. We also record document acceptance, purpose choices, notices, content permissions and removal/deletion actions to establish what happened and which version applied.

Providers and disclosures

Our service providers include Supabase for authentication, databases and storage; Railway for media and backend workers; Cloudflare for web delivery, DNS and email routing; Resend for authentication email delivery; Stream.io, Inc. for real-time call audio and video transport; Sentry for optional diagnostics; and Better Stack for operational logs and monitoring. Our support and privacy mailbox provider is Google (Gmail). Apple provides native push delivery, sign-in and distribution services; Google provides sign-in where selected. Apple and Google also handle information under their own policies. We use no Expo push relay. Suno was used for the founder-supplied music catalogue; it is not a runtime recipient of members’ uploads for this Beta.

When safety-alert delivery is enabled, we use Discord to deliver limited safety alerts to our operator in restricted channels. A safety alert may state its urgency, a fixed description of the report or moderation event, what the operator should check, a link to the restricted Founder Admin, and an opaque alert reference. The reference can be linked to the underlying alert inside TryMyDays. We do not send the report text, member names or account identifiers, media, or case evidence in these alerts. Discord processes and retains the alert messages under its own terms, including in the United States and potentially other countries; deleting a message may not immediately remove all provider-held copies.

When safety-alert email is enabled, we also use Resend to send limited safety-alert email to our operator as a secondary notification route, in addition to authentication email. These safety emails contain a generic operational notice and an opaque alert reference, rather than report text, member identities, media, or case evidence. Resend and the operator's email provider process the sender and recipient addresses, message content and delivery information. The reference can be linked to the underlying alert inside TryMyDays. Processing can occur in the United States and other provider processing locations. Provider logs, mailbox copies and backups may remain under their applicable retention rules after an alert is acknowledged or a delivered message is deleted.

The configured processing locations for core hosting, workers, support email and operational services are the United States for configured core hosting and operational storage: Supabase in North California (AWS us-west-1), Railway in California (us-west2), Better Stack in US West, and Sentry in its US organization; Resend stores authentication-email data in the United States. These hosting and storage locations do not limit all processing to the United States. Cloudflare web delivery, DNS and email routing operate through its global services, and Google (Gmail) may process support correspondence on servers around the world. Provider support, routing and other permitted processing may occur in additional countries; no exclusive US-only or exhaustive country list is asserted. Stream processes call audio, video and call signalling in Canada for the configured application data region, with real-time media routed through Stream’s global edge network and other service processing in the United States and locations used by Stream’s subprocessors. Information may be processed outside your province, state or country and may be accessible to authorities in the processing country under its laws. We require safeguards appropriate to the provider’s role and applicable law. Our Privacy Officer can explain foreign-service-provider policies and safeguards, including for Alberta inquiries.

We disclose information to the audience and recipients you select through Service features; to providers as needed for their functions; to authorized people handling a rights complaint where necessary and lawful; to authorities when legally required or otherwise lawfully justified; and where needed for legal claims. A request from an authority is not itself permission for unrestricted access. Complaint procedures may require sharing a notice with the affected uploader or complainant; safety and privacy limits still apply.

A financing, acquisition, restructuring or business transfer may involve limited disclosure or transfer under legal conditions and safeguards. It does not authorize unrelated use of your information or expand content licences. We give any legally required notice.

We do not sell personal information, share it for cross-context behavioral advertising, use cross-app tracking for advertising, or run advertising in this Beta. No external Recommendation or product-analytics provider is activated. Essential app storage supports authentication, playback and feature operation. Legally applicable opt-out preference signals are honored for the processing to which they apply; the current no-sale/no-sharing practice applies regardless of a browser Do Not Track setting.

Other retention and deletion periods

Active account, core social and published-content records generally remain while needed for the account, feature or publication. Day drafts expire after 14 days of inactivity. Private source media is retained for its authorized content/rendering lifecycle, rather than under the 90-day Analytics period. Deleting an Original Day moves it to your owner-only Trash. Its source clips, finished rendition and covers are retained so you can view and restore the same Day; Trash has no automatic expiry. The Day is unavailable to other members and cannot accept new Tries or Results, but already-published lawful Syncs keep their creator material and attribution. Strong Removal permanently removes the Day from Trash and starts the applicable media cleanup. Surviving participant posts are presented as Chill without the creator contribution or identity; restricted internal records retain the original Sync provenance. Ordinary message storage and Story retention are described above. Message photos, videos and voice messages remain while their message is available and are deleted after it is unsent or removed, or after the sender’s account is deleted, unless a report or legal hold requires a restricted copy; an upload that is never sent is deleted after 24 hours. Call records follow their conversation. Stream keeps its own records of calls under its retention: Provider-controlled call, signalling, session, quality, security and operational records follow Stream’s applicable service and data-processing terms. TMD does not set or promise a fixed deletion period for those records; deleting the TMD calling-identifier link is not provider-side deletion. A message waiting to be sent from your device is kept on that device for up to seven days so it can be retried. It remains there after sign-out until it is sent, discarded or expires, is removed when the account is deleted on that device, and may be included in your device backup.

Ordinary moderation evidence is kept for 12 calendar months after the case is finalized. Minimal privacy-request, account-deletion and Strong Removal records are kept for 24 calendar months after completion. Applicable consent evidence is kept for 24 calendar months after the covered processing ends; post-deletion contractual-acceptance evidence is kept for 24 calendar months after deletion is accepted. A minimal content grant still supporting a lawful surviving use can be retained for that use and for the applicable evidence period afterward.

General security evidence normally has a 90-day period from the recorded event. Where Canadian breach-record requirements apply, the required record is kept for 24 months after determining that a breach occurred. This does not make every security event a breach or authorize retaining every security log for two years.

Specialized intimate-image, child-safety, copyright, emergency and legal-process records follow their specific legal requirement or limited case purpose. NCII, copyright and privacy case metadata normally has a 24-month period from closure; intimate images and other case media are kept only as long as needed for the action or an actual preservation requirement. Required child-safety preservation and destruction periods take priority over ordinary case schedules. A legal hold has a defined scope and is reviewed; it is not permission for ordinary product reuse.

Optional deletion feedback is used to understand problems and improve the Service and is kept for 12 months after submission. This is feedback you choose to submit, separate from the automated Product Analytics setting. It has no account or deletion-request link, but text you volunteer can still identify you. A deleted username is reserved for 30 days. Encrypted material used to revoke Apple sign-in access has a seven-day operational limit and is deleted sooner after successful processing.

Support correspondence and provider logs/backups follow these configured schedules: Google (Gmail) stores support mailbox messages until they are deleted. Gmail automatically permanently deletes messages from Trash after 30 days, or earlier if Trash is emptied. Google's general deletion process usually takes about two months, may take longer, and encrypted backups can retain data for up to six months; security, legal and service-continuity exceptions can extend retention. These are provider policies, not a separately verified mailbox-specific log or backup expiry setting. Cloudflare Email Routing forwards inbound support email to Gmail; its routing activity and analytics include message metadata and are retained for the past 31 days under its published Email Service policy. No independently established fixed expiry for other Cloudflare or Gmail provider logs/backups, or guarantee about provider-controlled restoration, is asserted. Better Stack Production retains operational logs for three days and metrics for 30 days. Supabase Production has daily physical database backups with PITR off; database backups do not restore Storage objects. The accepted database recovery point is at most 24 hours and target recovery time at most four hours; these are recovery objectives, not data-erasure deadlines.. Statutory requirements take priority. Backup restoration must reapply deletion controls before removed data is returned to ordinary service. Expiry starts the relevant bounded cleanup process; we do not promise instantaneous erasure of every storage copy.

Account deletion removes your account and own posts, applies Strong Removal to your creator material, revokes sign-in access and removes the authentication identity after the required cleanup and provider-revocation stages. It also removes your group memberships, push and VoIP tokens and the link between your account and your Stream calling identifier, and queues your message media for deletion. Removing that link does not by itself delete records Stream keeps under its own retention. Lawful participant-only Results can remain, presented as Chill without your creator footage, voice or TMD-supplied creator attribution/profile links. Account deletion is irreversible and does not move your Days into restorable Trash. Limited evidence and legal-preservation records can remain for the periods above, with protected subject references instead of an active account. We cannot erase copies independently controlled by another person. See Account and Data Deletion (https://trymydays.com/account-deletion/).

Your choices, requests and complaints

You can manage the separate Recommendation, Product Analytics, diagnostics and notification controls in Settings and correct your private eligibility details through the available account controls. Settings changes take effect on this device immediately where supported; the app reports an account update as pending until the server receives it, after which other devices follow the account setting. Required processing for the features you use, security and legal obligations is distinct from those optional choices.

Contact privacy@trymydays.com to request access, correction, deletion, a portable copy, withdrawal of consent, or an applicable restriction or appeal. Available statutory rights depend on your location and the law covering the particular processing. Canada’s access and correction rights do not create an unlimited right to erase information still lawfully required. Where applicable US state privacy law applies, we honor its access, portability, correction, deletion, opt-out, authorized-agent and appeal rights without unlawful discrimination. Home ranking is not used to decide eligibility for credit, employment, housing, insurance or another similarly consequential service.

We verify requests proportionately and explain applicable exceptions, timing, extensions or reasons for a refusal. Do not send passwords, sign-in codes, identity documents or private recordings unless we arrange a necessary, secure way to receive specific evidence. You may make a request even if ordinary account access is restricted or your region is unavailable. To appeal, reply to the decision or email privacy@trymydays.com stating that you seek an appeal. We provide any applicable regulator complaint route. You may also contact the Office of the Information and Privacy Commissioner for British Columbia, the Office of the Privacy Commissioner of Canada, the Alberta Information and Privacy Commissioner, or the appropriate regulator for the matter.

A person without an account can report a privacy or recording concern through Privacy and Unauthorized Recording Reports (https://trymydays.com/privacy-recording-removal/). We provide additional notices about information received from others when required by law. Access responses may withhold or sever another person’s information, privileged information or protected safety/investigation information where law requires or permits.

Safeguards and changes

We use access controls, private storage, limited serving permissions and separated operational, optional and legal-evidence systems appropriate to the information. No system is perfectly secure. Report a concern to privacy@trymydays.com or support@trymydays.com.

The Service does not knowingly admit accounts for people under 18. Report an underage account or child-safety concern through our safety channels; an adult-only account rule does not prevent a child or representative from reporting harm. We update this policy when practices change, identify the version and effective date, and provide notice and any additional consent required before a new use starts. Agreeing to the Terms is not blanket consent to every personal-information use.