Cookie Policy
Cookies that sign you in and keep the platform safe, plus the Meta Pixel, which sets advertising cookies. Google Analytics measures how Rydz is used without setting any cookies.
01About This Policy
This Cookie Policy explains how Garagify Trading Pty Ltd (ACN 700 925 766), trading as Rydz (“Rydz”, “we”, “us” or “our”), uses cookies and similar technologies on the website located at rydz.io and any related applications, features and services we make available (together, the “Service”).
This Policy is referred to in clause 11 of our Privacy Policy and forms part of that Policy. It should be read together with our Privacy Policy and our Terms and Conditions (“Terms”). Terms defined in the Terms or the Privacy Policy have the same meaning in this Policy unless stated otherwise.
If you do not agree to our use of cookies as described in this Policy, you should adjust your browser settings as described in clause 6, or stop using the Service.
02What Cookies Are
A cookie is a small text file that a website asks your browser to store on your device. Cookies let a site recognise your browser between requests — for example, so that you stay signed in as you move from page to page.
Cookies are described in two useful ways:
- First-party or third-party. A first-party cookie is set by the site you are visiting. A third-party cookie is set by another organisation whose service the site uses.
- Session or persistent. A session cookie is deleted when you close your browser. A persistent cookie remains on your device until it expires or you delete it.
Websites also use technologies that work like cookies without being cookies, including browser storage. Clause 5 describes how we use those.
03Cookies We Use
We use two kinds of cookies: strictly necessary cookies, which operate the Service, keep you signed in and protect the Service and your Account against abuse, and advertising cookies set by the Meta Pixel, which clause 4 describes. The table below describes each strictly necessary cookie, why it is used, and how long it lasts.
| Cookie | Purpose | Type | Expires |
|---|---|---|---|
| Rydz session cookie | Keeps you signed in after you authenticate, and tells our systems which Account a request belongs to. It cannot be read or modified by scripts running in your browser. If you sign in without choosing to stay signed in, a second cookie records that choice. | First-party. Strictly necessary. | Up to 7 days, or until you sign out. If you did not choose to stay signed in, when you close your browser. |
| Signed-in marker | Lets the website send you to the right page before it loads, such as your garage or the sign-in screen. It records only that you are signed in, whether your email address is confirmed and, until it is, that address. It does not sign you in. | First-party. Strictly necessary. | Up to 7 days, or until you sign out. |
| Sign-in transaction cookies | Set only while you are signing in. They protect the sign-in exchange against interference and cross-site request forgery, and hold your place while you enter the sign-in code we email you. | First-party. Strictly necessary. | Up to 15 minutes. Deleted at the end of the sign-in process. |
| Remembered browser cookie | Set after you enter a correct sign-in code, so that we do not ask for a code again on that browser. It holds a random identifier tied to your Account and cannot be read by scripts running in your browser. | First-party. Strictly necessary. | 30 days, renewed each time you sign in on that browser. It stops working if you change or reset your password. |
| Google sign-in cookies | Set by Google on its own sign-in pages where you choose to sign in with a Google account, in order to authenticate you and protect the sign-in process. We do not control these cookies. | Third-party. Strictly necessary. | As determined by Google. See Google’s own privacy and cookie information. |
Strictly necessary cookies are used to provide a service you have asked for. Because the Service cannot sign you in or keep you signed in without them, they are not subject to a consent choice, and we do not present a consent banner for them.
04Analytics and Advertising
Google Analytics
We measure how the Service is used with Google Analytics, provided by Google. It is configured so that it does not set or read any cookie or other storage on your device. It counts pages viewed and actions taken in the Service, such as adding a car or joining a club, without your name, email address or other contact details. Pages are reported by their type, such as “a car page”, rather than their full address, so usernames and other identifiers in the address are not sent. Google still receives the technical information that comes with any request from your browser, such as your IP address and browser type.
Meta Pixel
We use the Meta Pixel, provided by Meta Platforms, Inc. (“Meta”), the company behind Facebook and Instagram. It helps us measure how well our advertising on Facebook and Instagram works, and reach people on those platforms who may be interested in Rydz.
The pixel loads when you open the Service. It sends Meta the address of each page you view, actions such as button clicks, and technical information such as your IP address and browser type. If you have a Facebook or Instagram account, Meta may link this information to that account. Meta uses it under its own privacy policy, including to provide and improve its advertising services. The pixel sets or reads these cookies:
| Cookie | Purpose | Type | Expires |
|---|---|---|---|
| _fbp | Identifies your browser to Meta, so that Meta can tell your visits and actions on the Service apart and measure our advertising. | First-party, set by the Meta Pixel. Advertising. | 90 days, renewed each time you visit. |
| _fbc | Set only when you arrive from a link on Facebook or Instagram, usually an ad, to record which link you followed. | First-party, set by the Meta Pixel. Advertising. | 90 days. |
| Meta cookies | Where your browser allows it, Meta may also read or set its own cookies, for example if you are signed in to Facebook or Instagram in the same browser. We do not control these cookies. | Third-party. Advertising. | As determined by Meta. See Meta’s own Cookies Policy. |
We do not currently ask for your consent before the Meta Pixel loads. Clause 6 explains how to block or delete these cookies and limit how Meta uses this information.
Apart from Meta, we do not allow advertisers or advertising networks to set cookies through the Service. If we add analytics or advertising cookies beyond those described here, we will update this Policy before they are used.
05Similar Technologies
The Service uses your browser’s local storage and session storage to remember things on your device, such as a car you start building before you create an Account, or your place in a list when you come back to it. Information stored this way stays on your device and is not a cookie, but we describe it here because it serves a similar purpose.
The Meta Pixel described in clause 4 is a tracking pixel: a small piece of code that reports your activity on the Service to Meta. Apart from the Meta Pixel, we do not use device fingerprinting, tracking pixels or similar techniques to identify or track you.
06Managing Cookies
Most browsers let you see the cookies stored on your device, delete them, block cookies from particular sites, or block cookies altogether. These controls are found in your browser’s settings, and your browser’s own help pages explain how to use them.
You should be aware that blocking or deleting the cookies described in clause 3 will prevent you from signing in to the Service, or will sign you out unexpectedly, because those cookies are what keep you signed in.
You can limit analytics and advertising in these ways:
- Your browser.Deleting the _fbp and _fbc cookies resets the identifier Meta receives, and blocking third-party cookies stops Meta’s own cookies being read. Many browsers and browser extensions can also stop the Meta Pixel and Google Analytics from loading at all.
- Google Analytics. Google offers a browser add-on that stops Google Analytics receiving information about your visits, available at tools.google.com/dlpage/gaoptout.
- Meta.If you have a Facebook or Instagram account, Meta’s Accounts Centre lets you choose whether Meta uses activity from other websites to show you ads (under Ad preferences), and see and disconnect that activity (under Your activity off Meta technologies).
07Cookies and Your Privacy Rights
Where information collected through a cookie is personal information, we handle it in accordance with our Privacy Policy and the Privacy Act 1988 (Cth), including the Australian Privacy Principles. Clause 14 of our Privacy Policy describes the rights and choices available to you, and clause 15 sets out additional information for users located outside Australia.
If you are located in the European Economic Area or the United Kingdom, the cookies described in clause 3 are used because they are strictly necessary to provide a service you have requested. The Meta Pixel cookies described in clause 4 are not strictly necessary. We do not currently ask for consent before they are set. You can block or delete them as described in clause 6, and if we introduce a consent choice, we will update this Policy.
08Changes to This Policy
We may amend this Policy at any time. We will take reasonable steps to notify you of material changes, including by posting a notice on the Service. Changes take effect from the date stated in the notice, or otherwise from the date of posting. Where a change adds a cookie, we will update this Policy before the cookie is used.
09Contact Us
Garagify Trading Pty Ltd (ACN 700 925 766), trading as Rydz
PO Box 308, Daw Park SA 5041, Australia
Email: contact@rydz.io
If you have a complaint about how we have handled your personal information, clause 19 of our Privacy Policy explains how to make it and how to escalate it to the Office of the Australian Information Commissioner.