We're not able to share the specifics behind a workspace restriction, and unfortunately for paid workspaces the restriction cannot be reversed. There is no appeal or review path available. For recovering your setup, you should still be able to view your environment variables in the dashboard and copy them out, or use the Railway CLI with railway variable list to export them per service. Your source code lives in your connected Git repo, so that remains accessible as usual. Once you've saved what you need, the next step would be to cancel your plan from your workspace billing settings.

I'll accept that you can't share the specifics of this restriction. But I do want to keep using Railway, and to do that I need to understand how to stay within your rules. Could you help with whichever is possible:

1. Any concrete fair-use guidance I should follow on a new project so I don't trigger a restriction again.

2. A direct answer on one thing: are scraping or third-party-API-proxy services (one of mine fetched data from an external site) allowed under your fair use policy, or are those something I should avoid hosting here?

Even a simple yes/no on that second point would help me decide how to rebuild. Thank you.

We understand the desire to avoid this in the future. We're not able to give guidance on specific use cases in this context, but our Fair Use Policy and Terms of Service are the best references for what's expected on the platform. Reviewing those before starting a new project would be the right move.