Privacy
Slope counts its installs, and that is all it reports. Your models and results stay on your computer.
The install count
The first time Slope runs on a computer it sends one short message to
stats.syncster.dev, a service we run, and one more the first time it runs
after its version has changed. That is how we know how many copies are in use and which
versions they are. It is always sent; there is no setting for it, because it holds
nothing about you. The message says:
| What | For example | Why |
|---|---|---|
| A random installation id | 3f0c8a52-91d4-4c1e-8b7a-5d2e6f104b99 | To count each copy once |
| Slope's version | 0.1.1 | To tell an install from an update, and see which versions are in use |
| The operating system | macos | To know which systems to build for |
| The processor's architecture | arm64 | The same |
| For an update, the version before | 0.1.0 | To see updates arriving |
The id is made of random digits on Slope's first run. Nothing about you or your computer
goes into it, so it isn't tied to a person: it only tells one copy of Slope from another.
It is kept, with the last version reported, in the file stats.json in
Slope's data folder (~/Library/Application Support/Slope); delete the file
and the next start counts as a new install.
The service stores those values and the time the message arrived. It does not store the network address the message came from with them.
What is never sent
- Your models, their soils, loads and results, or your reports
- File names, folder names or paths
- Your name, email address, user name or computer name
- What you do in Slope: no usage tracking, no crash reports
Slope has no accounts, no advertising, and nothing is sold or shared.
The download count
Pressing a download button on this website tells the same service that Slope was downloaded: the product, the version and the system it is for (macOS or Windows). Nothing about you is in it, and there are no cookies.
Other connections
There are none. Slope doesn't look for updates by itself: new versions are on this website.
Questions
Write to us through syncster.dev.