Support

Contact

The fastest way to reach the R-Data team is email. We read every message and aim to respond within one business day (Monday through Friday, Pacific time).

nate@builtbyape.com

What to include in a bug report

To help us diagnose quickly, please include as much of the following as you can. None of it is required, but each detail shortens the back-and-forth.

• The migration route you were running (e.g., Lucid to Miro, FigJam to Miro, Lucid to ZIP).
• The source document URL or board ID, if you are comfortable sharing it. We will not open it without permission.
• A screenshot of the R-Data dashboard, the Active Migration view, or the target platform showing the issue.
• The browser and OS version you are using (Chrome is our primary target; other Chromium-based browsers mostly work but are not officially supported).
• The time and date (including timezone) when you hit the issue. This helps us correlate with backend logs.

Account, billing, and refunds

Billing questions, refund requests, and questions about document credits are handled by email. Include the email address on your R-Data account and a brief description of the issue. See also: Terms of Service.

Privacy and data

For questions about how R-Data handles your data, which platforms it connects to, or to request deletion of your account, see our Privacy Policy. You can also email the address above with the subject line “Privacy request” and we will respond within one business day.

Documentation

The Guide covers the supported migration routes, how connections work, and what to expect on the target platform. The Shapes page lists every source shape class R-Data understands and how it maps to each target platform.