Help Center

The Dreamin' Roomie Connect (TDRC) is a platform that helps people attending the same conference or event find compatible roommates so they can share accommodation costs. TDRC provides event-based profiles, listings, roommate preferences, requests, matching, messaging, and safety tools to help users connect and make their own accommodation arrangements.

Create an account, verify your email and identity, complete your profile and roommate preferences, then join an event. You can browse or create listings, review potential roommates, send or receive a roommate request, and become matched when a request is accepted. Once matched, you can use TDRC messaging to coordinate your stay. TDRC facilitates the connection; users remain responsible for their own travel, hotel reservations, payments between roommates, and final roommate decisions.

TDRC is intended for adults who are attending an event supported by the platform and want to find someone with whom to share accommodations. Users must meet TDRC's eligibility requirements, including the minimum age requirement and required account verification steps.

Yes. You must be at least 18 years old to create or use a TDRC account.

Select Create Account and follow the registration process. You will need to provide the requested account information, verify your email address, and complete the required profile and verification steps before using features that require a verified account.

Yes. TDRC supports social sign-in where available, including Google sign-in. You may also create an account using an email address and password.

Email verification confirms that you have access to the email address associated with your account. It helps protect accounts, reduces fraudulent registrations, and allows TDRC to send important account, request, match, safety, and event notifications to the correct address.

TDRC requires identity verification as a trust and safety measure. Verification helps reduce fraudulent or duplicate accounts and gives members additional confidence that another profile is associated with a real person. Identity verification is not a background check and does not guarantee that another user is safe, trustworthy, or compatible.

Follow the identity verification instructions shown during onboarding or in your account. You will be asked to submit the required verification information or identification for review. Your account will show when verification has been approved or if additional action is required.

If your identity cannot be verified automatically or during the initial review, you may be asked to provide additional information or resubmit your verification. Certain features, including creating listings or sending roommate requests, may remain unavailable until verification is completed.

No. TDRC allows one account per person. Creating duplicate accounts may result in the duplicate account being restricted or removed.

Open your profile and provide the required information, including your name, profile photo, date of birth, gender identity, hometown, company, title, About Me information, and roommate or sleep preferences. Complete all required fields so TDRC can display your profile and determine whether you are eligible to use matching features.

Other users may see the profile information TDRC designates as public or match-visible, such as your name, photo, hometown, company, title, About Me information, and roommate preferences. Sensitive account, authentication, verification, and private contact information is not intended to be displayed publicly. Visibility may also depend on whether another user is participating in the same event or is matched with you.

Before contacting a potential roommate through TDRC, complete your required profile information, verify your email and identity, and satisfy any event-access requirements. TDRC uses roommate requests rather than unrestricted pre-match messaging, so direct messaging becomes available after a roommate request is accepted and a match is created.

An event is a conference, meetup, convention, or similar gathering supported by TDRC. Listings, roommate searches, requests, and matches are organized by event so members connect with other people attending the same gathering.

Open the Events area and browse or search the available events. Select the event you plan to attend to view its details and available roommate activity.

TDRC initially focuses on Salesforce and community-led conferences and events, with the platform designed to support additional events over time.

Select the event and follow the available unlock process. Each beta tester receives an individual promo code tied to their account email. The code must be redeemed on the Billing page by December 31, 2026 at 11:59 PM Eastern Time. Once redeemed, its three Event unlocks do not expire. Other event access requires the applicable paid event unlock or plan.

The event may not have been added yet, may be outside the currently supported event set, or may not yet be open for roommate activity. If event submissions are available, you can request that TDRC review the event for inclusion.

Yes, where event submissions are enabled. Submitted events enter a review process before they are added to TDRC.

TDRC may add events from supported event sources and user submissions. Events can be reviewed for relevance, legitimacy, dates, location, and whether they are appropriate for roommate matching before publication.

Yes, subject to your plan or event-access limits. Your listings, requests, matches, and messages remain associated with the event where they were created.

Event access is tied to the event and the applicable TDRC access rules. Event content may remain available in a limited or read-only state after the event for recordkeeping, safety, and support purposes.

Active event activity is closed when appropriate after the event. Historical records such as listings, matches, and messages may remain available in a read-only state and may be retained according to TDRC's retention policies.

You may stop participating in an event, but existing requests, matches, reports, or retained records may still be preserved according to TDRC's product and retention rules.

A listing describes the accommodation arrangement you are offering or seeking for a specific event. It includes the dates, budget or expected cost, room and bed details, preferences, and other information potential roommates need to evaluate the opportunity.

