Get marketing insights first
Subscribe for actionable strategies, growth tips and useful industry insights, delivered straight to your inbox.
Website transparency
Cookie Policy
This policy explains how DesignEpic uses cookies and similar browser technologies on our WordPress website and booking experience.
The short version
Our core website uses essential technologies for security, login and bookings. Preference technologies remember choices such as cookie consent. We do not describe analytics or advertising cookies as active unless those services are deliberately enabled and disclosed.
01
Scope of this policy
This Cookie Policy applies when you visit the DesignEpic website, use our Amelia booking page or access any customer or employee panel we make available. It should be read with our Privacy Policy , which explains how we handle personal information more broadly.
The register below reflects our standard WordPress configuration using Amelia, Blocksy and GreenLight or Greenshift components. Cookies and browser storage may change when plugins are updated, optional features are enabled or third-party content is added. We review the register periodically and update this page when material changes occur.
02
What cookies and similar technologies are
A cookie is a small text file stored by your browser when you visit a website. Session cookies usually expire when you close the browser. Persistent cookies remain until their expiry date or until you delete them.
We may also use browser storage, pixels, tags and server logs. Local storage can remain after a browser session, while session storage is normally removed when the relevant tab or browser session ends. These technologies can support the same kinds of functions as cookies, so this policy addresses them together.
First-party and third-party:
first-party cookies are set for our website domain. Third-party cookies are set or accessed by another provider, for example when an embedded service, analytics tool or payment gateway is enabled.
03
Cookie categories
Always active
Strictly necessary
Required for requested functions such as security, login, bookings, session continuity and saving a consent choice.
Your choice
Preferences
Remember settings such as language, interface choices or commenter details. Some are used only after an action or opt-in.
Consent first
Analytics and marketing
Measure audiences or support targeted promotion. These are not part of the core stack declared in this policy and must not be activated before required consent.
Strictly necessary technologies cannot normally be disabled through a consent banner because the requested service may not work without them. You can still block them in your browser, but login, booking or security functions may fail.
04
Current cookie and storage register
Names containing
[hash]
,
{HASH}
or
{UID}
include a site-specific value or user identifier.
| Name | Provider | Purpose | Category | Typical duration |
|---|---|---|---|---|
wordpress_test_cookie
|
WordPress | Checks whether the browser accepts cookies on the login page. | Necessary | Session |
wordpress_[hash]
wordpress_sec_[hash]
|
WordPress | Authenticates registered users in secure administration areas. | Necessary | Usually up to 2 days; up to 14 days with “Remember Me” |
wordpress_logged_in_[hash]
|
WordPress | Recognises a signed-in user across the website. | Necessary | Usually up to 2 days; up to 14 days with “Remember Me” |
wp-settings-{UID}
wp-settings-time-{UID}
|
WordPress | Remembers interface preferences for a registered user. | Preference | Up to 1 year |
wp_lang
|
WordPress | Remembers the selected language on the login screen. | Preference | Session |
comment_author_{HASH}
comment_author_email_{HASH}
comment_author_url_{HASH}
|
WordPress | Optionally remembers commenter details when comments are enabled and the visitor opts in. | Conditional | Up to 1 year |
ameliaToken
ameliaUserEmail
|
Amelia | Authenticates an Amelia customer or employee panel session when panel access is enabled. | Necessary | Until the configured Amelia login token expires or the user logs out |
ameliaCacheData
Session storage, not a cookie |
Amelia | Temporarily restores booking details when a configured payment flow redirects away from and back to the website. | Conditional | Session; removed after restoration |
blocksy_cookies_consent_accepted
|
Blocksy | Records whether the visitor accepted or declined the Blocksy cookie notice. | Necessary | Up to 12 months under our configured consent period |
Some cookies appear only to administrators, registered users, commenters or people using an enabled Amelia panel or payment integration. A normal visitor may receive only the Blocksy consent record and technologies needed for requested website functions.
05
How WordPress uses cookies
WordPress uses cookies primarily to authenticate registered users, secure administration sessions and remember user-interface preferences. It may also set a temporary cookie on its login page to confirm that cookies are supported.
If commenting is enabled, WordPress can offer visitors an opt-in choice to remember their name, email address and website for future comments. DesignEpic may disable comments or the commenter-cookie option where it is not needed.
More information is available in the official WordPress cookie documentation .
06
How Amelia supports bookings
Amelia stores booking information in our WordPress database. Its booking interface may use session storage to preserve a booking during certain payment redirects. If customer or employee panel access is enabled, Amelia may use authentication cookies or browser storage to keep an authorised user signed in.
- The ordinary booking form does not require advertising cookies.
- Payment gateways, video-meeting services, calendar integrations or other optional Amelia integrations may use their own cookies and privacy terms.
- Amelia panel access tokens should be treated as essential authentication technologies.
- Closing the browser, signing out or clearing site data may interrupt an unfinished booking or end panel access.
Information entered into a booking form is handled as described in our Privacy Policy .
07
Blocksy and GreenLight
Blocksy
Blocksy’s Cookies Consent extension stores the consent-choice cookie listed above. If analytics is configured through Blocksy’s own integration, Blocksy can delay that analytics script until acceptance. Its notice does not automatically control every cookie set by unrelated third-party plugins or embeds.
GreenLight or Greenshift
Core design blocks do not set visitor cookies by default. Optional interactions can be configured to save preferences in cookies or browser storage, such as a dark-mode or dismissed-popup choice. We will add any such configured storage item to this register before enabling it.
Consent period:
this policy assumes the Blocksy Cookies Consent period is set to “One year”. If the site setting is changed, the duration in this register must be updated to match.
08
Third-party services and embedded content
Optional services can create additional cookies or similar technologies. Examples include analytics, payment gateways, embedded video, maps, spam protection, live chat, calendar connections and video-meeting platforms.
We will take reasonable steps to identify these technologies, understand their purpose and duration, and obtain consent before activating non-essential technologies where required. If a third-party feature is loaded only after you choose to use it, that provider may collect technical information and apply its own privacy and cookie terms.
At the date of this policy, no advertising or behavioural-targeting cookie is declared as part of DesignEpic’s core website stack. If we introduce analytics or marketing technologies, we will update this register and the available consent controls before treating them as active.
09
Your cookie choices
When our cookie notice is shown, you can accept or decline the non-essential technologies controlled by that notice. Declining them will not prevent strictly necessary technologies used to provide requested features.
- Use the cookie settings control on our website, where available, to review your choice.
- Clear site data for this domain to remove the saved Blocksy consent choice and display the notice again.
- Use browser settings to view, block or delete cookies and browser storage.
- Use privacy extensions or browser tracking-protection features for additional control over third-party technologies.
Blocking all cookies may prevent WordPress login, Amelia panel access, consent preferences or parts of the booking process from working correctly.
10
Contact and policy updates
Questions about cookies, browser storage or our consent controls can be sent to hello@designepic.com.au .
We may update this policy when our website configuration, plugins, integrations or legal obligations change. The latest version will be published here with a revised “Last updated” date. You can also contact us about personal information collected through these technologies or exercise the rights described in our Privacy Policy .
Need more information?
Ask us about website tracking.
We can explain the technologies active on the DesignEpic website and how to manage your choices.
Important updates waiting for you!
Practical ideas for connected customer journeys, digital systems and better work across APAC.