0 points

Privacy

What CeKiN stores, and why

This page says plainly what CeKiN stores, what for, for how long, and who can see it. It follows what this site really does today.

In short

  • Testing needs no account. Without an account, CeKiN does not know your name or e-mail address.
  • Every test stores its result, the public IP address of your connection (12 months), and device details from your browser.
  • Location is stored only if you allow it. The exact point is never shown to anyone else.
  • A comparison test is run and published by M-Lab — publicly, forever, including your IP address. That is why your consent is always asked first.
  • There are no ads and no third-party trackers on this site. Your data is not sold.

What is stored

One row per kind of data: what, what for, for how long, and who can see it.

What is storedWhat forFor how longWho sees it
Test results: score, download and upload speed, latency, jitter, packet loss, the time of the test and its code. This is the service itself: your history, and the average figures per area. For as long as CeKiN runs; nothing is deleted automatically yet. You and CeKiN's operator. Others only see averages per area, and only once that area has at least 10 tests from 3 people. One exception: someone who records a fixed line as their package and answers that they own the connection sees how many tests other people made on that line during the package assessment window and their median download — never who tested, when, or any single result.
The public IP address of your connection at the time of the test. ↓ Keeping the data sound: recognising the internet provider and finding implausible tests. 12 months, then deleted automatically. The test result stays. You (your address is shown on your own test screen) and CeKiN's operator. Never anyone else.
A fingerprint of the IP address: a string made from the address that cannot be turned back into it. ↓ So tests from the same connection can still be recognised after the address is deleted. For as long as CeKiN runs; nothing is deleted automatically yet. CeKiN's operator.
The name of the internet provider, its network number and its country. ↓ So results can be read per provider. For as long as CeKiN runs; nothing is deleted automatically yet. You and CeKiN's operator. Other people see only the number of tests per provider in an area, once that area has reached the threshold above.
Only if you allow it: your position (latitude and longitude), its accuracy, and the 500-metre square it falls in. ↓ Placing the test in the right area. For as long as CeKiN runs; nothing is deleted automatically yet. You (on the Map page, under “My tests”, once signed in) and CeKiN's operator. Never anyone else.
The area names of that position: village, district, regency/city, province. ↓ The map of internet quality by area. For as long as CeKiN runs; nothing is deleted automatically yet. You and CeKiN's operator. Other people see the area only as combined figures, once it has reached the threshold above.
Details from your browser: browser name and version, operating system, kind of device, screen size, language, time zone, and the page the test was started from. Understanding the result — a test from a phone and one from a computer are not the same. For as long as CeKiN runs; nothing is deleted automatically yet. You (in History and in your data download) and CeKiN's operator.
What the browser says about your connection, if it is willing to: connection type (WiFi, mobile data, cable), its estimated class and speed, and whether data-saver mode is on. Telling WiFi from mobile data. For as long as CeKiN runs; nothing is deleted automatically yet. You and CeKiN's operator. Other people see only the number of tests per connection type in an area, once it has reached the threshold.
This browser's random mark, kept as a cookie named cekin_klien. ↓ So your tests can be shown again in the same browser, and so the waiting rule between tests can work. The mark is not a name. In your browser for one year from when it was first made. On the server, for as long as its tests are stored. CeKiN's operator.
Only if you sign in with Google: your name, e-mail address, the address of your profile picture, and the identifier of your Google account. ↓ Recognising you when you sign in, and bringing together the tests and points from your devices. Until you delete your account. You and CeKiN's operator.
Sign-in marks: when you signed in, from which browser, a fingerprint of the IP address at that moment, and the list of browsers you have signed in from. ↓ Keeping you signed in, and showing the tests from all your devices in your history. A sign-in mark lasts 30 days or until you press Sign out. The list of browsers, until the account is deleted. You (the list of devices on the Account page) and CeKiN's operator.
The points you earn: from which test, and the day and time slot of that test. Working out your points and level. For as long as CeKiN runs; nothing is deleted automatically yet. You and CeKiN's operator.
For a comparison test: when you agreed to it, the version of the consent text, its language, your browser; then the result (download, upload, latency) and the name of the M-Lab server used. ↓ Proof that consent was asked every time, and so the result can be shown beside CeKiN's. For as long as CeKiN runs; nothing is deleted automatically yet. You and CeKiN's operator. What M-Lab itself publishes is explained below.
The internet package you record yourself: provider, package name, promised download and upload speed, price per month, how it is billed and the start date — and previous packages with their dates. Each package names its connection: its kind (fixed line or mobile), the provider's network number and name, and — for a fixed line only — a one-way fingerprint of the network the line is seen on. The network itself is not stored, and the fingerprint cannot be turned back into it. Only the download speed is required; the price may be left empty. This is your own statement; CeKiN does not check it. Recording the package you pay for and when each package was in force — one package per connection, such as a home line and a phone data plan together — so your tests can be read against the package of the connection used at the time. Until you delete it, delete your account, or erase your browser's data. You and CeKiN's operator. Never part of area figures, not in the monitoring copy on the operator's computer, and never leaves SETARA.
Your answer before testing, once per network: a connection you pay for yourself, a guest, or not sure — with the kind of connection (fixed line or mobile), the provider's network number and name, and the connection's identifier: for a fixed line a one-way fingerprint of its network, for mobile only the operator's network number. The answer and the identifier are also stored with every test you make there. The network itself is not stored. If you claim your older tests on a network as yours, those tests are marked with the time of the claim, and your answer to that offer (claimed or skipped) is stored too. If you answer guest, your answer about the kind of place (public, not public, or skipped) is stored with it. So the question is not asked twice for the same network, so you can change your answer, and so that a package is judged only by its owner's own tests on that package's connection — while every test still adds to its area's figures. Until you change it, delete your account, or erase your browser's data. When browser data is erased, its tests stay without a name and without their connection identifier. You and CeKiN's operator. Not in the monitoring copy on the operator's computer, and never shown to anyone else.
Place records: a public place you named yourself a guest at — one-way fingerprints of its connection (several, when people confirm the same place), the 500 m cell the test was made in, its desa, and its kind. No address, no WiFi name, no person's name. A test is linked to a place only when three things hold: it carries a location in that place's cell, its connection is one of the place's connections, and you answered guest at a public place. Tests without a location, mobile tests and tests with an unknown role are never linked. A network you answered “not public” is marked private: no shown place is ever made for it, and only CeKiN's operator can lift that mark. Place names: the name you picked from the OpenStreetMap suggestions or typed, with who gave it (account or browser mark) and the result of the automatic checks (phone number, web address, advertising words, resembling a person's name, length). A published name is shown to other people who test at that place; who gave it is never shown. A held name is seen only by you and CeKiN's operator. Every decision about a name — automatic or the operator's — is written in the place's history. Reports of wrong data: who reported (account or browser mark), their note, when it was checked and what changed; the corrections the checks made (tests moved, a place split) are shown on the place's page naming nobody. So that, later, the figures of a public place — a café, a mall, an airport — can be worked out from the tests of people who were really there, without ever linking a home or an office. For as long as CeKiN runs. A test's link to a place stays after browser data is erased, because the link points at nobody. For now only you (the places your tests count for) and CeKiN's operator; nothing is shown publicly yet. Not in the monitoring copy on the operator's computer. A published place name is shown to other people who test at that place. The page of a published place — name, desa, 500 m cell, medians and a score from enough tests and people, quality by time of day, and corrections — is seen by everyone; never its provider, never who tested.
Claims on a public place: who claims (account or browser mark), the public IP address and business domain they declared (if any), the DNS token, the result of the six automatic checks on that address, and the operator's decision. Requests to read a non-public network's figures: who asks, on what basis — a company e-mail domain (the address itself is forgotten once the code is right) or the file name of a letterhead statement (the file is deleted the moment the operator decides) — when, and the decision; the announcement of a new reader to the existing ones. So that a public place's owner or manager can be verified, and the people entitled to it at an office can read their network's aggregate figures — both decided by CeKiN's operator, never automatically. For as long as CeKiN runs. The e-mail address: only until the code is right. The letter's file: only until the operator decides. You and CeKiN's operator. Another claimant never sees your claim. A granted reader sees the network's aggregate figures (above 3 people and 5 tests), never who tested; other readers of the same network are told a new reader exists. People who test on a network with a verified reader are told on their result card.
The satisfaction rating you give after a test: worse than, as or better than you expected — or that you chose not to answer — with the test it is about and the day. So the question is never asked twice for the same test and at most once a day, to give the rating points (the same for any answer), and later for a picture of satisfaction per area. No advice uses it yet. Until you delete your account or erase your browser's data. You and CeKiN's operator. One person's rating is never shown publicly; combined figures may only appear once the area meets the same threshold as the map.
If a test is rejected because its report is impossible: the reason and the figures it claimed. The test result itself is not stored. Knowing how often that happens, and why. For as long as CeKiN runs; nothing is deleted automatically yet. CeKiN's operator.
When an account or a browser's data is deleted: a one-way fingerprint of the account's identifier or the browser's mark, which kind it was, and the date. No name, e-mail address or IP address. ↓ So that a deletion can be carried out again if an older backup copy is used to restore the site. For as long as CeKiN runs; nothing is deleted automatically yet. CeKiN's operator.

Your public IP address

Your public IP: 216.73.216.192

Every time you run a test, the CeKiN server records the public IP address your connection is using at that moment. The address is also shown on the test screen, so you know exactly what is recorded.

The address is kept for 12 months, then deleted automatically. The test result, its internet provider and its area stay, and so does the fingerprint that cannot be turned back into the address.

Only you and CeKiN's operator can see your address. An IP address is never shown to other users, never appears on the map, never enters the figures per area, and is never part of data that leaves SETARA.

An IP address is personal data under Indonesia's Law No. 27 of 2022 on Personal Data Protection. That is why it is kept only as long as needed and deleted when its retention period ends.

Finding the name of your internet provider

To know which internet provider a test used, the CeKiN server asks the internet's network registries — a public service called RDAP, the successor of WHOIS: whose network is this?

The question is about the network, not about you. For the address 114.5.1.77, for example, what is sent is 114.5.1.0 — the last number is removed, so your device cannot be recognised from the question. Local addresses are never asked about.

The question goes to the rdap.org service; if it does not answer, to Team Cymru's DNS service, then to the Asia-Pacific registry (APNIC). They receive that network address and the address of the CeKiN server — nothing about you.

What is stored from the answer: the name of the network's holder, its network number, its country, and when it was asked. The answer for one network is reused for 90 days.

A city cannot be learned this way: those records only hold the provider's head-office address. An area comes only from a location you share.

Location

Before the first test on a device, CeKiN asks whether it may read your location. You may always skip it: the test still runs and is still stored, it just stays off the map. Your choice is kept in that browser only and can be changed at any time on the Account page.

If you allow it, what is stored with your test is your position (latitude and longitude), its estimated accuracy, and the 500-metre square it falls in. If you skip, or the browser refuses, no location is stored; only the fact that the test has none, and why.

The exact point is visible only to you (on the Map page, under “My tests”, once you are signed in) and to CeKiN's operator. Other people never see a point: the Map shows areas only — a village at the most detailed — and only once that area has at least 10 tests from 3 different people.

For a point in Bali, the area names are looked up in a boundary file kept on the CeKiN server itself. No outside service is called, and your location is sent nowhere.

For a point outside Bali, the CeKiN server asks OpenStreetMap's Nominatim service. What is sent is the centre of the 500-metre square your test falls in — not the exact point — and one square is asked about only once.

Area boundaries and names: © OpenStreetMap contributors. openstreetmap.org/copyright

Cookies and what is kept in your browser

CeKiN uses only its own cookies, the ones the site needs in order to work. There are no advertising cookies and no third-party cookies.

  • cekin_klien — this browser's random mark. One year.
  • cekin_lang — the language you chose. One year.
  • cekin_sesi — the mark that you are signed in. 30 days, or until you press Sign out. Present only if you sign in.
  • cekin_masuk and cekin_kabar — two temporary cookies during sign-in with Google. They disappear by themselves within minutes.
  • Your choice about location (allow or skip) is kept in the browser's own storage, not on the server. So are the time the invitation to sign in last appeared and the number of times you closed it.

Accounts: signing in with Google

An account is optional. Every test works without signing in, and without an account CeKiN does not know your name.

If you choose to sign in with Google, Google gives CeKiN three things about you: your name, your e-mail address and your profile picture — together with the identifier of your Google account, so CeKiN recognises you when you sign in again. CeKiN does not receive your password, your contacts or anything else in your Google account, and does not ask for them.

The three are used only to keep your account: to recognise you when you sign in, to show your name and picture on the Account page, and to bring together the tests and points from your devices. They are not used for advertising and are not given to anyone else. Your profile picture is not copied to the CeKiN server; only its address is stored, and your browser loads it straight from Google.

When you sign in, the tests, comparison tests and points already stored for that browser — including the IP address and location recorded with them — become linked to your account, and so do the tests you run while signed in. Before signing in, all of that is linked only to the browser's random mark.

Because you sign in through Google, Google knows that you signed in to CeKiN and when. What Google does with that is governed by Google's own policies.

Comparison tests: what M-Lab publishes

A comparison test is run by M-Lab (Measurement Lab), an open internet measurement organisation — not by CeKiN. Your browser connects directly to M-Lab's servers.

M-Lab publishes the result of every test as open data: publicly, forever, and including the public IP address of your device. Once published, it cannot be withdrawn — not by you, and not by CeKiN.

That is why CeKiN asks for your consent before every comparison test, every time, and records that consent. A comparison test never earns points, a badge or any reward, so there is no reason to run one other than wanting to compare.

M-Lab's privacy policy · M-Lab's acceptable use policy

A result card you share

A result card for sharing carries: the score and its label, download and upload speed, response time, jitter, the test code, the date, the area down to the district, the server the test was measured to, and the name of your internet provider — the name you recorded yourself in your package, or if there is none, the name from the network registry, and the card says which. Since 27 October 2026 also the connection fingerprint: six median figures from your own tests on that connection (download, upload, response, stability, loss, consistency) and its six-sided shape.

The card never carries your IP address, your position, your browser's mark, your account name or your e-mail address.

Sharing a card is your own choice. A card can only be made for your own test, as a picture made in your browser; CeKiN keeps no copy and makes no public link for it.

What you have sent to other people cannot be withdrawn by CeKiN, and is not erased when you erase your browser's data or delete your account.

Other parties involved

To be clear, these are all the parties outside CeKiN that receive something when you use this site:

  • Network registries (rdap.org, Team Cymru, APNIC): the network address of your test — not your full address.
  • Nominatim / OpenStreetMap: the centre of a 500-metre square, only for located tests outside Bali.
  • Google: only if you choose to sign in with Google.
  • M-Lab: only if you agree to a comparison test.
  • The server provider: this site runs on a rented server, so the data is stored there.

There are no others. This site loads no advertising, no analytics tool and no script from any other party.

What is never shared

  • Your exact position.
  • Your IP address.
  • Your name, e-mail address and picture.
  • Your tests one by one. What leaves CeKiN is only combined figures per area and per provider.

CeKiN sells no data today. If SETARA ever provides data to others, it will use only combined figures per area and per provider — never an IP address or a position.

CeKiN does not record your phone number or what you open on the internet.

What the operator sees

CeKiN's operator can see everything listed in the table above, including IP addresses and exact positions. To monitor the site, test data and the points awarded are copied continuously to the operator's computer; that monitoring copy holds the tests and points without the names and e-mail addresses of accounts — only a browser's random mark or an account number says whose they are. Besides that there are backup copies, which hold the whole database — accounts included, with their names, e-mail addresses and picture addresses. See “Backup copies” below.

What you can do

If the account is deleted, the tests you ran are not deleted: they become anonymous again — no longer linked to your account — and are still used for the area figures. The IP address on those tests is still deleted when its retention period ends.

If you have no account

Even without an account you can see and download what is stored for the browser you are using, and erase it, from the Account page. Open the Account page

Erasing a browser's data means: its tests are detached from that browser; their IP address, address fingerprint, position, 500-metre square, and device and connection details are deleted at once; its provisional points, internet package records and satisfaction ratings are deleted. The result figures, internet provider and area names stay as anonymous tests. Tests that already belong to an account are not erased this way — that is done from the account.

The monitoring copy on the operator's computer is cleaned the same way at its next pull. For the backup copies, see below.

What M-Lab has already published cannot be deleted by CeKiN.

Backup copies

So that data is not lost if the server breaks, CeKiN makes backup copies. A backup copy holds the whole database: tests, IP addresses, positions, accounts (name, e-mail address, picture address), and everything else in the table above.

  • On the server: every night one copy of the whole database is made. Kept are the newest 7 daily copies, plus one copy per week for the 4 weeks before those — so the oldest copy is about 5 weeks old. The folder they are in can only be opened by the server's administrator.
  • On the operator's computer: the newest copy from the server is also pulled to the operator's computer, so the data survives losing the server. There the last 5 copies are kept, and none older than 30 days — except the newest one, which is always kept whatever its age, so that one copy always exists if the server is lost. Older copies are deleted while the operator's app is running; if that computer is not switched on for a long time, they are deleted as soon as the app is started again.
  • The operator's working database — which also holds the monitoring copy of the tests, with IP addresses and positions but without the names and e-mail addresses of accounts — is copied to the server once a day. The server keeps the last 7 copies: usually one week, longer if the operator's computer is rarely on.

Backup copies are never sent anywhere else, are not public, and are not part of any data that leaves SETARA.

When you delete your account or your browser's data, it is gone from the site's database at once. But backup copies made before that still hold it until they are deleted in turn: on the server at most about 5 weeks; on the operator's computer at most 30 days (or until the operator's app is started again, if that takes longer) — except in the newest copy there, from which you disappear as soon as a newer copy arrives; and in the copies of the operator's working database until the next 7 copies have replaced them.