Offering Space means you already have, or plan to provide, accommodation space and are looking for someone to share it. Looking for Space means you need a place to stay and are looking for someone who has suitable accommodation available.

Open the Listings area for the event, choose whether you are Offering Space or Looking for Space, complete the required accommodation and preference fields, review the information, and publish the listing.

Listings can require your check-in and check-out dates, budget, expected total cost, room type, number of beds, smoking and alcohol preferences, accessibility information, and whether you are offering or seeking accommodation space.

Dates help TDRC and other members determine whether your stay overlaps with another person's plans. A potential roommate may be attending the same event but staying for different nights.

Enter the amount you realistically expect to spend for your portion of the stay. Be clear about whether the amount reflects your share rather than the full room cost, and use the listing's expected-total-cost field where applicable.

Expected total cost is the estimated full cost of the accommodation arrangement for the stay described in the listing before the cost is divided among roommates.

Use the listing fields to describe the accommodation and available sleeping arrangement accurately. Enter the room type and the number of beds that are actually expected to be available.

These fields help members communicate expectations about smoking and alcohol in or around the shared accommodation. Choose the options that accurately reflect the arrangement you are comfortable with.

Use the available accessibility fields or listing details to describe needs or accommodation features that are relevant to your stay. Discuss important accessibility requirements directly with a potential roommate and independently confirm them with the hotel or property, because TDRC does not verify hotel accessibility.

Yes, while the listing remains editable. Update it promptly if your dates, costs, accommodation details, availability, or preferences change so other members are not relying on outdated information.

Where the hide option is available, you can remove a listing from active discovery without erasing the retained record. Hidden listings may still be kept according to TDRC's retention requirements.

Use the available close or hide action for the listing. TDRC may retain the underlying listing record after it is no longer publicly active for safety, support, compliance, and recordkeeping purposes.

A listing may not be visible if your account or identity is not fully verified, the listing is incomplete, hidden, closed, associated with an inactive event, affected by a match, or restricted by a moderation or account status.

Once you have an active match for the event, the listing should no longer function as an open invitation for additional roommate requests. Its historical record may remain available or retained.

TDRC's current product rules call for closed or hidden listing records to be retained for five years.

Offering Space indicates that you have accommodation space available, or are arranging accommodation space, and want to find another event attendee to share the stay and associated costs.

If TDRC requires booking evidence for an Offering Space listing, you will need to provide acceptable evidence of the accommodation reservation before the listing can receive the applicable verification or approval status.

Booking evidence helps reduce misleading or fraudulent Offering Space listings by providing evidence that the accommodation being offered is connected to an actual reservation. It does not guarantee that the reservation will remain valid or that the person offering it will fulfill the arrangement.

Provide the reservation information requested by the booking-evidence workflow, such as enough information to associate the reservation with the accommodation, dates, and person submitting it. Follow the upload instructions shown in TDRC and avoid providing unnecessary sensitive information.

Remove or obscure information that TDRC does not request and that is not needed to review the reservation, such as full payment-card numbers, account passwords, or other unrelated sensitive data. Do not hide information TDRC specifically requires to review the evidence.

Booking evidence should be limited to authorized TDRC personnel or systems that need it for verification, safety, support, or compliance purposes. It is not intended to be publicly displayed to other users as part of your listing.

You may be asked to provide clearer or additional evidence. The listing may remain unverified or unavailable for matching until the required review is completed.

Yes, but update the listing immediately. If the accommodation change affects previously reviewed booking evidence, TDRC may require new or updated evidence before treating the listing as verified.

Update or close the affected listing as soon as possible and notify any current match if applicable. Do not continue representing canceled accommodation as available. If you obtain a replacement reservation, update the listing and provide new booking evidence if required.

Join the event, then browse the available roommate profiles and listings associated with that event. Review each person's profile, accommodation details, and compatibility information before deciding whether to send a roommate request.

TDRC compares relevant profile and roommate-preference information, such as sleep schedule, noise, lighting, room temperature, and other matching factors supported by the product. Compatibility information is intended to help you compare potential roommates; it is not a guarantee.

Compatibility information summarizes how closely selected profile and roommate preferences align. It is decision-support information only and should be considered together with the person's profile, listing, communication, and your own judgment.

No. A high compatibility result only reflects the information and preferences evaluated by TDRC. It does not guarantee personal compatibility, safety, reliability, cleanliness, behavior, or a successful shared stay.

Select the person's profile or listing from the applicable event view to see the information they have made available to potential roommates.

Review practical factors such as dates, budget, room or bed arrangements, sleep schedule, noise and light preferences, smoking or alcohol expectations, accessibility needs, communication style, and any other information important to your comfort. Use TDRC's verification and safety tools, but make your own judgment before agreeing to share accommodations.

