Contact

Before you write: do not send your session key

Never include a share key or a session PIN in an email, a bug report or a screenshot. The key is the whole of the security — anyone holding it can open the session and read it. If you need to demonstrate a problem, start a throwaway session and use that. A screenshot of the app is fine as long as the key panel is cropped out or the key is blanked.

Support and general questions

info@realtimeclipboard.com. Expect a reply within about three working days.

Most "it is not syncing" questions have a faster answer than an email can give, because the causes are few and well understood — a browser that will not read the clipboard without permission, two devices on different keys, or an extension blocking the connection. The sync troubleshooting guide walks through them in order, and the help section covers installing on each platform. Try those first and you will usually be done in a minute.

Bugs and feature requests

Open an issue on GitHub. This is better than email for anything reproducible: it is public, so the next person hitting the same problem finds the answer, and it is where the fix will be linked when it lands.

A useful report says which browsers and operating systems were on both ends, what you expected, what happened instead, and anything in the browser console. Everything in the project is open source, so if you would rather send a pull request than a description, that works too.

Security disclosures

Security problems have their own route and should not go in a public issue. Open a private advisory — it stays visible only to you and the maintainer — or email info@realtimeclipboard.com if that form is not available to you.

Expect an acknowledgement within about a week. Valid reports are credited in the advisory and the changelog unless you would rather they were not. There is no bug bounty and no money — it is a free tool with one maintainer, and pretending otherwise would waste your time. The full policy, including which known trade-offs are deliberate design rather than defects, is in SECURITY.md.

Privacy requests

Send them to info@realtimeclipboard.com. Be aware in advance that the usual answer is that there is nothing to hand over: there is no account, no email on file and no server-side record of any session, so the material a service would normally hold about you does not exist. For the advertising and analytics data Google holds, the links in the privacy policy reach further than any request to this site could.

Press, advertising and business enquiries

info@realtimeclipboard.com, with "press" or "business" in the subject. RealtimeClipboard is published by CadNative. Logos and the icon set are in the repository and may be used to refer to the project.

Why there is no contact form

A form has to post somewhere, and that would mean a server that stores messages. The only server in this project is the relay, which is built to be incapable of storing anything and is more useful staying that way. An email address does the same job and leaves the architecture honest.