1 · Who is responsible

The controller of the personal data described here is Roberto Alexandre Schopf, at Servidão Luxemburgo 375, Joinville, Santa Catarina, Brazil, CEP 89202-315. For anything on this page, including access, correction and deletion requests, write to support@rasqintelligence.com.

2 · What we collect, and why

2.1 · When you contact us or use a free tool

The contact form and the free tools (fit assessment, OEE calculator, bottleneck ROI) ask for your name, work e-mail, company and whatever you write in the message field. If you used a calculator first, a plain-text summary of its result is attached, so we can answer knowing what you were looking at.

That submission goes to two places:

• Formspree, which delivers it to us as e-mail. It receives the full submission.
• Our own record, on Cloudflare. Here it is deliberately reduced: we store the domain of your e-mail address, never the address itself — @yourcompany.com, not you@yourcompany.com — plus a coarse market derived from that domain, the subject, and the message text. The full address is transmitted so the domain can be derived, and is not retained.

The purpose is to answer you and to understand which markets ask for what. Basis: our legitimate interest in responding to a business enquiry you initiated.

2.2 · When you have access to the products

Sign-in uses a one-time code sent to your e-mail — there is no password to create, and we never handle one. Your e-mail address is processed to let you in and to know that you are entitled to the products.

If you hold a licence, we keep the licence key, your e-mail address, the product, the issue and expiry dates and the transaction identifiers from the payment provider. That record is what makes the licence work; we cannot run it without holding it.

2.3 · When you use the software

This is the part that matters most, and it differs by product:

• Line Simulator. Your line definition — stations, cycle times, operators, breakdown and setup parameters, recipes and distributions — is sent to a server to be computed, because that is where the engine runs. It is processed in memory and is neither written to disk nor logged. Your financial configuration is never sent at all: prices, margins and demand stay in your browser. Saved lines and backups live in your browser.
• Industrial Investment Analyzer. The server calculates and stores nothing. There is no database of business cases. Your case lives in your browser and in a file you export and keep. An automated test fails the build if any financial field could reach a log.
• Manufacturing Project Manager. Same posture: single user, data in your browser plus a file you export. The server signs a snapshot on request and does not retain it.
• 6Sigma Studio. Your datasets and analyses stay on your machine.

The AI commentary in the Investment Analyzer is off by default. It only sends anything if you switch it on for a specific case, and it shows you the exact payload before it leaves your machine.

2.4 · This website

This site sets no cookies at all — not for advertising, not for analytics, not for anything else. The only thing it stores in your browser is your choice of light or dark theme, under the key rasqi_site_theme, and only once you click the toggle. That is a preference, kept on your device, and it never reaches us.

Two things on the page are served by someone else, and both are worth naming:

• Audience measurement, by Cloudflare. Our hosting platform counts page views so we know which pages are read. It is cookieless: it stores nothing in your browser and gives you no identifier, so it cannot follow you here or anywhere else. What it records is the page, where you arrived from, and coarse technical facts such as country and browser.
• The Orbitron typeface, served by Google Fonts. Loading it means your browser asks fonts.googleapis.com for the font file, and that request carries your IP address to Google as any request does. No cookie is set and nothing is stored.

Neither is used to build a profile of you, and neither touches the products themselves — inside the four applications there is no measurement of this kind at all.

3 · What we never collect

• Card details. Payments are handled by Paddle as Merchant of Record. We never see, receive or store a card number.
• Your financial configuration in the Line Simulator — prices, margins, demand.
• Your business cases and projects. There is no server-side copy to hand over, lose or be compelled to produce.

4 · Who processes data on our behalf

• Cloudflare — hosting, the access gate, the records described in 2.1 and 2.2, and the cookieless audience measurement on this website described in 2.4.
• Google — only the delivery of the Orbitron typeface on this website, as described in 2.4. Nothing else reaches them, and the products do not use it.
• Formspree — delivery of contact-form submissions.
• Paddle — payment processing as Merchant of Record, and the buyer details attached to a purchase.
• Anthropic — only if you explicitly switch on the optional AI commentary, and only for the payload shown to you beforehand.

Processing takes place on infrastructure that may be located outside your country. Where that involves a transfer from the European Economic Area, it is made under the safeguards those providers publish.

5 · How long we keep it

• Enquiries: for as long as needed to answer and to keep a record of the commercial conversation.
• Licences: for the life of the licence and for as long afterwards as tax and accounting rules require.
• Reduced market records (2.1): retained without your e-mail address, so they cease to identify you.
• Your engineering data: we hold none, so there is nothing to delete on our side. Deleting it is deleting the file, or clearing your browser.

6 · Your rights

You can ask what we hold about you, ask for it to be corrected, ask for it to be deleted, ask for a copy, or object to our use of it. Write to support@rasqintelligence.com. We answer within 30 days.

Two honest limits. Deleting your licence record ends your access, because that record is the licence. And we cannot delete data we never had — for anything you created in the products, the copy is yours.

7 · Security

The products are served over HTTPS only and sit behind an authenticated gate that is verified in code on every request, not merely assumed from the presence of a header. Payment data never touches our systems.

8 · Changes

If we change how any of this works, this page changes in the same edit as the software. The effective date at the top tells you which version you are reading.