What Cookies Do
Small files that help the site work, remember preferences, and measure usage – see § 2.
Last updated 18 October 2026
The plain-English summary. The full legal text below is the binding document.
Small files that help the site work, remember preferences, and measure usage – see § 2.
Essential, preference, and analytics cookies – full inventory in § 4.
No third-party cookies; our analytics is first-party and off until you agree – see § 9.
Adjust your preferences anytime via Cookie Settings – see § 6.
Automize RPA SaaS Platform
Capitol Hill Consulting (Pty) Ltd
This Cookie Policy explains how Capitol Hill Consulting (Pty) Ltd ("Capitol Hill", "Automize", "we", "us", or "our") uses cookies and similar technologies on:
This Cookie Policy should be read together with our Privacy Policy and Terms of Service.
By using our Sites or Platform, you consent to the use of cookies as described in this Cookie Policy. You can manage your cookie preferences as explained in Section 6 below.
Cookies are small text files that are placed on your computer, smartphone, or other device when you visit a website. They are widely used to make websites work more efficiently and provide information to website owners.
When you visit our Sites or Platform:
Session Cookies:
Persistent Cookies:
First-Party Cookies:
Third-Party Cookies:
In addition to cookies, we use other similar technologies:
What it is: Storage in your browser. Unlike a cookie, it is not sent to our servers with each request, and it stays until you clear it.
What we keep there: only settings and state for the interface. Nothing in it is used to track you.
| Key | Purpose |
|---|---|
cookie_consent |
Your cookie choices (display preferences, analytics), so the banner does not ask again |
display |
Interface preferences: panels open or closed, view modes. Only kept if Display Preferences is on in Cookie Settings |
theme |
Light or dark theme |
sort, shared |
How you sorted a list, and your recent sharing choices. Only kept if Display Preferences is on in Cookie Settings |
views:…, views-last:… |
List views you saved by name, and the filters you last used on each list. The last filters are only kept if Display Preferences is on in Cookie Settings |
Sidebar and canvas keys (e.g. process-sidebar-expanded, wiki-sidebar-tab, minimap-collapsed, canvas-density, palette-recent, pmShapes) |
Layout of the process map and wiki editors, and your recently used steps |
| Form drafts | Values you typed into a form that is not sent yet, so they survive a page reload |
lastActivity, lastKeepAlive |
When you last used the platform, so the idle timeout works across every open tab. Strictly necessary: it is part of a security control and is kept whatever your cookie choices |
automize:toastedNotifications, dash-default-prompt-dismissed:* |
Which notifications and tips you have already seen |
What they are: Tiny, transparent image files embedded in web pages or emails.
How we use them:
What it is: Browser storage that is deleted when you close the tab.
How we use it: the process map notes, per step, when an action cannot be undone (pm-no-undo-*), so it can warn you before you repeat it.
These cookies are needed for the Sites and Platform to work and to keep them secure. You cannot switch them off, because sign-in, security checks and the services you ask for depend on them. All are set by Automize (first-party), sent only over secure connections, and none is used for advertising or tracking.
| Cookie Name | Purpose | Duration | Type |
|---|---|---|---|
auth_token |
Keeps you signed in. Cannot be read by page scripts (HttpOnly) | 30 days | First-party |
csrf_token |
Protects your forms and actions from being sent by another website (cross-site request forgery) | 30 days | First-party |
email |
Remembers the email address you are signing in or resetting a password with, between the steps | 10 minutes | First-party |
payload |
Holds the steps of a sign-in or sign-up that is in progress | 10 minutes | First-party |
sso_state |
Checks that a single sign-on reply belongs to the sign-in you started | 10 minutes | First-party |
connector_oauth_state |
Checks that the reply from an app you are connecting belongs to the connection you started | 10 minutes | First-party |
signup_plan |
The plan you picked on the pricing page, while you sign up | 1 hour | First-party |
signup_for |
Which product page you came from, so sign-up can suggest what you want to automate | 1 hour | First-party |
auto-discover |
Remembers which Automize site address you use, so the bot can find it | 30 days | First-party |
dt_trial |
Counts free uses of the public document tools, so the free allowance is shared fairly. Holds a random value, not who you are | 12 months | First-party |
no_count |
Only set when you ask us not to count your visits (Privacy Choices). Remembers that choice | 13 months | First-party |
The consent choice itself is kept in local storage (cookie_consent, Section 3.1), not in a cookie.
Legal Basis: These cookies are necessary for the performance of our contract with you and to provide the Services you've requested.
These remember choices you make. The Sites and Platform still work without them; you just have to choose again.
| Cookie Name | Purpose | Duration | Type |
|---|---|---|---|
language |
The language you chose | 12 months | First-party |
ccy |
The currency you chose on the pricing page | 12 months | First-party |
Interface preferences are kept in local storage, not cookies (Section 3.1). The display preferences are only kept if Display Preferences is on in Cookie Settings.
Legal Basis: Our legitimate interest in remembering the choices you made.
Can be disabled: Yes. Delete them in your browser (Section 6.4), or switch Display Preferences off in Cookie Settings.
Our analytics is Automize's own and first-party: no Google Analytics and no other analytics provider. It works at two levels.
Counting visits, for everyone, with no cookie. To see which pages help people and where they get stuck, we group each visit by a code made from your address and browser and a secret that changes every day. The secret is deleted when the day ends (our database backups keep a copy for 7 days, then expire), after which the code cannot be turned back into your address or linked to another day's visit, by us or anyone. We keep only the code, the page, the site that sent you, any campaign tag, and the country your address is in; never the address itself. We also note which important links are clicked, where on a page clicks land, how far the page is scrolled and how long it is open. Each page also sends one short “the page was drawn” signal back, so we can tell people from bots. Nothing is stored on your device for any of this, and nothing you type is recorded. It is our legitimate interest in running and improving the site (see our Privacy Policy). You can object: choose “Don’t count my visits” on the Privacy Choices page, or send Global Privacy Control, and none of it happens.
Analytics cookies, only if you agree. With your consent we also set visitor_id, so we can see how your visits connect over several days (for example that you read the pricing page on Monday and signed up on Thursday), and we keep your IP address and browser details for 30 days. Your choice is carried in analytics_consent. Without your consent neither is set.
| Cookie Name | Provider | Purpose | Duration | Type |
|---|---|---|---|---|
analytics_consent |
Automize | Remembers whether you agreed to analytics (1 = yes, 0 = no) | 180 days | First-party |
visitor_id |
Automize | A random value that links your visits over several days. Only set with your consent, and removed on your next visit if you withdraw it. Cannot be read by page scripts (HttpOnly) | 13 months | First-party |
What we track:
What we DON'T track:
Legal Basis: Counting visits: our legitimate interest, which you can object to. Analytics cookies: your consent.
Can be disabled: Yes - See Section 6 for instructions.
Two of the essential cookies in Section 4.1 exist for security: auth_token proves each request comes from your signed-in session, and csrf_token stops another website sending actions in your name. The short-lived sso_state and connector_oauth_state cookies protect sign-in and app connections in the same way.
Legal Basis: Our legitimate interest in protecting our Services and users from security threats.
Can be disabled: No - These are essential for security.
To respect your privacy, we want to be clear about what we do NOT do:
❌ We DO NOT use:
❌ We DO NOT:
Global Privacy Control: We honour Global Privacy Control (GPC). A GPC signal turns analytics off and hides the cookie banner. See Section 11.
When you first visit our Sites, you'll see a cookie consent banner that allows you to:
Your choice is stored in the cookie_consent cookie for 12 months.
You can change your cookie preferences at any time by:
Option 1: Cookie Settings Link
Option 2: Browser Settings
Option 3: Account Settings (for logged-in users)
Cookie Settings:
Analytics is off until you agree. To turn it off again, open Cookie Settings and switch analytics off. We then set analytics_consent to 0 and remove visitor_id.
Don’t count my visits:
On the Privacy Choices page. We set no_count and stop grouping your visits or noting what you click; your page views are only added to the total.
Global Privacy Control: If your browser sends a GPC signal, analytics stays off and the banner is not shown. Accept All cannot override it.
Most browsers allow you to:
How to manage cookies in popular browsers:
Google Chrome: Settings → Privacy and security → Cookies and other site data https://support.google.com/chrome/answer/95647
Mozilla Firefox: Settings → Privacy & Security → Cookies and Site Data https://support.mozilla.org/kb/enhanced-tracking-protection-firefox-desktop
Microsoft Edge: Settings → Cookies and site permissions → Manage and delete cookies and site data https://support.microsoft.com/microsoft-edge/delete-cookies-in-microsoft-edge
Safari: Preferences → Privacy → Manage Website Data https://support.apple.com/guide/safari/manage-cookies-sfri11471/mac
Mobile Browsers: Check your mobile browser's settings or help documentation.
If you disable Essential Cookies:
auth_token, csrf_token and email cookies are required for authentication)If you disable Functional Cookies or clear Local Storage:
display local storage variable) won't be remembered between sessionsIf you disable Analytics Cookies:
Most of our cookies hold no personal data. These do:
auth_token - a signed token that links to your user accountemail - your email address, for up to 10 minutes while you sign in or reset a passwordpayload - a signed token for a sign-in or sign-up in progress, for up to 10 minutesAll three can only be read by our server (HttpOnly), are sent only over secure connections, and are not readable by other websites.
If cookies contain your personal data, you have rights under GDPR and POPIA:
To exercise these rights, contact: privacy@automize.co.za
Cookies are retained as follows:
auth_tokenLocal Storage:
cookie_consent and display): kept until you clear them or your browser dataData collected via cookies:
Cookies we set are stored on your device (in your location). However, data collected via cookies may be transmitted to:
When cookie data is transferred internationally:
If you are in the UK or EU, you have the right to:
We do not use Google Analytics. Our analytics is first-party: the data stays on our own servers and is never sold. It is off until you agree (see Section 4.3).
We do not use cookies from:
Fonts, icons and scripts: our pages load fonts from Google Fonts, icons from Font Awesome, and some scripts from cdnjs (run by Cloudflare). They do not set cookies for us, but when your browser fetches these files, those companies receive your IP address and browser details. See the Privacy Policy.
If we add third-party cookies in the future, we will update this Cookie Policy and notify you through the cookie consent banner.
Currently, Automize is a web-based platform accessed through browsers. We do not have native mobile apps.
If we develop mobile apps in the future:
"Do Not Track" (DNT) is a browser setting that signals to websites that you don't want to be tracked across websites for advertising purposes.
We honour Global Privacy Control (GPC): a GPC signal turns analytics off and hides the cookie banner. The older Do Not Track signal has no agreed standard, so we rely on GPC instead. In any case:
You can:
Security measures:
Potential risks:
How we mitigate risks:
To protect your cookies:
Our Services are not intended for children under 18 years of age. We do not knowingly collect information from children through cookies or any other means.
If you believe we have inadvertently collected information from a child through cookies:
We may update this Cookie Policy from time to time to reflect:
Material changes:
Minor changes:
Continued use of the Sites or Services after changes constitutes acceptance of the updated Cookie Policy. If you don't agree:
If you have questions about this Cookie Policy or our use of cookies:
Email: privacy@automize.co.za
Subject line: "Cookie Policy Inquiry"
Mail:
Capitol Hill Consulting (Pty) Ltd
Attn: Privacy Officer
4 Muller Street
Bethlehem, 9701
South Africa
To exercise your rights regarding cookie data:
Email: privacy@automize.co.za
Subject line: "Data Subject Request - Cookies"
Online form: https://automize.co.za/privacy-request
We will respond within 30 days.
If you're unhappy with how we use cookies:
Contact us first: privacy@automize.co.za
Supervisory authorities:
United Kingdom (GDPR):
Information Commissioner's Office (ICO)
Website: https://ico.org.uk
Phone: 0303 123 1113
Email: casework@ico.org.uk
South Africa (POPIA):
Information Regulator
Website: https://www.justice.gov.za/inforeg/
Email: inforeg@justice.gov.za
Phone: +27 10 023 5200
United Arab Emirates: [Contact relevant emirate authority based on your location]
For your reference, we maintain a record of your cookie consent choices:
What we record:
Why we record this:
How long we keep it:
Your rights:
| Cookie | Category | Duration | Can Disable? | Provider |
|---|---|---|---|---|
| auth_token | Essential | 30 days | ❌ No | Automize |
| csrf_token | Essential | 30 days | ❌ No | Automize |
| Essential | 10 minutes | ❌ No | Automize | |
| payload | Essential | 10 minutes | ❌ No | Automize |
| sso_state | Essential | 10 minutes | ❌ No | Automize |
| connector_oauth_state | Essential | 10 minutes | ❌ No | Automize |
| signup_plan | Essential | 1 hour | ❌ No | Automize |
| signup_for | Essential | 1 hour | ❌ No | Automize |
| auto-discover | Essential | 30 days | ❌ No | Automize |
| dt_trial | Essential | 12 months | ❌ No | Automize |
| language | Functional | 12 months | ✅ Yes | Automize |
| ccy | Functional | 12 months | ✅ Yes | Automize |
| no_count | Essential | 13 months | ❌ No (only set when you ask) | Automize |
| analytics_consent | Analytics | 180 days | ✅ Yes | Automize |
| visitor_id | Analytics | 13 months | ✅ Yes | Automize |
✅ What we use cookies for:
❌ What we DON'T use cookies for:
🔒 Your control:
Questions? privacy@automize.co.za
© 2026 Capitol Hill Consulting (Pty) Ltd. All rights reserved.
Document Version: 1.4
Effective Date: 18 October 2026
Last Updated: 18 October 2026