Where supported by the current search and filtering tools, you can use available event, listing, and preference information to narrow potential roommate options.

No. TDRC's standard matching flow does not provide unrestricted direct messaging before a match. You first send a roommate request; messaging becomes available when the request is accepted and a match is created.

Common reasons include an incomplete or unverified account, not having access to the same event, already having an active request or match that prevents another request, the other member being unavailable, or a block or moderation restriction.

Yes. Matching activity is event-specific, so you may participate in multiple events subject to any account or plan limits.

No. TDRC helps you discover and compare potential roommates, but you decide whom to request, accept, and ultimately share accommodations with.

A roommate request is an invitation to another eligible member in the same event to become your roommate match. A request is not a confirmed match until the recipient accepts it.

Open an eligible member's profile or listing and select the option to send a roommate request. You must meet the applicable profile, verification, event-access, and active-request requirements.

The recipient can review the request and your available profile or listing information, then accept or decline it. The request remains pending until it is acted on, canceled, or expires.

Open the pending request, review the sender's profile and listing information, and select Accept if you want to match. Acceptance creates the roommate match and enables post-match features such as messaging.

Open the request and select Decline. Declining does not create a match, and the requester can pursue another eligible roommate after the request is closed.

Yes, while it is still pending and cancellation is available. Once canceled, the request no longer can be accepted.

Pending roommate requests expire after three days if they are not accepted, declined, or canceled first.

TDRC automatically expires a pending request after three days so members are not indefinitely prevented from pursuing another roommate.

Yes. TDRC's current notification rules include a reminder approximately six hours before a pending roommate request expires.

No. TDRC allows one active roommate request at a time under the current matching rules.

The one-active-request rule reduces conflicting commitments and prevents multiple people from accepting requests from the same user at the same time.

Whether an incoming request is allowed depends on the matching-state rules enforced by TDRC. The platform prevents states that would create conflicting active matches or commitments.

The request closes without creating a match. You can then consider another eligible potential roommate.

Yes. Once the previous request is no longer active, you may send a new request to an eligible user.

Yes. Accepting an eligible roommate request creates an active match for that event.

An active match is created for the event. Match-specific features, including messaging, become available and the matched users are no longer treated as openly available for another active match in that event.

TDRC updates the request and match status and sends the applicable in-app or email notification when a request is accepted.

No. The current TDRC rules allow one active match per event.

Matching enables the information and functionality TDRC designates for matched users, including direct messaging. You should still share only the personal information needed to coordinate the stay.

Not for another active match in the same event while your current match remains active. TDRC limits each user to one active match per event.

Open the active match and use the available cancellation action. TDRC requires a cancellation reason as part of closing the match.

A cancellation reason provides context for the match record and may help TDRC with support, trust and safety review, and product integrity.

The conversation becomes read-only after the match closes under the current product rules. Messages are retained for five years rather than being deleted when a match ends.

A future rematch may be possible only if both accounts remain eligible and the product permits a new request for that event. A canceled match itself does not automatically reactivate.

The active match closes, the conversation becomes read-only, and you may resume roommate discovery if you remain eligible for the event.

Use TDRC messaging to make reasonable attempts to contact them. If you no longer want to rely on the arrangement, use the match-cancellation process. If the behavior creates a safety or policy concern, use the reporting tools.

The match can move to a closed or historical state after the event. The associated record and messages may remain available in read-only form and are retained according to TDRC's retention rules.

Direct messaging becomes available after an eligible roommate request is accepted and an active match is created.

TDRC limits direct messaging to matched users to reduce unsolicited contact and keep the communication flow tied to a mutual roommate decision.

Open the Messages area or your active match conversation, enter your message, and send it using the available messaging controls.

Yes. TDRC's messaging rules allow supported attachments. Do not use attachments to send prohibited, unsafe, or unnecessarily sensitive information.

No. TDRC messages are intended to be immutable and retained as part of the conversation record.

No. Sent messages are not intended to be edited because the conversation is maintained as an immutable record.

No. A user cannot erase the retained conversation record for both participants. Conversation availability may change when a match closes, but retained messages are not removed simply because one user wants to delete them.

TDRC's current product rules require messages to be retained for five years.

Avoid sharing passwords, full payment-card information, government identification numbers, unnecessary financial information, or other sensitive data. Share only what is reasonably needed to coordinate the accommodation arrangement.

Use your judgment and prioritize communication through TDRC while you are evaluating the arrangement. If you choose to exchange contact details after matching, understand that communications outside TDRC may not be available to TDRC for support or safety review.

