Back to Here
Privacy Policy
Last updated:
The company below is responsible for the personal data processed by Back to Here. Basic practices work without an account. We do not use advertising trackers or session replay. Self-hosted Umami provides aggregate public-page traffic and recent active-visitor statistics. Optional Google Analytics runs only after you allow it.
Legal operator / data controller
北京金色黎明科技有限公司
Beijing Golden Dawn Technology Co., Ltd.
- Country of registration
- China
- Registered address
- Room 336, 1st Floor, Nos. 318–354 Jingkai Road, Huangcun Town, Daxing District, Beijing, China
- Customer support and privacy requests
- support@backtohere.com
The English name and address are translations for reference. The Chinese name is the registered legal name.
1. Free tools and browser storage
We do not collect your grounding observations. CBT worksheets and appointment notes remain in the open page’s memory; they are not sent to our server or AI and are cleared when you leave or refresh.
Your browser may store sound preferences, the date and ID of today’s thought, and saved thought IDs in local storage. These remain until you clear site data. Temporary exercise progress can be stored in this tab’s session storage when switching languages and ends when the tab session ends. You can clear this data in your browser; core practices still work if storage is unavailable.
Our self-hosted Umami analytics records public page paths, referring website origins, browser and device information, language and approximate location to understand traffic and recent activity. It uses no analytics cookies. We remove URL query strings and fragments, replace page titles with the site name, respect browser Do Not Track, and exclude account, sign-in, private AI and administration pages. We do not send form entries, conversations, email addresses, account IDs or exercise observations to analytics. Analytics data is accessible only to our authorised operators.
If you choose Allow analytics, we also use Google Analytics 4 (Google) for selected public-page visits and related session statistics. Before you allow it, we do not load the Google tag or send it analytics requests. Google receives a random cookie identifier, the permitted page path, browser/device information and the IP address needed for the network connection. We send a fixed site title and no URL query or fragment; external referrers are limited to their website origin; we exclude account, authentication, billing, administration, AI chat, CBT and appointment-note pages. We do not send user IDs, form text or exercise content, and disable Google signals and advertising personalization. This choice controls Google Analytics separately from the cookie-free Umami statistics above.
Google Analytics cookies and your consent choice are configured for up to 180 days. Use Analytics settings to decline or withdraw at any time; withdrawal stops future collection and removes our accessible Google Analytics cookies, but does not delete data already received by Google. Browser Do Not Track and Global Privacy Control keep Google Analytics disabled. Google may process data outside your country under its privacy policy: https://policies.google.com/privacy. Necessary account cookies are unaffected.
2. Accounts, security and payments
For accounts we store your email, internal user ID, verification status, password hash and creation time. Passwords are protected using salted scrypt hashes. Login sessions use a cookie named pause_session, valid for up to 7 days; the server stores a hash of the session token. The cookie is HttpOnly, SameSite=Lax and Secure on HTTPS. It is used for login, not advertising.
Registration, email-code login and password resets send your email, purpose and language to our Golden Dawn transactional email service, which we operate on Railway. It delivers and checks one-time codes. Our site stores the associated request ID, email, expiry and, during registration, a password hash. Codes are valid for 10 minutes and are single-use.
For paid plans we store the subscription status, product and order references, billing interval, relevant billing event IDs and monthly reply counts. We send Waffo your account email, stable user ID and selected plan to create checkout and manage access. Waffo handles payment details and may collect billing information and fraud-prevention data under its own checkout disclosures; we do not store full card numbers or card security codes.
We use hashed identifiers derived from an IP address, email or user ID, with short-lived counters, to limit abuse. Hosting and network providers also receive the IP address, request details and technical information needed to deliver and secure the service.
3. Optional AI conversations
Only after you check the AI consent box, we send your message, recent conversation context and selected Guide instructions to OpenAI. When OpenRouter routing is enabled, OpenRouter receives and forwards this content to the OpenAI model. Our current hosted AI configuration uses that route. Neither your account email nor our internal user ID is added to the model request.
Back to Here does not save chat history. The page holds the conversation in memory and clears it when you refresh, leave or choose “Clear conversation”. This does not delete copies a service provider may retain. Text you choose to send may contain sensitive information; avoid names, contact details, identity numbers and personal medical reports.
OpenAI API data is not used to train its models by default. Its abuse-monitoring logs can retain content for up to 30 days, with exceptions described in its policy. OpenRouter and model providers apply their own retention rules and account settings; routing is not a guarantee of zero retention. We do not promise that third parties immediately erase every message.
You can decline or withdraw consent by leaving the box unchecked and stopping AI use. Free exercises remain available. Withdrawing consent stops future submissions; it does not reverse earlier processing.
4. Reviews and support messages
If you submit a review, we store your chosen display name, rating, review text, language, time and moderation status. Reviews are private pending moderation; approved reviews publish the display name, rating and text. Do not include identifying or medical information. Contact support to request correction or removal.
If you email support, we receive the address, message and attachments you choose to send. Cloudflare Email Routing forwards support mail to our monitored mailbox. Our mail provider processes these messages so we can answer account, billing and privacy requests. Please do not email passwords, verification codes, full card details or unnecessary sensitive records.
5. Purposes, providers and international processing
We use account and billing data to provide the service you request, consented content for optional AI and public reviews, technical data to prevent abuse, and relevant records to meet legal obligations or resolve disputes. Where a legal basis is required, the applicable basis depends on these purposes and the law that applies to you. We do not sell personal data or use chat content for marketing.
Railway hosts the website, private databases and transactional email service. Cloudflare provides domain, network and support email routing services. Waffo handles payments. OpenRouter and OpenAI handle consented AI requests. Access is limited to the company and providers who need the data for these functions, or where disclosure is legally required.
Our operator is in China, while hosting and AI services may process data in Europe, the United States and other countries outside your location. Data protection rules can differ between countries. Contact us before using an optional feature if you need further details.
6. How long data remains
Account, subscription and usage records are retained while your account exists, then reviewed for deletion when we complete a verified erasure request. The site does not currently offer automatic account deletion. Records needed for unresolved billing disputes or applicable legal obligations may be retained longer, with the reason explained in response to your request. Waffo’s financial records have its own retention requirements.
Login sessions stop working after at most 7 days and are removed on logout or later session cleanup. Verification requests stop working after 10 minutes; used requests are removed, and expired requests are cleaned up when new requests of the same type are created. Expiry is not a claim that every stored record is erased at that exact instant. Abuse counters use windows of up to one hour and are cleaned up as further requests arrive.
Review submissions remain until removed through moderation or a verified removal request; approved reviews remain public until withdrawn. Support correspondence is retained while needed to handle the request and related billing, security or legal issues. Local browser data remains under your control as explained above; third-party retention is governed by the linked provider policies and their settings.
7. Your choices and requests
Email support@backtohere.com to request access, correction, a copy, deletion, or restrictions or objections available under applicable law. Use your account email when possible. We may ask for information proportionate to verifying ownership; do not send an identity document unless we explain why it is needed.
There is no self-service deletion button at present; requests are handled by support. We will explain the action taken and any lawful reason a record must remain. Account deletion and cancellation are separate: cancel an active subscription through Account or ask support to help stop renewal. You may also complain to the competent data protection authority where applicable.
8. Age, security and updates
Accounts and paid AI features are intended for people aged 18 or older. We do not knowingly register children. Contact us if you believe a child has provided account data so we can review and remove it as appropriate.
We use HTTPS, password hashing, server-side access checks and private storage. No service can promise absolute security. This policy will be updated when data practices change; material changes will be communicated through the service or account email. The date above identifies the current version.