# Privacy Policy ## 1. Who is responsible **Nirvana Travel Club LLC** operates Meltyfox Chat. **Nick Danilov** is its contact representative. Legal contact: nirvanatravelclub@gmail.com and https://www.nirvana-travel.com/en/contacts For account administration, security and billing, the operator determines the processing purposes. For a customer's widget, the customer chooses its content, audience and staff access; Meltyfox processes information to run that service. Contact the website's organization about its own use of conversations. Roles depend on the actual processing, not just these labels. ## 2. Information processed - Account and organization details: email, names, organization code, memberships, password hashes, verification records and authentication sessions. - Customer content: instructions, widget settings, avatars, pasted text, extracted TXT/PDF text, public-page URLs and stored text snapshots, plus original/English knowledge and search chunks. The PDF binary is not stored as the knowledge source. - Conversations: visitor identifiers, messages, English variants/search queries, English answers and delivered translations, language choices, timestamps, available page context, participant display details and handoff activity. - Team contacts: names, email addresses, optional phone numbers, avatars, channel settings, restricted-access grants, summaries and notification status. Configurable SMS fields do not mean an SMS provider is active. - Operations: IP addresses or derived rate-limit identifiers, sign-in browser/user-agent details, usage/provider/model/token records, credit ledgers, purchase/payment/refund identifiers and amounts, and exact document-version acceptance or acknowledgment records. ## 3. How the service uses it Processing supports sign-in, organization access, knowledge retrieval, AI answers, translations, human handoff, transactional email, billing, quotas and abuse prevention. Original/English views help authorized teams review knowledge and conversations. Imported pages are stored snapshots; changing the source website does not automatically update or erase them. Human-only messages remain original-only, without automatic translation calls. This is not a promise that human conversation history never reaches AI: relevant history can accompany an assistant request or handoff summary. A required Privacy Policy acknowledgment confirms receipt, not blanket consent or a waiver of rights. ## 4. Who receives information Authorized customer staff can review their widget's conversations and knowledge; assigned operators receive restricted conversation access. Published content, replies, display names and avatars can be visible to visitors. ## 5. Cookies and browser storage Authentication and restricted operator access use cookies. Local browser storage preserves sandbox access; session storage preserves widget conversation access and language choices across same-tab navigation. Clearing storage can lose access without deleting server records. The loader sends the host origin/path and language hints. Optional browser-native language detection examines a bounded visible-text sample locally; that sample is not sent for remote language detection. Submitted chat and imported knowledge are separate provider flows described above. ## 6. Retention and deletion Public sandboxes have configurable expiry and trash periods; code defaults are 24 hours active and seven days in trash, not confirmed production settings. Expired sandboxes become inaccessible. Platform administrators can restore them before purge. Purge removes their application data, including knowledge copies/chunks, inline avatars, conversations, messages and usage records. Keep my widget transfers a sandbox into an authorized organization and excludes it from sandbox purge. Customer widgets and records persist; no general automatic account/customer-data deletion schedule is implemented. Removing a knowledge source removes its original/English text and search chunks, not necessarily earlier replies, provider copies or backups. Removed operators can leave historical messages/audit records; expired verification/access links do not imply their records are erased. Unpublishing is not deletion. ## 7. Requests, safety and changes Depending on applicable law and our role, you may have access, correction, deletion, restriction, objection, portability or complaint rights. Contact the privacy address above, or the customer responsible for its widget. Do not submit highly sensitive data or other people's information without authorization. English is the original; automated translations are convenience copies. The record identifies the exact version acknowledged. ## 8. Optional Meltyfox SMS notifications Nirvana Travel Club LLC operates the Meltyfox operator SMS notification program. When available, the program sends requested phone-verification codes and recurring notifications about website conversations that need a widget operator. It is not a marketing program or a way to send messages to website visitors. Message frequency varies with chat activity and verification requests. Message and data rates may apply. **Information and purposes.** We process an operator's mobile number, organization and widget association, SMS preferences, consent wording/version and timestamps, verification status, activation and verification records, message content and delivery records, and incoming messages such as STOP, START and HELP. We use this information to verify the number, provide the requested notifications, record consent, honor opt-outs, prevent abuse, handle support requests, and account for message delivery and charges. Activation tokens and verification codes are stored as hashes in the consent record; message providers process the verification message needed for delivery. **No marketing sharing.** We do not sell, rent, or share mobile phone numbers, SMS opt-in data, or SMS consent with third parties or affiliates for their marketing or promotional purposes. Text messaging opt-in data and consent are excluded from any permission elsewhere in this policy to share information for marketing or promotional purposes. **Service providers and authorized access.** We provide information needed to deliver and administer the program to Twilio, telecommunications carriers, and hosting/service providers acting to support the program. These operational disclosures are not permission for recipients to use SMS opt-in data for their own marketing. Authorized Meltyfox personnel and the relevant organization's administrators can access SMS configuration, consent status and delivery information needed to operate and support the service. We may also disclose information when required by applicable law. **Choice and records.** SMS is optional. An administrator adding a number or creating an invitation does not establish the recipient's consent. The recipient reviews the invitation, selects the SMS consent checkbox, requests a code, and verifies the number before recurring alerts are activated for that widget. **Reply STOP to stop Meltyfox SMS notifications to your number, or HELP for assistance.** Opting out does not automatically erase records: we retain consent, delivery, and suppression records as described in section 6 to honor your choice, investigate delivery problems, and maintain appropriate records. START permits a new activation; it does not restore previous widget subscriptions automatically. For SMS or privacy questions, email [nirvanatravelclub@gmail.com](mailto:nirvanatravelclub@gmail.com). See [SMS help](https://meltyfox.com/sms/help) and the [Terms and Conditions](https://meltyfox.com/docs/terms-and-conditions).
Privacy Policy
English original
Privacy Policy
# Privacy Policy ## 1. Who is responsible **Nirvana Travel Club LLC** operates Meltyfox Chat. **Nick Danilov** is its contact representative. Legal contact: nirvanatravelclub@gmail.com and https://www.nirvana-travel.com/en/contacts For account administration, security and billing, the operator determines the processing purposes. For a customer's widget, the customer chooses its content, audience and staff access; Meltyfox processes information to run that service. Contact the website's organization about its own use of conversations. Roles depend on the actual processing, not just these labels. ## 2. Information processed - Account and organization details: email, names, organization code, memberships, password hashes, verification records and authentication sessions. - Customer content: instructions, widget settings, avatars, pasted text, extracted TXT/PDF text, public-page URLs and stored text snapshots, plus original/English knowledge and search chunks. The PDF binary is not stored as the knowledge source. - Conversations: visitor identifiers, messages, English variants/search queries, English answers and delivered translations, language choices, timestamps, available page context, participant display details and handoff activity. - Team contacts: names, email addresses, optional phone numbers, avatars, channel settings, restricted-access grants, summaries and notification status. Configurable SMS fields do not mean an SMS provider is active. - Operations: IP addresses or derived rate-limit identifiers, sign-in browser/user-agent details, usage/provider/model/token records, credit ledgers, purchase/payment/refund identifiers and amounts, and exact document-version acceptance or acknowledgment records. ## 3. How the service uses it Processing supports sign-in, organization access, knowledge retrieval, AI answers, translations, human handoff, transactional email, billing, quotas and abuse prevention. Original/English views help authorized teams review knowledge and conversations. Imported pages are stored snapshots; changing the source website does not automatically update or erase them. Human-only messages remain original-only, without automatic translation calls. This is not a promise that human conversation history never reaches AI: relevant history can accompany an assistant request or handoff summary. A required Privacy Policy acknowledgment confirms receipt, not blanket consent or a waiver of rights. ## 4. Who receives information Authorized customer staff can review their widget's conversations and knowledge; assigned operators receive restricted conversation access. Published content, replies, display names and avatars can be visible to visitors. ## 5. Cookies and browser storage Authentication and restricted operator access use cookies. Local browser storage preserves sandbox access; session storage preserves widget conversation access and language choices across same-tab navigation. Clearing storage can lose access without deleting server records. The loader sends the host origin/path and language hints. Optional browser-native language detection examines a bounded visible-text sample locally; that sample is not sent for remote language detection. Submitted chat and imported knowledge are separate provider flows described above. ## 6. Retention and deletion Public sandboxes have configurable expiry and trash periods; code defaults are 24 hours active and seven days in trash, not confirmed production settings. Expired sandboxes become inaccessible. Platform administrators can restore them before purge. Purge removes their application data, including knowledge copies/chunks, inline avatars, conversations, messages and usage records. Keep my widget transfers a sandbox into an authorized organization and excludes it from sandbox purge. Customer widgets and records persist; no general automatic account/customer-data deletion schedule is implemented. Removing a knowledge source removes its original/English text and search chunks, not necessarily earlier replies, provider copies or backups. Removed operators can leave historical messages/audit records; expired verification/access links do not imply their records are erased. Unpublishing is not deletion. ## 7. Requests, safety and changes Depending on applicable law and our role, you may have access, correction, deletion, restriction, objection, portability or complaint rights. Contact the privacy address above, or the customer responsible for its widget. Do not submit highly sensitive data or other people's information without authorization. English is the original; automated translations are convenience copies. The record identifies the exact version acknowledged. ## 8. Optional Meltyfox SMS notifications Nirvana Travel Club LLC operates the Meltyfox operator SMS notification program. When available, the program sends requested phone-verification codes and recurring notifications about website conversations that need a widget operator. It is not a marketing program or a way to send messages to website visitors. Message frequency varies with chat activity and verification requests. Message and data rates may apply. **Information and purposes.** We process an operator's mobile number, organization and widget association, SMS preferences, consent wording/version and timestamps, verification status, activation and verification records, message content and delivery records, and incoming messages such as STOP, START and HELP. We use this information to verify the number, provide the requested notifications, record consent, honor opt-outs, prevent abuse, handle support requests, and account for message delivery and charges. Activation tokens and verification codes are stored as hashes in the consent record; message providers process the verification message needed for delivery. **No marketing sharing.** We do not sell, rent, or share mobile phone numbers, SMS opt-in data, or SMS consent with third parties or affiliates for their marketing or promotional purposes. Text messaging opt-in data and consent are excluded from any permission elsewhere in this policy to share information for marketing or promotional purposes. **Service providers and authorized access.** We provide information needed to deliver and administer the program to Twilio, telecommunications carriers, and hosting/service providers acting to support the program. These operational disclosures are not permission for recipients to use SMS opt-in data for their own marketing. Authorized Meltyfox personnel and the relevant organization's administrators can access SMS configuration, consent status and delivery information needed to operate and support the service. We may also disclose information when required by applicable law. **Choice and records.** SMS is optional. An administrator adding a number or creating an invitation does not establish the recipient's consent. The recipient reviews the invitation, selects the SMS consent checkbox, requests a code, and verifies the number before recurring alerts are activated for that widget. **Reply STOP to stop Meltyfox SMS notifications to your number, or HELP for assistance.** Opting out does not automatically erase records: we retain consent, delivery, and suppression records as described in section 6 to honor your choice, investigate delivery problems, and maintain appropriate records. START permits a new activation; it does not restore previous widget subscriptions automatically. For SMS or privacy questions, email [nirvanatravelclub@gmail.com](mailto:nirvanatravelclub@gmail.com). See [SMS help](https://meltyfox.com/sms/help) and the [Terms and Conditions](https://meltyfox.com/docs/terms-and-conditions).
Content hash: b5b98c4c1d59f1bbfbc4478d4a99a8333705112a8f67ec3d25fda1156584e960