Use TDRC's report and block tools. If the message suggests an immediate threat or emergency, prioritize your safety and contact the appropriate local emergency service rather than relying on TDRC support.

The conversation becomes read-only when the match closes under the current rules. Existing messages remain retained, but new messages are no longer allowed through that closed match conversation.

TDRC may review relevant retained messages when necessary to investigate a report, enforce platform rules, provide support, or address safety and legal obligations, subject to its privacy and access controls.

TDRC uses measures such as account and identity verification, event-specific matching, booking-evidence review where applicable, blocking and reporting tools, retained message records, moderation processes, and safety notices. These measures reduce risk but cannot eliminate it, so members should still use their own judgment and take reasonable precautions.

TDRC's current product rules do not establish a comprehensive criminal background-check program. Identity verification should not be interpreted as a background check.

No. Identity verification helps confirm that an account is associated with a real person, but it does not guarantee that the person is safe, trustworthy, compatible, financially reliable, or suitable as a roommate.

Identity verification checks the information and documentation required by TDRC's verification process to establish that the account is associated with a real individual. The exact verification checks may depend on the verification method used.

Review the person's profile, compatibility information, listing details, verification status, dates, costs, room arrangement, and expectations. Communicate clearly, independently confirm important reservation details, avoid sending unnecessary sensitive information, and do not proceed if anything makes you uncomfortable.

If practical, meeting in a public setting before sharing accommodations can help both people confirm expectations and comfort levels. If an in-person meeting is not possible, communicate thoroughly through TDRC before the stay.

Avoid sharing passwords, full payment-card numbers, bank login information, government identification numbers, or other sensitive information that is not necessary to arrange the stay.

Use caution with any payment between roommates. TDRC does not currently process roommate-to-roommate accommodation payments, so independently verify the reservation and understand the arrangement before sending money. Never send payment based solely on pressure, urgency, or unverifiable claims.

Confirm the accommodation details, dates, total cost, your agreed share, cancellation expectations, and evidence of the reservation. Keep a record of what both parties agreed to and use a payment method that provides appropriate records or protections.

Review the booking evidence available through the TDRC process where applicable and independently confirm important details with the hotel or accommodation provider when possible. Do not rely on screenshots alone if you have unresolved concerns.

You may choose whether to exchange outside contact information after matching, but keeping important communications in TDRC preserves a record that may be useful for support or safety review. Be cautious if someone pressures you to leave the platform immediately.

Do not feel obligated to proceed. You can decline or cancel the applicable request or match, block the user, and report conduct that may violate TDRC's rules or raise a safety concern.

Prioritize your immediate safety. Leave the situation if you can do so safely, contact hotel or venue security when appropriate, and contact local emergency services for an immediate threat. You can also report the user to TDRC for platform review.

TDRC is not an emergency-response service. If you or someone else is in immediate danger, contact the appropriate local emergency service or onsite hotel or venue security.

No. TDRC facilitates connections between event attendees. It is not the hotel, accommodation provider, travel agent, property manager, or a party to the private roommate arrangement. Users are responsible for evaluating one another, confirming reservations, agreeing on payment arrangements, and making their own final accommodation decisions.

Use the block action available from the applicable profile, match, message, or safety menu. Choose the available block scope when prompted.

Blocking prevents the blocked user from interacting with you in the ways covered by the selected block scope. Existing records may still be retained for safety, support, and compliance purposes.

TDRC does not need to send a direct notification identifying that you blocked someone. However, the person may infer it if they can no longer view or interact with you in the same way.

An event-specific block applies within the selected event, while a global block is intended to prevent covered interactions across TDRC, not just in one event.

A block restricts profile visibility and interaction according to the scope and privacy rules enforced by TDRC. Historical records required for moderation or support may still exist internally.

No. A block that applies to the relevant event or globally prevents the blocked user from sending you a new roommate request.

A blocked user cannot continue normal messaging with you through a block that applies to that relationship. Existing messages may remain retained and visible in read-only or historical form.

Use the account or privacy controls where blocked users are managed and select the available unblock action. Unblocking does not automatically recreate an expired request or closed match.

Use the Report action from the relevant profile, match, message, or safety menu. Select the appropriate reason and provide the information or evidence needed for TDRC to review the concern.

Report behavior that may violate TDRC's Community Standards or create a trust or safety concern, including harassment, threats, fraud, impersonation, discriminatory conduct prohibited by policy, misleading reservation information, inappropriate content, or other serious misuse of the platform.

Yes. A closed match does not prevent you from reporting conduct associated with that relationship while the relevant records are available.

