Legal

Privacy Policy

Last updated · support@raeda.build

Changes made take effect for existing accounts on .

This policy explains what Raeda stores about you, why, who else handles it, how long it is kept, and how to delete it.

1. OVERVIEW

Raeda ("we", "us" or "our") runs the Raeda app and website (the "Services"). This policy explains how we collect, use and protect your information when you use them. By using the Services, you agree to it.

We do not sell your data, we do not show ads, and we do not use your data to train AI models.

2. INFORMATION WE COLLECT

We collect only what we need to run the Services.

Your account: your email address, your password if you set one (kept only as a secure hash, which no one can read back), and the display name you choose.

If you sign in with your account at another service, that service gives us your email address, your name, a link to your profile picture and an identifier for your account there. Your name there becomes your display name, which you can change. If you change your email address, any such sign-in that does not use your new address is removed from your account once the change completes.

Your builds: everything you enter for each build: the van and its dimensions, the components you place (with any link you added them from), tasks, budget items and categories, wishlist items, journal entries and saved layouts.

Your files: the product images, install photos, van photos and receipts you upload, and the product image we copy from a page you paste. They are kept in private storage that only your account can read.

Your component library: the components you save to your library, each with its details and a copy of its product image, kept with your account rather than with any build.

Your settings: your theme, your rotation step, when you accepted the safety notice, which version of the Terms and this policy you agreed to and when, when you saw our notice of a change to them, when we sent you our welcome email and which notice of a change to them we last emailed you, and whether you have dismissed the getting-started list and the workspace tour.

Your plan and usage: your plan, how many extractions you have used and a record of each one spent, how many builds you have started, how many components, budget items, wishlist items and journal entries each build has added, and when a Builder plan ended. The plan limits are counted from these.

Extraction records: one record each time the app reads, or tries to read, a product or van page for you, which we use to measure how well extraction works and what it costs: the website’s address without the page’s path (example.com, not the full link), how long it took, how much AI processing it used, whether it worked, the details it found, and how many of them you kept.

Payment records: what our payment processor tells us about your subscription and purchases, described under Payment Information below.

Messages you send us: if you write to us through the contact form, your name if you give one, your email address, the topic you choose and your message. They are kept in our support mailbox.

Change history: a record of what was added, changed and deleted in your account and builds, including what each record held. It does not record moving or rotating a component, which of its configurations a component is shown in, changes to your saved layouts, or changes to your display name and preferences. How long it is kept is described under Data Retention below.

Collected automatically: the cookies described below, the standard request logs our hosting and database providers keep, such as your IP address, your browser and the time, to run and secure the Services, and, when something fails, the error report described under Third-Party Services. We also collect page-view statistics through the analytics service described under Third-Party Services, which uses no cookie and does not follow you across other websites.

3. HOW WE USE YOUR INFORMATION

To run Raeda for you: to save and show your builds, to work out their figures, to read the pages you ask it to read, to sign you in, to apply your plan and its limits, to take payment, and to send the emails your account needs. Those emails confirm your address, reset your password, and tell you when your email or password changes. They also welcome you when you sign up, confirm that your account has been deleted, tell you when your paid plan ends, and give you advance notice of changes to the Terms or this policy. We send no marketing email.

We also use the extraction records to measure how well extraction works and what it costs, and the change history to investigate problems and resolve disputes. When you write to us through the contact form, we use your message to answer it, and your IP address to limit how many messages one address can send and to tell people from automated programs. We use the page-view statistics to see which pages are visited and how people find the Services, so that we can improve them. We use your data for nothing else.

4. PAYMENT INFORMATION

Payments for the Builder plan and for prepaid extractions are handled by our payment processor. Your card details go to the processor and never to us, and we cannot see them. When you first open the checkout to subscribe, before you pay anything, we give the processor your email address so that it can create your customer record. With that record and with each checkout, we also give it an identifier for your account, so that its records can be matched to yours.

From the processor we receive and keep: references to your customer record and subscription; the subscription’s status, whether it is monthly or annual, when its current period ends, and whether it is set to cancel; a record of each prepaid pack you buy, with how many extractions it added and what you paid; and a record of each payment event the processor sends us. We use these only to apply your plan and your prepaid extractions.

The processor keeps its own records, including your customer record and your payments, also after you delete your account.

5. THIRD-PARTY SERVICES

We use other companies’ services to run Raeda, and each receives only what its part needs: hosting for the app and this website; our database, sign-in and file storage, which hold everything described above; a page-fetching service, which receives each link you ask the app to read; an AI model provider, which receives the text of that page; an email delivery service, which receives your email address to send your account emails, and delivers a message you send through the contact form (your name, address and message) to our support mailbox; a rate-limiting service, which receives your IP address (for an IPv6 address, its first half) when you send a message through the contact form, and whose record of it is set to expire after an hour; a bot-check service on the contact page, which sees your browser and your IP address in order to tell people from automated programs; a sign-in service, if you choose to sign in with one; our support mailbox, if you write to us; an analytics service and an error-monitoring service, both described below; and our payment processor.

