noospheric bot | privacy & payment

• 1 min read

how user data is handled

storage

  • to enable multi-turn roles, we save chat histories on our servers temporarily. all chat history entries evaporate after a set TTL of 2 weeks no-use.
  • at any time, users may /clear_all of their chat history without leaving a trace.
  • conversational data isn’t used/collected for any purposes outside of noospheric’s main functions offered.

request path (pipeline)

  • 3’rd party: requests are parsed exclusively through openrouter with denied data-retention and without prompt/response-logging.
  • 3’rd party: telegram’s bot privacy policy applies additionally.
  • we advise users to not share sensitive or personal data. our internal and openrouter’s redaction, can’t account for all contents. please do not include: real names and addresses, nor any sensitive fields alike.
  • all requests are bundled into a single pool without user IDs hitting inference endpoints.
  • voice message inputs are sent forward-only to an eligible STT model, then converted to user-prompt text.

stripe

  • stripe is exclusively used for binary verification of user subscription-status. other stripe entries never touch DB.
  • if a recurring payment fails 4 times over 2 days, the subscription is canceled. add a backup payment method to prevent.
  • for any payment-related issues, questions, or help (pro), please contact axotyc+noo@gmail.com immediately.