Yes, where the reporting workflow remains available. TDRC retains relevant records in part so post-event safety and policy concerns can be reviewed.

TDRC reviews the submitted information and any relevant retained records, may request additional information, and determines whether moderation or other action is appropriate under its policies.

TDRC's current product rules target review of submitted reports within three business days.

TDRC should not disclose the reporter's identity unnecessarily. However, details required for investigation, legal process, or enforcement may make the underlying incident recognizable to the reported user.

Where supported by the reporting workflow, provide relevant messages, attachments, screenshots, reservation information, or other evidence that helps TDRC understand the concern.

Depending on the circumstances and applicable policy, TDRC may take no action, issue a warning, restrict features, suspend an account, remove content, terminate access, preserve records, or take other measures needed to protect the platform and its users.

A suspended account may lose access to some or all TDRC features while the suspension is active. TDRC may provide information about the action and any available appeal process consistent with its policies.

Yes. TDRC's current rules allow one appeal of an eligible moderation decision.

The current rules allow one appeal to be submitted within 30 days of the applicable moderation decision.

TDRC collects information needed to operate the platform, such as account details, profile information, roommate preferences, event activity, listings, requests, matches, messages, verification information, reports, and technical or security data. The final Privacy Policy should describe the categories and purposes in full.

Members can see the profile, listing, compatibility, and match information made visible to them based on the product state and privacy rules. Sensitive authentication, verification, and private account information is not intended to be publicly displayed.

Your name may be visible as part of your TDRC profile to users who can access that profile under the event and matching rules. Exact visibility should follow the production privacy settings and Privacy Policy.

Your full date of birth should not be treated as ordinary public profile information. It is primarily used for eligibility and account purposes, with only the minimum age-related information needed for the product experience displayed where appropriate.

Identity-verification information is used for account eligibility, trust and safety, fraud prevention, and related operational purposes. Access should be limited to authorized systems or personnel, with handling governed by TDRC's security and privacy rules and any verification provider requirements.

The exact production answer depends on the identity-verification architecture and provider. TDRC should disclose whether documents are stored by TDRC, by a third-party verification provider, or only retained for a limited review period before this article is published.

Booking evidence should be stored with restricted access and used only for the verification, trust and safety, support, compliance, or recordkeeping purposes defined by TDRC. The exact storage and retention details should match the production security and privacy implementation.

Booking evidence is not intended to be public. Access should be limited to authorized TDRC personnel or systems that need it for verification, support, trust and safety, compliance, or related operational purposes.

Retention depends on the data type and the reason it is kept. Current product rules specify five-year retention for certain records, including messages and hidden or closed listings. Other information may have different retention periods based on operational, safety, legal, or privacy requirements.

TDRC's current product rules specify a five-year retention period for messages.

Some records may need to be retained for trust and safety, fraud prevention, dispute handling, legal compliance, enforcement, or protection of other users. Account deletion does not necessarily require immediate deletion of every retained record where another lawful retention purpose applies.

Use the privacy-request process provided by TDRC. The production Privacy Policy and account settings should identify the available method for submitting an access request.

Use TDRC's account-deletion or privacy-request process. TDRC will handle the request subject to applicable law and any information it is permitted or required to retain.

Yes. You can update editable profile information directly and use the applicable support or privacy process for information that cannot be changed through your account.

This answer must match the final Privacy Policy and data practices. It should not be published as a categorical statement until TDRC's production privacy disclosures are finalized.

TDRC may need to share information with service providers that support functions such as hosting, authentication, identity verification, communications, storage, analytics, or payment processing. The final Privacy Policy should identify the applicable categories, purposes, and legal disclosures.

TDRC is designed to use technical and organizational safeguards appropriate to the information and platform risks, including access controls and security protections defined in its security architecture. No online system can guarantee absolute security.

The Community Standards define the behavior expected from TDRC members and the conduct that can result in warnings, restrictions, suspension, or removal. The final standards should be published alongside the Terms of Service and safety policies.

Prohibited behavior should include conduct such as harassment, threats, fraud, impersonation, intentionally false listing or reservation information, harmful or unlawful content, misuse of personal information, prohibited discrimination, and attempts to misuse TDRC for purposes outside its intended roommate-matching function.

TDRC can review the conduct and take action proportionate to the circumstances, including warnings, content removal, feature restrictions, suspension, or account termination.

Yes. TDRC may suspend, restrict, or terminate accounts when necessary to enforce its rules, respond to safety or fraud concerns, or meet legal and security obligations.