The analytics service counts visits to the app and this website. Since your browser sends it each page view, it sees your IP address, as any site your browser contacts does, and works out your approximate location from the request. For each page you open, it records the time, the page’s address, the address of the site that linked you to it, your approximate location (country, region and city), your browser and operating system, with their versions, and your device type. It sets no cookie. It tells one visitor’s page views apart by a code worked out from each request, which is reset every day and discarded after 24 hours, so it cannot link your visits on different days or on other websites. Its records are not tied to your IP address, and it never receives your email address, your name or what you write. We see only totals, such as how many people opened a page.

The error-monitoring service receives reports of errors and failures in the app and this website, and the app’s diagnostic records of them. For an error in your browser, the report gives the page’s address, without anything after its “?”, and since your browser sends it, the service also sees your browser and device type, as any site your browser contacts does. Where a failure concerns them, it receives the identifiers of your account, builds and records, and the address of a page you asked the app to read, without anything after its “?”. It never receives your email address, your password or what you write, and it is set not to keep your IP address.

When the app reads a page for you, nothing from your account (not your email, your name or your builds) is sent with the link or the page’s text. If the page has a product image, we copy it into your private storage.

These providers may store and process your data in the United States and in other countries where they operate. We do not control their privacy practices.

6. COOKIES AND SESSION DATA

Raeda sets only the cookies it needs to work: the ones that keep you signed in and complete the links we email you (with a one-hour one while you reset your password), one that completes a sign-in with another service, and one that remembers your light or dark theme. It also keeps one note in your browser, for the current tab only: that you have opened the getting-started list, so its reminder dot stays cleared. The contact page also runs the bot check described under Third-Party Services in your browser; it sets no cookie unless its optional pre-clearance setting is on, and we do not use that setting. The analytics described under Third-Party Services sets no cookie. There are no advertising or tracking cookies, so there is no cookie banner.

7. DATA RETENTION

We keep your data while you have an account. If a Builder plan ends and some of your builds are locked, they and their files are kept until you delete them or your account, or ask us to. The one exception is a locked build’s Trash: a component already in it is still removed for good, with its files, about 7 days after it was deleted, as described below, and cannot be restored while the build is locked.

A deleted component goes to its build’s Trash, where you can restore it, and is removed for good about 7 days later. Reset 3D layout, in a build’s settings, skips the Trash: it deletes every placed component, and everything already in the Trash, at once.

Anything else you delete, such as a build or a journal entry, or your whole account in Settings, is removed from the app at once. Deleting your account cannot be undone.

Your files are deleted along with what they belong to. A daily cleanup also deletes any file that nothing in your builds uses any more, which catches the files of a component removed from the Trash and any file a deletion missed.

The change history keeps a copy of what you change and delete for a time. While your account exists, its record of your builds and other content is kept for 12 months, so a deleted entry’s text stays in it for up to a year, and its record of your sign-up, plan, usage and payments is kept as long as the account exists. After you delete your account, its record of your content is deleted 30 days later, and its record of your sign-up, acceptances, usage, payments and the deletion itself 2 years later, so that we can answer a dispute raised after the account has gone. The change history is not shown in the app.

A message you send through the contact form is kept in our support mailbox for up to 12 months, then deleted. The rate-limiting service’s record of your IP address expires after an hour.

The error-monitoring service keeps its error reports and diagnostic records for up to 90 days.

The analytics service keeps the page-view records described above. The code it tells visitors apart by is discarded after 24 hours.

Copies may also remain in our database provider’s backups until those backups expire.

8. DATA SHARING

We do not sell, rent or trade your personal information. We share it only with the service providers described above, as far as each needs it, and with legal authorities where the law requires us to.

9. DATA SECURITY

We take reasonable steps to protect your information: it travels over encrypted connections, your files are in private storage, and the database’s access rules let each account read only its own data. No system is completely secure, and we cannot guarantee absolute security. If we learn of a breach that affects your data, we will tell you.

10. YOUR RIGHTS

You can see and correct almost everything we store in the app itself, and delete your builds or your whole account in Settings. Depending on where you live, you may also have rights to access, correct or delete your personal data. To ask for a copy of your data, or to use any of these rights, email support@raeda.build.

11. CHILDREN

Raeda is not for anyone under 16. If you think a child has made an account, email support@raeda.build and we will delete it.

12. CHANGES TO THIS POLICY

We may update this policy. When it changes, the "Last updated" date at the top changes too. If a change is material, we will post a notice in the app at least 30 days before it takes effect, giving the date it takes effect. If you keep using the Services from that date, you agree to the updated policy. If you do not agree, stop using the Services before then. You can delete your account in Settings. If you create your account after a change is published, it applies to you from when you agree to this policy. Other changes apply once they are published here.

13. CONTACT US

Questions about this policy or your privacy: support@raeda.build.