Cookie policy
Cookies in Timetastic
If you signup, login and use Timetastic then these are the cookies you'll see in use:
Name | Provider | Purpose | Duration | Type |
.AspNetCore. Antiforgery. xxxxx | Timetastic | This is a standard security cookie we use. It's an Antiforgery token that stops people being able to make requests "across origin" forging a request to Timetastic that isn't actually from Timetastic. | Browser close | Functional |
.AspNetCore. Identity. Application | Timetastic | This is the login cookie. It's how we know which user is logged in. | 1 year | Login |
__cflb | Cloudflare | Cloudflare load balancing cookie. | max 24 hours | Functional |
__stripe_mid | Stripe | Stripe fraud prevention cookie. It helps Stripe assess the risk associated with an attempted transaction. | 1 year | Fraud prevention |
__stripe_sid | Stripe | As above, but shorter duration, so they can identify fraud on a session basis. | 30 minutes | Fraud prevention |
_cioid | Customer.io | A cookie that identifies a user to Customer.io. It gives us the "user did x on y" so we can segment for transactional and marketing emails. | 1 year | Functional |
Timetastic.2fa .Device | Timetastic | Notifies us that this user has signed in using 2FA, so we don't ask them again until the cookie expires. | 30 days | Functional |
MUID | Microsoft | Microsoft/Bing Id cookie. MUID = Microsoft User Identity. It's used to track conversions from Microsoft advertising. | 1 year | Statistics |
_uetsid | Microsoft | Microsoft conversion tracking cookie. | 1 day | Statistics |
_uetvid | Microsoft | Microsoft conversion tracking cookie. | 16 days | Statistics |
ai_session | Microsoft | Microsoft Application Insights cookie - to keep tabs on whether things worked or not and load speed. We use this to spot issues, slow requests, identify and fix bugs. | 30 mins | Statistics |
ai_user | Microsoft | Same purpose as ai_session above - the App insights snippet installs both cookies and uses them to provide this service. | 1 year | Statistics |
Additional cookies on our billing page
You'll find the following additional cookies on our billing page:
These cookies are slightly different in that they are set by a 3rd party, but they are essential for security and fraud prevention.
Name | Provider | Purpose | Duration | Type |
Stripe.js | Stripe | Security and fraud prevention. | No expiry | Functional |
Re-captcha | Fraud scoring. It's recommended we use this by Stripe to help prevent fraudulent activity. | 2 minutes | Functional |
Cookies on our help centre
We use Zendesk to provide support and host the content on our help centre:
Name | Provider | Purpose | Duration | Type |
__cfruid | Zendesk/ Cloudflare | This is their Cloudflare load balancing cookie | Browser close | Functional |
__cf_bm | Zendesk/ Cloudflare | Cloudflare Bot management cookie to detect bots | 30 mins | Functional |
_help_center _session | Zendesk | Stores unique session key for Help Center product. | Browser close | Functional |
__cfruid | Zendesk/ Cloudflare | Cloudflare cookie used in cases were multiple users are hidden behind the same client IP address. Each user will have a unique cookie to help prevent a case of rate limiting all users if one particular user hits the rate limit threshold. | Browser close | Functional |
_zendesk_ session | Zendesk | Stores account ID, route for internal service calls and the cross-site request forgery token. | 8 Hours | Functional |
_zendesk_ shared_session | Zendesk | Stores account ID, route for internal service calls and the cross-site request forgery token. | 8 Hours | Functional |
Questions about cookies?
If you have any questions about the cookies you find on our site then please contact our support team, we're always happy to help.