The final treatment must follow TDRC's Terms of Service and applicable law. TDRC's current product rule is that purchases are generally non-refundable except where required by law, but enforcement-related outcomes should be stated explicitly in the final Terms.

TDRC's final Community Standards and legal review should define prohibited discriminatory conduct and any lawful roommate-preference options. This article should align exactly with those policies rather than creating a broader or narrower rule on its own.

TDRC currently supports Same Gender and No Preference as roommate gender-preference options. Their use must remain consistent with TDRC's final Community Standards, applicable law, and the product's roommate-sharing context.

TDRC is intended for individual event attendees seeking to share accommodation costs, not for commercial accommodation inventory. The final Community Standards should explicitly prohibit commercial listings unless TDRC later introduces an authorized business program.

Not under the current individual-roommate model unless TDRC creates a separate authorized business feature or program. Standard listings are intended for eligible individual users.

TDRC is designed to help attendees share accommodation costs, not to operate a commercial resale or profit-making marketplace. Listings should accurately represent expected costs and the actual shared accommodation arrangement.

No, not through ordinary roommate listings, requests, or messages unless TDRC explicitly authorizes that activity. Unsolicited commercial promotion can interfere with the platform's intended purpose and may violate the Community Standards.

Materially false profile, identity, listing, reservation, or accommodation information can result in removal of content, loss of verification, restrictions, suspension, termination, or other moderation action depending on the circumstances.

The Terms of Service should be available from TDRC's website, account or legal links, and the application footer once the final production terms are published.

The Privacy Policy should be available from TDRC's website, account or legal links, and the application footer once the final production policy is published.

Use the support or contact channel designated for policy, safety, or legal questions. The final Help Center article should link directly to that channel once the production contact method is finalized.

TDRC may offer free access during a beta period. Under the planned paid model, event access is purchased through an event unlock or included through an eligible annual plan.

The planned Per Event price is $29.99 USD for one event unlock.

An event unlock gives your eligible account access to TDRC's roommate-related features for the selected event, subject to profile, verification, safety, and product rules.

The planned Annual Plan costs $99.99 USD and includes up to five event unlocks during the applicable one-year plan period.

The planned Annual Plan includes five event unlocks during the one-year plan period.

After the included unlocks are used, additional eligible event access can be purchased under the applicable additional-unlock rules.

The planned price for an additional event unlock is $19.99 USD, subject to the annual event limit and the terms shown at purchase.

Yes. The current pricing rules specify a maximum of five events per year.

The Annual Plan covers a one-year period beginning according to the plan's purchase or activation terms. Your account should display the applicable expiration or renewal date.

The final production renewal behavior should be confirmed from the checkout and subscription implementation before this article is published. TDRC's product rules do require renewal reminders one month and one week before renewal where automatic renewal applies.

Yes, where the plan is configured to renew. TDRC's current rules call for renewal reminders one month and one week before the renewal date.

The exact cancellation workflow should be confirmed when production subscription billing is enabled. Any available cancellation controls and their effect on future renewal will be shown in your account or billing settings.

The final effect of cancellation on remaining access and unused unlocks should follow the production billing terms shown at the time of cancellation. Cancellation does not override TDRC's stated refund policy.

Under TDRC's current product rules, purchases are non-refundable except where a refund is required by applicable law.

The specific access or credit treatment for a canceled event should follow the terms presented with the purchase and applicable law. TDRC's general policy is that purchases are non-refundable except where required by law.

Choosing not to attend does not by itself create a refund right. TDRC's current policy treats purchases as non-refundable except where required by law.

Payment processing is not part of the current free beta scope. Once production payments are enabled, common decline reasons and billing-support steps should be documented based on the selected payment processor.

Payment processing is not part of the current free beta scope. The production payment-method workflow should be documented once billing is enabled.

Payment processing is not part of the current free beta scope. The production billing experience should provide the appropriate transaction or receipt access once payments are enabled.

TDRC's planned base pricing is in U.S. dollars (USD). The interface may display approximate local-currency conversions for convenience.

Local-currency displays can be estimates. Your bank, card issuer, or payment provider may use a different exchange rate or add conversion or international transaction fees. The authoritative TDRC price is the USD amount shown at checkout unless the checkout explicitly states otherwise.

Open TDRC, select Sign In, and use the email-and-password or supported social sign-in method associated with your account.

Select Forgot Password on the sign-in screen and follow the password-reset instructions sent to the email address associated with your account.

Confirm that you entered the correct account email address, check spam or junk folders, and allow time for delivery. If the message still does not arrive, try the reset process again or use the available support channel.

Check that the email address on your account is correct, review spam or junk folders, and use the resend-verification option if available. If the problem continues, contact TDRC support.

