Skip to content
What does linking a service to a public support thread disclose?
iam_nell
OP

18 days ago

Before opening a technical support request, I want to understand Central Station's privacy controls. When a Hobby user selects a service for a public thread, which details become visible to everyone, and which are visible only to Railway staff? Please clarify whether this includes project, service and environment names or IDs, deployment details, logs or account information.

Is there a way for a Hobby user to request general technical guidance without linking a service or exposing those details? This is a general account and privacy question; no service-specific investigation or account changes are requested.

$20 Bounty

4 Replies

Status changed to Awaiting Railway Response Railway • 18 days ago


Railway
BOT

18 days ago

Linking a service does not make any service information publicly visible, even on a public thread. It makes non-sensitive details, such as the service name, deployment source, and build and start commands, available in the support context. Only Railway admins can see those details. Linking a service does not expose sensitive information.

You can request general technical guidance without linking a service, just as you have here. No service is linked to this thread. For questions about a specific service, though, we need it linked to investigate and answer.

The Hobby plan does not include a guaranteed response from a Railway admin for general technical questions. Those questions will be answered by our support bot or the community.


Status changed to Awaiting User Response Railway • 18 days ago


iam_nell
OP

17 days ago

Could a Railway staff member confirm this privacy policy? Specifically, when a service is linked, are project and environment names or IDs, deployment details, logs, and account information visible only to Railway admins, and which of those fields become available to them? Also, for a general PostgreSQL recovery-method question prompted by a Railway service, is there a supported way to ask without linking it? The Technical Help form's N/A option says 'This is unrelated to a Railway service,' which would not accurately describe that case. No service-specific investigation or account changes are requested.


Status changed to Awaiting Railway Response Railway • 17 days ago


Railway
BOT

17 days ago

Linking a service doesn't make any of its information public, even on a public thread. The linked details go into the support context and only Railway admins can see them. They are non-sensitive service details such as the service name, deployment source, and build and start commands. Linking doesn't expose sensitive information, and logs, secrets, and account information are not published to the thread.

A general PostgreSQL recovery-method question can be asked without linking a service, even if a Railway service prompted it. A link is only needed when you want us to investigate that specific service and answer about it. If you don't link one, describe the question as general guidance in the thread body.


Status changed to Awaiting User Response Railway • 17 days ago


iam_nell
OP

17 days ago

I'm asking for general PostgreSQL recovery-method guidance, not an investigation of a linked service or any account changes.

Consider PostgreSQL 18 on a nearly full volume. A large import-history table contains disposable feed snapshots mixed with review rows that must be kept. Verified off-volume copies exist. TRUNCATE followed by replay in one transaction needs more working space than remains, because the old table must stay available for rollback. Committing TRUNCATE first would free space sooner, but creates a non-rollbackable gap before the review rows are restored.

Without adding storage or manually deleting WAL files, is there a documented way to create safe working room or reclaim only the import history? What minimum headroom, writer controls, and crash-recovery steps would need to be verified before attempting it? If there is no safe route under those constraints, please say so.


Status changed to Awaiting Railway Response Railway • 17 days ago


Railway
BOT

17 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • 17 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...