> For the complete documentation index, see [llms.txt](https://cth-development.gitbook.io/store-elements-for-tebex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cth-development.gitbook.io/store-elements-for-tebex/support-and-privacy/privacy-cookies-and-support.md).

# Privacy, Cookies, and Support

Store Elements for Tebex uses only the data needed to connect your Wix site to Tebex, run store elements, manage licensing and provide support.

This guide explains what the app stores, how cookies are used and how to contact support.

### Privacy Policy and Terms of Service

You can view the current legal documents here:

* [Privacy Policy](https://tebex-wixapp.callumthull.com/privacy-policy)
* [Terms of Service](https://tebex-wixapp.callumthull.com/terms-of-service)

### Data stored by the app

The app stores information needed to operate each Wix app installation.

This can include:

* Wix app instance identifiers.
* Wix account/site identifiers needed to manage the installation.
* Encrypted site owner email address; provided by Wix.
* Encrypted Tebex Public Token.
* Encrypted Tebex Private Key.
* Detected Tebex store information.
* Billing, trial and licence status.
* Support requests.
* Optional support diagnostics.
* Troubleshooting/error logs.

{% hint style="info" %}
Tebex Private Keys are encrypted before being saved. The dashboard does not show the Private Key back to you.
{% endhint %}

### Why installation data is retained

Installation, billing, licence and anti-abuse records may be retained after uninstall for a limited period.

This helps:

* Prevent repeated trial abuse.
* Keep billing state accurate.
* Support reinstall and troubleshooting scenarios.
* Meet legal and operational requirements.

See the Privacy Policy for the current retention details.

### Cookies and browser storage

Store Elements for Tebex uses functional browser storage for store features such as:

* Basket session.
* Login state.
* Checkout flow state.
* Discord connection flow state, when used.
* Pending basket actions.

These are required for the store experience to work correctly.

{% hint style="warning" %}
If a visitor denies required cookies or browser storage through cookie consent settings, login, basket and checkout actions may be blocked until consent is accepted.
{% endhint %}

### How cookie consent works

The app checks the site user's current consent status.

The behaviour is:

| Consent state           | App behaviour                                                |
| ----------------------- | ------------------------------------------------------------ |
| No preference specified | Continue as normal.                                          |
| Allowed                 | Continue as normal.                                          |
| Denied                  | Block login, basket and checkout flows that require cookies. |

### No marketing cookie use

Store Elements for Tebex uses browser storage for functional store behaviour.

The app does not use these basket/session cookies for advertising or marketing tracking.

### Support form

The dashboard includes a Support card.

To send a support request:

1. Open your Wix dashboard.
2. Go to **Apps > Store Elements for Tebex**.
3. Scroll to the Support card.
4. Enter your name, email, subject and message.
5. Choose whether to include app diagnostics.
6. Send the request.

### Support ID

The Support card shows:

**Support ID**

This identifies the Wix app installation/site you need help with.

Include the Support ID when contacting support outside the dashboard or when not including app diagnostics.

### App diagnostics

The support form can optionally include app diagnostics.

Diagnostics are designed to help troubleshoot setup and store connection issues.

They can include information such as:

* Wix instance identifiers.
* Detected store type.
* App setup status.
* Billing/licence status.
* Tebex connection status.
* Recent relevant app state.

Diagnostics do not include your Tebex Private Key.

{% hint style="warning" %}
Do not paste your Tebex Private Key into support messages; support does not need it.
{% endhint %}

### Error logging

The app records some errors so support can troubleshoot issues.

Logs are designed to avoid exposing secrets or unnecessary personal data; they're retained for a limited period. For more information, see the Privacy Policy.

### Contact email

You can contact support through the dashboard support form or by email:

<seft-support@callumthull.com>

For the fastest help though, **get in touch via the Dashboard**, include app diagnostics and give a clear description of the issue.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cth-development.gitbook.io/store-elements-for-tebex/support-and-privacy/privacy-cookies-and-support.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.