Use the account settings option for updating your email address, if available. You may need to verify the new address before it becomes active.

Open your account or security settings and use the password-change option. If you cannot sign in, use the password-reset process instead.

Use the account or authentication settings provided by TDRC to review supported connected sign-in methods. Availability depends on the social authentication features currently enabled.

Common causes include an incorrect password, unverified email, using a different sign-in method than the one associated with the account, an account restriction, or a temporary technical issue. Try the applicable password-reset or social sign-in method and review any error message shown.

An account may be temporarily restricted because of security controls, repeated failed sign-in attempts, suspected misuse, or another account-protection event. Follow the instructions shown in TDRC or contact support if no recovery option is provided.

TDRC may suspend an account because of a safety, moderation, fraud, policy, or security concern. The notice associated with the suspension should explain the status and any available appeal or next steps.

If TDRC provides session-management controls, use them from your account security settings. If that feature is not available and you believe someone else has access to your account, change your password immediately and contact support.

No. TDRC accounts are personal and tied to the individual who completed the account and identity-verification process.

Use the available account-deactivation or deletion controls in your settings. If no self-service option is available, use TDRC's support process to request the applicable account action.

Use the account-deletion option where available or submit a deletion request through the designated privacy or support process. Some records may still be retained when required for safety, legal, fraud-prevention, or other legitimate retention purposes.

Your active account access is removed, but TDRC may retain historical listings, match records, messages, reports, and other information according to its retention, safety, legal, and compliance requirements. Retained records may no longer function as active user content.

Account restoration is not guaranteed. If deletion has been completed, you may need to create a new account if TDRC permits it, and retained historical records do not necessarily become active again.

Your roommate profile can include your name, photo, date of birth, gender identity, hometown, company, title, About Me information, and sleep or roommate preferences such as snoring, CPAP use, sleep schedule, light preference, noise sensitivity, room temperature, and gender preference.

Open your profile or account settings, select the profile editing option, update the applicable fields, and save your changes.

A complete profile gives potential roommates enough information to make an informed decision and allows TDRC to evaluate the compatibility factors used by the platform. Required profile completion is also an eligibility condition for sending roommate requests.

TDRC supports preferences including snoring, CPAP use, sleep schedule, light preference, noise sensitivity, room temperature, and roommate gender preference. Listings may also contain accommodation-specific preferences such as smoking and alcohol.

Sleep preferences describe habits and environmental preferences that may affect whether two people are comfortable sharing a room. They are intended to help members discuss practical compatibility before agreeing to room together.

Answer based on what you reasonably know about your normal sleep habits. If you know that you regularly snore, indicate that honestly so potential roommates can make an informed decision.

The CPAP field lets you indicate whether you use a CPAP device while sleeping. This can help roommates anticipate equipment, outlet, noise, or bedside-space considerations.

These options describe your general sleep schedule. Early Risers typically prefer earlier bed and wake times, while Night Owls typically stay awake and wake later. They are broad preference indicators rather than strict schedules.

Light preference indicates the sleeping environment you generally prefer, helping potential roommates identify whether their preferred nighttime lighting habits are likely to be compatible with yours.

Noise sensitivity indicates how easily normal room sounds may disturb your sleep or comfort. Use the option that best reflects your typical experience.

Room temperature preference indicates whether you generally prefer a cooler, warmer, or moderate sleeping environment. It helps identify a common source of roommate conflict before matching.

TDRC allows members to select the available roommate gender-preference options, including Same Gender or No Preference. The preference is used for roommate matching and discovery within the platform's applicable policies.

Yes. You can update your roommate preferences from your profile. Changes may affect future compatibility results, listings, and roommate discovery.

Your date of birth is used for eligibility and account purposes and should not be treated as ordinary public profile information. TDRC may display only the age-related information needed for the product experience rather than your full date of birth.

Visibility depends on the field and TDRC's privacy rules. Some information is required for profile or matching purposes, while sensitive account and verification information is not publicly displayed.

Open your profile, select the profile photo editing option, upload or choose a new supported image, and save the change.

TDRC can send in-app and email notifications related to account verification, roommate requests, request expiration, matches, messages, safety or moderation activity, events, weekly digests, and plan renewal where applicable.

Open your account or notification settings and adjust the available notification preferences. Some operational, security, safety, or legally required notices may not be optional.

Yes. TDRC's notification model includes in-app and email notifications for important roommate-request activity.

Yes. The applicable request status is updated in TDRC, and important request and match outcomes are included in the notification model.

Yes. TDRC's current rules call for a reminder approximately six hours before a pending roommate request expires.

