The ENHANCED_EMAIL_VALIDATION error means our email authentication provider has blocked the yandex.ru domain from the email OTP login flow. We authenticate through external providers and cannot change account emails, swap auth providers, or bypass authentication - this is a security boundary we cannot override. Your project data remains intact, but we are unable to restore access to an account when the authentication method is no longer available. If you originally linked a GitHub or Google account to this Railway account, you may still be able to log in through that method at railway.com/login.

You should have warned me beforehand that you were going to change your rules and my account would become inaccessible. That would have been polite, wouldn't it?

The domain restriction was applied by our third-party email authentication provider, not something we controlled or had advance notice of ourselves. We apologize for the inconvenience. Unfortunately, as mentioned, we're unable to modify authentication methods or bypass login on our end - this is a hard security boundary we cannot override.

I understand that Railway is currently unable to authenticate me through email OTP because the yandex.ru domain is blocked by your email authentication provider.

Since Railway cannot restore my access to the existing account, I am making a formal account deletion and data erasure request.

Please delete the Railway account associated with decimator@yandex.ru and all associated resources, including but not limited to:

• all Railway projects and environments
• all services and deployments
• all volumes, databases, files, build artifacts and runtime data
• all environment variables and secrets
• all API tokens, sessions and authentication data
• all logs and telemetry that are not legally required to be retained
• all source code submissions / user submissions stored in the account
• all personal data associated with this account

Please also remove or redact my email address from this public support thread, since it is personal data.

I still control the original email address decimator@yandex.ru and I am ready to verify ownership using any reasonable method, including:

• replying from the original email address
• confirming billing/payment details
• confirming invoice details
• confirming project names, service names, domains, deployment metadata, or usage history
• any other reasonable verification method you require

We understand your request to delete your account and erase your data. Unfortunately, we are unable to delete accounts on behalf of users, as that would pose a security risk. Since your account is on the free plan with no active subscription, no charges will accrue. Your account will remain inactive, and all services and deployments associated with it are stopped.

To clarify: I am not asking Railway support to delete the account without verifying ownership.

I am asking Railway to provide an alternative ownership verification process, because Railway's normal authentication flow is unavailable for my existing account due to your email authentication provider blocking the yandex.ru domain.

I am currently located in Kazakhstan. I am making a formal account deletion and data erasure request for the account associated with decimator@yandex.ru under Railway's Privacy Policy and any applicable privacy/data protection law.

If GDPR or another data protection framework applies, I am exercising my right to deletion/erasure and, where immediate deletion is not possible, restriction of processing. If Railway believes GDPR does not apply, please process this request under Railway's Privacy Policy and the applicable legal framework, and explain which framework Railway is relying on.

Your response says that the account will remain inactive and services are stopped. That does not address my request. I am asking for deletion/erasure, not only suspension or inactivity.

Please escalate this to your privacy / legal / data protection team and provide an alternative method to verify ownership. I can verify ownership by any reasonable method, including:

• replying from the original email address;
• confirming project names, service names, domains, deployment metadata, or usage history;
• confirming billing/payment/invoice details if any exist;
• confirming account creation details or other account metadata.

If Railway refuses to delete any category of data, please provide a written explanation identifying:

1. the exact category of data retained;
2. the legal basis for retaining it;
3. the retention period;
4. whether processing has been restricted;
5. when the data will be permanently deleted or anonymized.