Support
Last updated: 2026-08-13
Relayium is run by a small team. Every message reaches a person who works on the product — there is no ticket maze and no chatbot in front of us.
Email support@relayium.com and we aim to reply within two business days.
Billing and subscriptions
Who you deal with depends on where you subscribed. A subscription bought on the web is billed by Stripe and managed here, on your Relayium account page. A subscription bought inside a Relayium app installed from the Apple App Store, including the Mac App Store, is billed by Apple and managed in your Apple account settings.
For a web subscription you can manage most of it yourself without writing to us. From your account page you can upgrade, downgrade, or cancel at any time; cancelling keeps your plan running until the end of the period you already paid for, and then drops you to Free. Write to support@relayium.com for anything the account page cannot do — a refund request, a wrong charge, an invoice or VAT detail, or a payment that failed for a reason you cannot see.
For an Apple-billed subscription, change the plan or turn off auto-renewal in your Apple account settings, and ask Apple for a refund — we cannot cancel or refund an App Store purchase for you. We can still help you work out what happened: if your Relayium plan does not match what you bought, or a charge looks wrong, write to support@relayium.com and we will check what Apple has told us about your subscription.
- On the web, upgrades take effect immediately and are prorated; downgrades take effect at the end of the current billing period, so you keep what you paid for.
- Apple-billed plan changes, cancellations and refund requests go through Apple, not through us.
- Include the email address on the account. Never send us your card number — we never see it, and we will never ask for it.
Transfers and technical problems
If a transfer will not connect or a download fails, tell us which mode you were using (realtime pairing code, or a stored download link), the browsers and operating systems on both ends, and roughly when it happened. That is almost always enough to identify the cause.
Bug reports and feature requests are welcome in public on GitHub, where you can also read the code that handles your files.
- Do not paste a download link or its key into a public issue — the key in the link is what decrypts your file.
Self-hosted nodes
If you run your own relay or storage node, questions and problems belong on GitHub rather than in email, so the answers stay searchable for everyone else running one.
Security reports
Please report vulnerabilities privately through GitHub's vulnerability reporting on the repository rather than opening a public issue, so a fix can ship before the details are public. Our threat model and what we do and do not defend against are documented on the Security page.