TDRC can notify you of new messages according to your available notification settings.

The weekly digest is a recurring summary of relevant TDRC activity and information intended to help you keep up with your events and roommate-search activity.

TDRC's current product rules schedule the weekly digest for Sundays at 5:00 PM Eastern Time.

Where the digest is classified as an optional communication, you can disable it through the available notification or email-preference controls.

Yes, where an Annual Plan is configured to renew. The current rules call for reminders one month and one week before renewal.

Confirm that your email address is verified and correct, check spam or junk folders, review your notification preferences, and make sure messages from TDRC are not blocked by your email provider.

Use the unsubscribe or notification-preference controls provided with optional communications or in your account settings. Transactional, security, legal, or safety notices may still be sent when necessary.

Yes. TDRC may need to send essential account, security, safety, moderation, legal, billing, or service notices even if you opt out of optional promotional or digest communications.

TDRC should be designed and tested to support accessible use. The final public answer should reflect the actual accessibility conformance and supported assistive-technology behavior of the production application.

Use the available accessibility fields or listing details to identify needs or accommodation features that are relevant to your stay. Share only the information you are comfortable providing and that is useful for planning the accommodation.

Use the accessibility information available in listings and any supported filters. Because TDRC does not independently verify hotel accessibility, confirm critical features directly with the hotel or property before relying on them.

Where the accessibility fields allow it, you can identify relevant mobility or accommodation needs. You can also discuss practical room-layout or accessibility considerations with a potential roommate after matching.

Focus on the practical information needed to make the shared stay work, such as room layout, accessible bathroom needs, space for mobility equipment, service-animal considerations, or schedule needs. You are not required to disclose more personal or medical information than is necessary for the arrangement.

No. TDRC may display accessibility information supplied by users or event sources, but users should independently confirm critical accessibility features with the hotel or accommodation provider.

Do not rely on the incorrect information. Contact the matched user if appropriate, confirm the actual accommodation details with the hotel or property, and report materially misleading information to TDRC when it may affect other users.

Use TDRC's technical-support or accessibility-feedback channel and describe the page, feature, assistive technology, browser or device, and problem you encountered so the issue can be reproduced and reviewed.

Use the available support channel and explain what part of TDRC you need help accessing or completing. TDRC should provide reasonable assistance consistent with the service and applicable accessibility obligations.

Refresh the page, confirm your internet connection, and try a supported current browser. If the issue continues, clear the applicable site data or try another browser or device, then report the problem with the error details if it persists.

Confirm that you meet any eligibility requirements for the action, then refresh the page and try again. If the control appears disabled even though you should be eligible, report the page, button, browser, and steps that reproduce the issue.

Your profile or identity verification may be incomplete, the event may not be available for listing activity, required listing fields may be missing, or your account may have a restriction. Review any validation or status message shown in TDRC.

Confirm that your profile is complete, your email and identity are verified, you and the other user are eligible for the same event, and you do not already have an active request or conflicting match. Blocks and moderation restrictions can also prevent requests.

The request may have expired, been canceled, or become invalid because one of the users is no longer eligible or has entered a conflicting match state. Refresh the request status and review any message shown by TDRC.

Messaging requires an active match. If the match was canceled, closed, blocked, or restricted, the conversation may be read-only. A temporary technical problem can also prevent sending.

Review the profile for missing required fields, photo or verification requirements, and any incomplete roommate preferences. Save the profile again after completing all required items.

Verification may still be under review, additional information may be required, or the status may not have refreshed yet. Review the verification area for instructions and contact support if the status remains unchanged unexpectedly.

During the free beta, paid event unlocks may not be active. Once billing is enabled, confirm the transaction completed successfully and that you are signed into the same account used for the purchase; then contact support if access is still missing.

Confirm your account email is correct and verified, check spam or junk folders, review notification preferences, and make sure TDRC messages are not blocked by your email provider.

The file may exceed the allowed size, use an unsupported file type, fail a security check, or encounter a temporary upload problem. Review any upload validation message and try a supported file.

Use the file types accepted by the upload control. The exact production list and size limits should be documented from the implemented photo, messaging, identity, and booking-evidence upload rules before publication.

Read the message for any action you can take, then retry once if appropriate. If the error persists, capture the exact message, page, time, browser or device, and steps that caused it and provide those details to support.

The final support matrix should be based on TDRC's production compatibility requirements and testing results. This article should not name specific browser versions until those requirements are finalized.

Use the available Help or Support channel and include what you were trying to do, what happened instead, the exact error if any, the page or feature involved, your browser or device, and steps that reproduce the issue.