Privacy Policy
Remopipe runs your mobile test workflows on real devices. This page describes what we store to do that, how long we keep it, and how you get it out or have it deleted. Operated by Remopipe. Contact: admin at remopipe.io.
1. What we store
- Account — your email address and authentication records (handled by Supabase Auth), plan and subscription state.
- Workflows — the automations you build: nodes, parameters, schedules. These are content you author; we do not use them to train anything.
- Run history — for each run: which steps ran, their results, notes and errors, timing, the device and platform used, the worker build that executed it, and screenshots captured at each step. Screenshots are pictures of the device screen and may therefore contain whatever your app displayed, including data you entered during the run.
- Failure diagnostics— when a step fails, we additionally capture the screen's UI element tree and page source at that moment, so the failure can be reproduced and fixed without re-renting a device.
- Uploaded builds and files — app packages (APK/IPA) and AI models you upload to run on a device.
- Usage and metering — device-session start/end and billed seconds, AI token counts. These drive your usage page and your invoice.
- Product usage — which pages of the app you open and which nodes you add in the editor, with a timestamp. Page addresses are stored without the ids in them, and we do not record your IP address or device. We look at this only in aggregate, to decide what to improve.
- Launch list — if you ask to hear when Remopipe opens, your email address, when you signed up and when you confirmed it. It is used for two emails only: a reminder a week before launch, and the announcement on launch day. You can remove yourself with the link in any email the list sends, and the address is deleted rather than kept.
- Contact messages — what you write through the contact form on our launch page and the email address to reply to. An automated screen reads each message first; messages it judges to be sales or promotional pitches are discarded without being stored, and the rest are kept until we have answered them.
- Operational logs — technical logs from the machines that drive the devices, used to diagnose faults.
We do not sell personal data, and we do not use your content for advertising or model training.
2. How long we keep it
Run history is kept for as long as your subscription is active, and for 6 months after it ends. If you resubscribe within those 6 months, nothing is lost. If you have no subscription, runs are kept for 6 months from the date of the run. After that the run record is deleted automatically, together with its screenshots and any stored diagnostics. Deletion is permanent and we cannot restore a run afterwards.
Closing your account deletes your run history immediately — the 6-month window above applies to a lapsed subscription, not to a deletion request.
If you need runs for longer, export them before they expire: Runs → choose a date range → Download archive. You get a .tar.gz containing the full record of each run in that range plus its screenshots, which is yours to keep. The Runs page shows how long your oldest run has left and warns you in the last 30 days.
| Data | Retention |
|---|---|
| Run history + step screenshots | While your subscription is active, then 6 months after it ends (6 months from the run without a subscription) |
| Failure diagnostic captures | 14 days from the run |
| Operational logs (worker infrastructure) | 14 days |
| Product usage (pages opened, nodes added) | 180 days, or until you close your account |
| Workflows, schedules | Until you delete them, or you close your account |
| Uploaded builds / AI models | Until you delete them; over-quota builds may be removed after a plan downgrade grace period |
| Usage & billing records | As long as required for billing, accounting and tax obligations |
| Account record | Until you close the account |
3. Devices you rent
Runs execute on shared real devices rented from a device cloud (currently AWS Device Farm). We do not own the hardware. When a session ends, the provider resets the device; we do not retain anything from it beyond the artifacts described above. Do not use production credentials or real personal data on a shared rented device.
4. Who processes data on our behalf
- Amazon Web Services — device cloud (real devices), compute for the workers.
- Supabase — database, authentication and file storage.
- Vercel — application hosting.
- Stripe — payments (card details go to Stripe; we never receive them).
- Resend — transactional email.
- Anthropic and OpenAI — the managed AI features, when you use a node or chat that calls them.
Data may be processed outside your country, including in the United States. [Add the transfer mechanism used for EU/UK personal data — e.g. Standard Contractual Clauses — before launch.]
5. Your rights
You can access and export your run history at any time from Runs, and delete workflows, runs and uploaded files from the product. If you are in the EU/UK you also have rights of access, correction, erasure, restriction, portability and objection. Closing your account deletes your account data, workflows and run history; records we must keep for billing and tax are retained for that purpose only. To exercise any of this, contact admin at remopipe.io.
6. Cookies
We use cookies that are necessary for signing in and remembering your theme preference. Non-essential cookies are only set with your consent, which you are asked for on your first visit from the EU/EEA and can change at any time.
7. Changes
If we change what we keep or for how long, we will update this page and — for a material change such as shortening the run-history period — tell you in the product before it takes effect, with enough time to export.