If an older copy is ever used to restore the site, those deletions are carried out again before the site reopens. For that, CeKiN keeps a list of deletions: only a one-way fingerprint of the account's identifier or the browser's mark, which kind it was, and the date — no name, e-mail address or IP address.

Who runs CeKiN

CeKiN is a product of SETARA. SETARA is not a legal entity yet: for now CeKiN is run personally by Johan Giri Wijaya, who is responsible for the data on this site.

To ask a question, to request something about your data, or to complain, contact: info@cekin.tech

You may ask about your own data: what is stored, a copy of it, or that it be deleted. If your question is about one test, give its test code (for example CKN-20261019-SZ24W) — that helps a lot. There is no promised time for an answer yet.

If you want to complain

Tell the operator first by e-mail to info@cekin.tech, quoting your test code if it concerns a test. You also have rights as a data subject under Indonesia's Law No. 27 of 2022 on Personal Data Protection.

CeKiN is still a preview. This page is changed every time what is stored, or who can see it, changes. Last changed 27 October 2026: a result card you can share now also carries the connection fingerprint — six median figures from your own tests on that connection and its six-sided shape; still no IP address, location point, browser mark or name. Before that, 26 October 2026: the owner of a public place can file a claim (a declared IP address is checked six ways, the result a level of support), and the IT, a manager or the owner of a non-public network can ask to read its aggregate figures with a company e-mail or a letterhead statement; both are decided by CeKiN's operator. On the same day: a named public place has its own page with medians and a score (only after enough tests and people in 90 days), quality by time of day, no provider and no one's identity; someone who tested there can report wrong data, and corrections are shown. On the same day: you can give a public place a name and use it yourself at once; it is published to others only after it passes the automatic checks and enough different people have tested there — who gave it is not shown. On the same day: after you answer guest, CeKiN asks once whether it is a public place or not; for a public place a place record is made (connection fingerprint and 500 m cell, no address) and located tests there are linked to it; a network that is not public is marked private. Before that, 25 October 2026: you can claim your older tests on a network you own, once, as your own; they are marked as claimed afterwards. On the same day: a package is now judged only by the tests you made yourself as the owner of its connection; the owner of a fixed line sees how many tests other people made on it and their median download, apart from the judgement. On the same day: before a test, CeKiN asks once per network whether it is a connection you pay for yourself or you are a guest there; the answer is remembered for that network and stored with every test. On the same day: a package record now names its connection (fixed line or mobile, and its provider); for a fixed line a one-way fingerprint of its network is stored, not the network itself. Several packages can be in force together, one per connection. Before that, 23 October 2026: the satisfaction rating after a test is now stored; the shareable result card is described; the invitation to sign in keeps its record only in your browser. Terms of use

Preview: the speed test works; the other features are still being built. · Privacy · Terms