Last updated: 2019-11-05
With your privacy in mind, we do not collect or store any data beyond what is absolutely necessary.
We do not collect or store any of the time series data sent via your requests to our service. We do not claim ownership or rights to your time series data. By using our service, you assure us that the time series data you send with your requests does not violate the rights of third parties. The only time series meta data that we store is the length of the time series (the number of data points) used in successful requests. The function of this information is to obtain the total number of data points that were used for computations with our API across all users and endpoints.
For maximum transparency, here is a list with the account related data we store and its function:
|Name||Basic contact information.|
|Company||Required to ensure that the user is part of a company.|
|Account access; sending emails necessary to create, change, and use an account; sending emails with invoices and payment reminders|
|Invoked endpoints||Allows the user to monitor the API usage|
|Actual and billed API usage time||Required to calculate charges|
|User-Agent||Allows the user to detect suspicious account activity|
By signing up for our service, you agree that your email address may be used as a means of establishing email verification, sending invoices and payment reminders. We do not share your email address with third parties.
If you have a Time Door account and are signed in, we use the local storage of your browser to persist your signed in state and your theme. The data is stored locally in your browser's chache and remains there until you delete your browser's chache or sign out. The data stored in the local storage cannot be accessed by third parties. It will not be passed on to third parties or used for advertising purposes.
|Host||This is just "timedoor.io"|
|Path||For example, "/docs"|
|Referrer||For example, "github.com"|
|Viewport dimensions||Width and height of the viewport|
We also collect some events and interactions, for example the success status of requests made with the sandbox. This information is used to identify errors in our system.