Cookies help keep you signed in and use the service securely. Here we explain what the website stores in your browser and how you can control it.
At a glance
- Strictly necessary storage supports an action you request, such as signing in.
- Optional analytics and advertising tracking require prior consent. Browsing or silence is not consent.
- In addition to cookies, browser local storage is used to resume website creation.
- For questions, contact info@sibly.pro.
Why does the website store data in your browser?
A cookie is a small record that the browser sends with requests to the relevant website. It may hold a sign-in identifier. Browser local storage lets the website retain data in your browser; unlike cookies, its content is not automatically sent with every request.
These technologies must be assessed by purpose. Storage strictly necessary for a service you explicitly request differs from visit measurement and advertising tracking. The latter require separate, voluntary consent.
Cookies and their use
The table describes the solution checked; actual use depends on the environment and selected action. An asterisk (*) represents a variable part of the name. Not every cookie is created on every visit.
| Name and provider | Purpose and trigger | Duration and findings |
|---|---|---|
| wordpress_logged_in_* Sibly / WordPress | Maintaining the sign-in you requested and identifying your account. | Local code uses a 14-day authentication lifetime. The WordPress browser cookie may expire up to 12 hours later; this does not extend authentication validity. Signing out ends the session. Duration may depend on environment settings. |
| wordpress_sec_* or wordpress_* Sibly / WordPress | Security of authenticated actions; name and use depend on HTTPS and the action. | The same sign-in duration; administration may use other session options. Not a public website analytics cookie. |
| sibly_ssb_state_* Sibly | Linking a Storybook sign-in attempt to the correct browser and preventing forged responses. | Up to 10 minutes in code; deleted on completion. Created only when that sign-in flow is used and the integration is enabled. |
| sibly_ssb_result Sibly | Passing the Storybook sign-in result once. | Up to 10 minutes in code; deleted when the result is read. |
| PHPSESSID Provider depends on the environment | Listed in the older configuration for PHP session management. | Listed as a session cookie. An anonymous local homepage check did not find it being set; it is not treated as a confirmed active cookie. |
Analytics and marketing
The Google Analytics names _ga and _ga_* are commented out in the theme's cookie configuration. No active Google Analytics, Meta Pixel, Hotjar or Microsoft Clarity initialisation was found in the checked theme code. This does not rule out tracking added in production through a plugin, tag manager or server configuration.
Before activating such a service, its name, purpose, provider, actual retention, recipients and, where relevant, international transfer information must be added here. Optional tracking must not start before consent.
Resuming website creation
sibly-website-generation is a Sibly browser storage record. It keeps identifiers for website creation in progress, its start time and the company information entered during creation, so the action can resume after reopening the page.
The code removes the record in relevant completion and clearing scenarios, but the checked implementation has no fixed time-based expiry. An interrupted action's record may remain until the application or user removes it.
On a shared device, sign out after use and, if necessary, clear Sibly site data in your browser settings. Deleting creation data may prevent resuming the action.
How can you control storage?
Your browser settings let you view and remove a website's cookies and other site data. Look for “Site data” or “Cookies” in privacy settings and select the Sibly domain. Removal may sign you out or erase an action in progress.
The local preview does not have a separate cookie preference manager. You can view and delete saved site data in your browser settings.
If optional services are added, the consent interface must provide equally clear choices: “Necessary only”, “Allow all” and “Customise”. Optional categories are off by default. The footer must provide a persistent way to change preferences and withdraw consent as easily as giving it. Withdrawal must stop further optional storage and relevant requests.
Deleting browser data does not replace the website's consent withdrawal mechanism. Consent management and script blocking must be tested together.
Webmail, help centre and external services
This description covers Sibly's main website. Webmail, the help centre, Storybook authentication and payment pages may use their own technical cookies and settings. Each environment must be assessed separately; this check did not cover all those services.
A link to another website does not itself mean that provider's cookies are active on Sibly's homepage. Embedded content or authentication functionality may, however, cause requests to a service partner.
Storybook OÜ is responsible for personal data processing on Sibly's main website. See also the privacy policy and data security principles.
A question about cookies?
Contact info@sibly.pro with the page address and your question. Do not send authentication cookie values or sign-in tokens.