Your file never leaves your browser.

1. Controller and contact

Controller

KAUA MORAIS E SILVA LTDA

Country

BR

Address

Av. Araucárias, Ed. Via Enseada, Águas Claras, DF, 71936-250, Brasil

Privacy contact

support@sourcerow.co

2. Your file, and the twenty numbers

Your CSV file is never uploaded. It is read in your browser, and nothing else in it is transmitted.

When a subscriber generates a brief, the ten template fields from each of the two rows are sent to our server so that it can build the document. That is a period label, a client alias you choose, and eight aggregate numbers such as tickets opened and patch compliance. No credential, no ticket text, no hostname, no end-user data and no real client name is involved, because the template has nowhere to put them.

Those fields exist only in memory while the brief is being built. They are never written to disk, never logged, and cannot be retrieved afterwards by us or by anyone else. We keep only a count of how many briefs you generated this month, so the monthly allowance can be enforced.

The free sample runs entirely in your browser and reaches us not at all.

3. What we do store

Subscription

Your email, subscription status and renewal date

Payment

Held by Stripe. Sourcerow never receives card details

Usage events

Cookie-free counts of product actions, with no identifier tied to you

Brief allowance

A per-month count of briefs generated, with no brief content

Retention

90 days for contact records

Usage events record that an action happened, not who did it. They carry no advertising identifier and no cross-site tracking.

4. Behaviour measurement, and what it can never see

Public pages load Microsoft Clarity, a measurement tool operated by Microsoft. It records how pages are used — pointer movement, clicks, scrolling and which pages were opened — so the layout can be judged on evidence instead of opinion. It sets its own cookies to tell one visit from another. It is not advertising, and no profile is sold or shared for advertising.

Four things are masked in the page itself, not merely in a vendor setting, so they are never transmitted: the CSV you paste or upload, the brief generated from it, your access key, and every email field. A session recording of this site cannot contain your numbers, your clients or your credential.

The operator area is excluded. If you would rather not be measured at all, browser Do Not Track and tracker blocking both stop the script from loading, and nothing on this site stops working without it.

5. Why we hold it, and who else sees it

Your email and subscription state exist to give you access to what you paid for, to send receipts and service notices, and to meet accounting obligations. Usage counts exist to see which parts of the product work.

Two processors are involved: Stripe processes payments and holds the payment relationship, and the hosting provider runs the server. Sourcerow does not sell data, does not share it for advertising, and has no marketing tracking to opt out of.

The service is operated from BR, so if you are elsewhere your data is processed internationally. Stripe operates globally under its own published terms.

6. Your rights, and how deletion actually works

You can ask for a copy of what we hold, ask for it to be corrected, or ask for it to be deleted. Write to support@sourcerow.co from the address on the account.

Deletion is real and verified: the records are removed and the deletion is confirmed against the database rather than assumed. Backups containing the record are destroyed as part of the same operation instead of being left to expire.

One trace deliberately survives. We keep an irreversible fingerprint of the deleted address so that a later submission cannot silently recreate the record you asked us to remove. It cannot be read back as an email address, and it is never used to contact you or to build any list.

Cancelling a subscription does not delete your data, and deleting your data does not stop you subscribing again later if you choose to. Stripe keeps its own payment records for the period its own obligations require, independently of us.

7. Version

Notice version

2026-08-17-subscription-single-and-measurement-v4|retention-v1-expiry-heartbeat|days=90|recollection=implemented_v1

Approved at

2026-08-17T00:55:00Z

Changes that affect what is collected or why are announced by email to subscribers before they take effect.