Two contact details—an email address and a phone number—are not required for OtherDay username-and-password registration, according to its official privacy policy. If you are on that signup route, you do not need a temporary email just to create an account. If you choose Apple or Google sign-in instead, continue through the option shown on OtherDay’s page and follow its authorization flow.
This is for adults currently creating an OtherDay account, deciding whether to share a personal email, or choosing between a username-and-password route and a third-party sign-in.
Last updated October 30, 2026. We checked the conclusion against OtherDay’s privacy policy, FAQ, and the sign-in options described in its official materials. The live signup page and policies can change, so confirm the options shown when you register.
The email question depends on the signup route
Can you register without entering an email address? Yes, if you select username-and-password registration. OtherDay’s privacy policy says that this method does not require an email address or phone number. That statement applies to that specific route. It should not be stretched into a claim that every login option follows identical steps or collects identical information.
When you reach the account creation page, first identify the route you selected. A form asking you to choose a username and password is not the same flow as authorizing an external account. A third-party button may take you to a separate authorization screen, where the information presented depends on that route and its current prompts.
| Signup route | What the official information confirms | What to do |
|---|---|---|
| Username and password | OtherDay says email and phone are not required for this registration method. | Continue with this route if it is offered and suits your needs. |
| Apple sign-in | OtherDay lists Apple as a sign-in option in its official privacy information. | Choose it only if you want to use that authorization route. |
| Google sign-in | OtherDay lists Google as a sign-in option in its official privacy information. | Review the authorization prompt before continuing. |
The table is about the documented routes, not a promise that every screen will look the same. Registration pages can be revised. If the page in front of you differs from the official information, pause and check the current policy or FAQ rather than assuming the missing field is an error.
Username and password versus Apple or Google
What is the difference between a password signup and Apple sign-in? A username-and-password route has you create credentials for the account using the fields on OtherDay’s signup page. Apple or Google sign-in uses the corresponding option displayed there. OtherDay’s privacy policy describes those third-party options and its handling of related account information, but that does not establish every detail of account linking, email visibility, or future recovery.
| Choice | Main decision | Potential benefit | Check before proceeding |
|---|---|---|---|
| Username and password | Whether you want to create and manage a separate set of credentials | The documented route does not require email or phone | Save the chosen credentials securely and check what account controls are available |
| Apple sign-in | Whether you prefer the Apple authorization option shown by OtherDay | You can use the third-party route rather than filling in the username-and-password form | Read the authorization screen; do not infer what details are shared beyond what it says |
| Google sign-in | Whether you prefer the Google authorization option shown by OtherDay | You can use the third-party route rather than filling in the username-and-password form | Review the requested access and the account connection information |
For Google, you can also review Google’s explanation of how to manage connections between your Google Account and third-party apps. That guidance explains Google-side account connections; it does not replace OtherDay’s own policy or confirm what its current signup page will ask.
The practical difference is control, not a reason to assume that one route is automatically more private. With a password route, you are responsible for keeping those credentials accessible and protected. With a third-party route, you should understand which account is being used and review the authorization prompt. We would not treat the presence of an Apple or Google button as proof that OtherDay will never request additional information later.
Does the username-and-password option mean you can use any made-up details? No. Use the information the service asks for and follow its rules. Do not falsify details or try to disguise an email domain to get around a restriction. If the route you want is unavailable or the service requests information you do not want to provide, stop and decide whether to use another supported option.
Account access after signup
Creating an account and retaining access to it are separate questions. The official privacy policy answers whether email or phone is required for username-and-password registration. It does not, by itself, establish every future recovery condition, how account credentials can be changed, or what happens if you lose access to a third-party account.
OtherDay’s official FAQ is a useful place to check product and account questions. Its terms are also relevant when you need to understand the service’s conditions. We found no basis in the cited material for promising that a particular recovery method will always be available. Treat any recovery step not clearly documented there as something to verify directly, not as a feature you can count on.
How do you protect access after creating the account? Keep the chosen login method identifiable and the credentials for it secure. If you used a third-party sign-in, maintain access to that third-party account. If you created a password, store it in a secure password manager or another method you trust. Avoid relying on an inbox you may lose access to as the only record of how you signed in.
| Access concern | What is confirmed | Safer next move |
|---|---|---|
| Email needed during username-and-password registration | The policy says it is not required | Do not add a temporary inbox solely to satisfy a field the route does not require |
| Later recovery | The cited signup statement does not specify all recovery conditions | Check current account settings and official support information before relying on recovery |
| Third-party authorization | Apple and Google are listed as options | Read the prompt and keep the relevant third-party account accessible |
| Policy or page changes | The current published information may not match an older screenshot | Recheck the live page and official policy when you register |
A temporary address does not solve every account-access problem. If you use one for a different service, later password resets or security messages may depend on continued access to that address. For a closer look at that risk, read our guide to email and account lifecycle risks. If the account matters to you beyond a short trial, choose a login method and recovery plan you can maintain.
Important: “Email is not required for this signup route” does not mean “email can never matter to the account.” Do not assume future notices, support checks, or recovery flows will work in a particular way unless the current official information confirms it.
When a temporary inbox is unnecessary
Can you use a temporary email to register? The available official statement makes a temporary inbox unnecessary for username-and-password registration because that route does not require an email address. It does not confirm that every other flow accepts temporary addresses, nor does it say a temporary inbox is required for Apple or Google sign-in.
That distinction matters if you are trying to reduce exposure of your main inbox. Avoid sharing it when the chosen route does not ask for it. But do not add an extra email address simply because you assume every account needs one. Extra steps can create another credential or inbox to manage without solving a real signup requirement.
There are also cases where using a disposable address would be a poor fit. If you expect to need long-term support, account recovery, or notices sent to an email address, consider whether you can retain access to that inbox. Our guide to temporary email and email alias boundaries explains how the options differ when you need privacy without losing a way to receive future messages.
For the OtherDay signup decision, use this branch list:
- If the page offers username-and-password registration and you are comfortable using it, follow that route; the official policy says it does not require email or phone.
- If you prefer Apple or Google sign-in, select the matching option shown and review its authorization prompt.
- If the page requires an email despite the route you selected, stop and check that you are on the intended signup flow and that the current page matches the official guidance.
- If you need dependable long-term recovery through email, do not assume a temporary address will remain suitable; verify the available recovery options first.
- If none of the offered routes fits your privacy or access needs, do not invent details or try to bypass a restriction. Reconsider whether to create the account.
A quick page check before continuing
Use these checks while the signup page is open. They are designed to prevent confusion between a required field and an optional or third-party route.
- Read the selected route. Confirm whether you are entering a username and password or starting an Apple or Google authorization.
- Check the form fields. On the username-and-password route, compare the page with the official statement that email and phone are not required.
- Inspect the buttons before choosing. If you select a third-party option, make sure it is the account you intend to use and read the authorization screen.
- Do not infer recovery rules. Signup requirements do not tell you every way an account can be restored. Check official account information if future access matters.
- Save the access details. Record which route you used and protect the password or the third-party account that controls sign-in.
- Recheck unexpected prompts. If the page asks for an email or phone unexpectedly, verify the route and current official guidance before submitting information.
- Decide whether the account is worth creating. If the available login choices do not meet your privacy or recovery needs, it is reasonable to stop.
What if you are asked for an email anyway? First confirm that you are on OtherDay’s genuine signup page and that you have not moved into a different flow. Then check the current FAQ and privacy policy. The documented no-email rule is specific to username-and-password registration; it is not a guarantee that every screen, account action, or later policy will be identical.
A common mistake is to treat every email field as a verification requirement. A field may belong to a different path, or the page may have changed since the policy information was last reviewed. Read the label and surrounding instructions. If the purpose remains unclear, do not enter a disposable address just to move forward; consult the service’s official information first.
What the official information leaves open
The confirmed point is narrow and useful: OtherDay says username-and-password registration does not require an email address or phone number. It also documents Apple and Google sign-in options. Those facts are enough to choose a signup route without guessing that a temporary email is mandatory.
They do not answer every question people may have after registration. The cited information should not be used to claim that a temporary email is accepted in every account flow, that an account can always be recovered without email, or that third-party sign-in shares no account information. Those conclusions go beyond what the stated policy confirms.
If you are still unsure, compare the live signup page with the official privacy policy and FAQ immediately before submitting. That is especially important if you have an older screenshot, a saved instruction, or a sign-in page that looks different from the one described here. We would rather pause at an unexplained prompt than turn an uncertain assumption into a permanent account-access problem.
If you only need to protect your main inbox for a separate one-time registration or message, first check whether that service actually requires email. When it does, a temporary inbox can keep that interaction apart from your everyday address; when it does not, adding one may be unnecessary. You can review the current SendTmp inbox page if you have a genuine temporary-email use case, and compare it with an email alias when you need a more persistent way to receive messages.