SpeedTester Privacy Policy
Version: production-20261015-01. Published and effective: 15 October 2026.
1. Controller and scope
Edson Angelo Carara, an individual using the CararaLab brand, is the controller for SpeedTester at https://speedtester.cararalab.com.br. Support and data-rights contact: fale.conosco@cararalab.com.br.
This policy covers the portal and ingestion from paired clients. Independent software instances may have different operators and policies. Public comparisons and awards will be activated only after implementation and assessment for safe disclosure.
2. Data and purposes
To authenticate and link accounts, the Server stores the identity-provider identifier and the account identifier within that provider. CararaLab's Casdoor intermediates sign-in. SpeedTester Server does not request passwords, contacts, messages or social posts. Attributes presented by the provider during sign-in are not automatically added to the application's database.
To document choices, we retain account and session identifiers, document versions and hashes, language, server-recorded acceptance time, and authorization and withdrawal events. To pair and protect clients, we process installation identifiers and labels, public keys, credential hashes, encrypted delivery data and revocation status.
For measurement context, we process operator, country, region, city, access technology, Ethernet or Wi-Fi, and contracted speeds where supplied. We do not request an exact residential address or GPS coordinates. Do not include personal information in free-text profile fields or installation labels.
To ingest and validate results, we process separate values and statuses for supported download, upload, latency, jitter, loss, duration, transferred traffic and retransmissions, together with method, time, authorizations, attempt identifiers, hashes, signatures, receipts and audit events. Metrics not collected remain identified as such.
Network services process the IP address during connections, and it may appear in technical error or security records. The application's pairing limiter uses a derived identifier rather than storing the plaintext IP in that table. Information voluntarily sent to support is used to handle the request. Identifiers and hashes linkable to an account are treated as personal data, not anonymous data.
3. Choices and processing grounds
Account operation and requested features rely on performance of the requested service. Voluntary measurement contribution and its statistical use require specific consent. Records strictly necessary for security and abuse prevention are processed according to necessity and the legitimate interest in protecting the service and participants, with the possibility of objection. Legal obligations and the exercise of rights may justify specific retention.
Sign-in, terms acceptance, reading the policy and contribution authorization are separate acts. Participation checkboxes are not preselected. You can refuse or withdraw contribution through the portal; the server then blocks credential renewal, new authorizations and result submissions, including pending results. Pausing a client, revoking credentials, withdrawing consent and requesting deletion are different operations.
We do not sell account lists or use identifiable data for targeted advertising in this service. An incompatible new purpose requires advance information and an appropriate basis; where consent is required, fresh authorization is necessary.
4. Disclosure and recipients
Public results, when available, will be limited to aggregates assessed for sample size and identification risk, without names, email addresses, account/client identifiers, tokens, IP addresses or home addresses. Filters and small groups require additional care; a minimum observation count alone does not guarantee anonymity. Awards depend on a published methodology and data review.
CararaLab's Casdoor and enabled identity providers process sign-in according to their roles and policies. The actual list appears during authentication; we do not assume Google, Meta or X are enabled. Hosting infrastructure receives access only as required for its operation; Cloudflare provides public DNS. Software and automation use GitHub without publishing participant records, credentials or measurements in repositories.
Test targets receive traffic necessary for measurement and may observe the connection's IP address. Do not send unauthorized traffic to third parties. Additional external services, automatic IP identification and new transfers are not authorized merely because they appear in a plan. Where applicable, foreign infrastructure or providers must use required transfer mechanisms; participants may request information about recipients and processing through the stated contact. Authority requests are fulfilled only on an applicable basis and within their scope.
5. Security and storage
We use HTTPS, individually revocable credentials, possession proofs, signatures, receipts, a restricted database and separation between runtime and administrative migration access. The local community queue protects its contents with authenticated encryption and a separate storage key with restricted permissions. This does not independently establish trust in participant-controlled equipment.
This policy does not claim that every central disk or database is encrypted: access controls, local encryption and transport protection have different scopes. No protection removes every risk. Incidents will be handled and communicated where required by applicable rules.
6. Duration, withdrawal and deletion
Accounts, profiles and linkable measurements are retained while necessary for participation and the stated comparison history, until closure, a deletion request or an assessment that they are no longer necessary. Acceptance, authorization, audit and abuse evidence may be retained with restricted access while needed to demonstrate choices, resolve disputes, exercise rights or meet a specific obligation. There is no general permission for perpetual retention.
Expiry of a session, pairing code or token ends its usability; it does not immediately delete every associated record. This release has no general automatic history purge: the operator handles deletion and closure requests through the contact channel, assessing the basis for each retention and explaining the action and applicable timeframe.
Withdrawal does not automatically invalidate earlier processing, but you may request deletion of consent-based data subject to lawful retention exceptions. Immutable records do not prevent the exercise of rights: corrections may be appended without falsifying originals; blocking, unlinking or deletion are assessed where applicable. Truly anonymous aggregates may remain without allowing a participant to be identified.
Files and queues on your equipment remain under your control and are not remotely erased when an account closes. Any recovery copies require separate handling; revocation does not mean instant backup deletion. Withdrawn authorizations or revoked credentials will not be restored to resume contributions without your valid choice.
7. Your rights and requests
You may request confirmation of processing, access, correction, information about sharing and the consequences of refusing consent, consent withdrawal and, where applicable, anonymization, blocking, deletion and portability. You may also challenge automated decisions and request review of restrictions. Send requests to fale.conosco@cararalab.com.br without passwords or tokens; identity checks will be proportionate.
We will explain actions and any justified limitations within applicable timeframes. You may also contact Brazil's ANPD and competent authorities. The principal references are Brazil's General Data Protection Law — Law No. 13,709/2018 — and ANPD guidance on data-subject rights.
8. Languages and updates
Portuguese and English form one immutable version. Acceptance records hashes and the viewed language. Material changes receive a new version, a portal notice and mandatory renewed acceptance before contribution resumes. The current policy remains readable without starting measurements.
References: https://www.planalto.gov.br/ccivil_03/_ato2015-2018/2018/lei/l13709compilado.htm and https://www.gov.br/anpd/pt-br/assuntos/titular-de-dados/direito-dos-titulares.
