Sefrum
Data Policy
How Sefrum handles the data required to operate accounts, bots, workflows, subscriptions, and marketplace services.
This Data Policy explains the categories of information Sefrum may collect or store, how that information is used, when it may be shared with service providers, and how long it may be retained. The policy is intended to support transparency while preserving Sefrum's ability to operate, secure, debug, and enforce the platform.
This Data Policy should be read together with the Terms and Conditions and User Agreement.
This policy applies to information processed through Sefrum and related services.
Covered Data means information submitted to, generated by, stored in, or processed through Sefrum, including account data, workflow data, runtime data, billing records, marketplace activity, security records, and support communications.
Operational Data includes information needed to run the platform, such as bot configuration, workflow graphs, command settings, runtime status, logs, token metadata, install records, and service health information.
Security Data includes information used to protect account access and prevent abuse, including rate-limit records, verification events, password reset requests, device or network indicators, IP-derived records, and enforcement-related logs.
Sefrum collects and stores only the categories of data needed to provide, secure, bill, support, and improve the Services.
Account Data may include username, email address, password hash, account creation date, authentication status, verification state, subscription status, affiliate or referral associations, and administrative account records.
Workflow and Bot Data may include bot names, server descriptions, command flows, event flows, generated drafts, installed templates, marketplace submissions, runtime specifications, bot profile data, logs, and user-defined configuration.
Payment and Subscription Data may include plan selections, subscription status, credit balances, order references, marketplace purchase history, checkout records, renewal status, and payment-provider metadata required to reconcile transactions.
Support and Communications Data may include messages sent to Sefrum, support requests, email events, abuse reports, account recovery actions, and related troubleshooting details.
Data is used for legitimate platform operation, account security, billing, support, and abuse prevention.
Sefrum uses data to authenticate users, maintain dashboards, save workflows, operate bot runtimes, install templates, process marketplace activity, manage credits, and provide subscription-based features.
Sefrum may use Security Data to detect duplicate accounts, prevent registration abuse, rate-limit requests, investigate suspicious behavior, respond to chargebacks, secure password reset flows, and enforce platform rules.
Sefrum may use Operational Data to identify failures, repair installation issues, troubleshoot runtime behavior, improve generation quality, and maintain service reliability.
Sefrum uses billing and subscription records to process payments, reconcile orders, apply credits, manage plan access, operate marketplace purchases, and respond to billing questions or disputes.
Sefrum does not sell user data as a product. Data may be shared where necessary to operate the Services.
Sefrum may use third-party providers for hosting, email delivery, payments, analytics, security, infrastructure, support, or other operational needs. Data shared with providers is limited to what is reasonably required for the provider to perform its service.
Payment processors and email providers may receive transaction or delivery information required to process purchases, send verification codes, deliver password reset messages, or support account communications.
Sefrum may disclose information where required by law, to enforce platform policies, respond to abuse, protect rights and safety, investigate fraud, or address security, billing, or operational risk.
Data is retained for as long as reasonably needed to provide the Services, resolve disputes, satisfy operational requirements, and protect the platform.
Account, workflow, subscription, marketplace, and runtime records may be retained while an account is active and for a reasonable period afterward to support account recovery, billing reconciliation, dispute resolution, backups, enforcement, and security review.
Security-related records may be retained where needed to detect abuse, investigate policy violations, prevent repeat misuse, document enforcement actions, or protect Sefrum and its users.
Users may contact [email protected] about account or data questions. Some records may be retained where necessary for legitimate business, security, billing, legal, backup, or enforcement purposes.
Sefrum uses reasonable safeguards, but users must also protect sensitive information connected to their accounts and bots.
Sefrum uses account authentication, password hashing, rate limits, verification flows, access controls, runtime separation, and operational monitoring to help protect the platform.
Users are responsible for protecting bot tokens, API keys, Discord permissions, server access, workflow configuration, and any credentials or secrets they choose to connect to Sefrum.
No online system can guarantee absolute security. Users should configure accounts carefully, rotate compromised credentials, and report suspected account or platform issues promptly.
Questions about this Data Policy may be sent to Sefrum support.
Questions, deletion inquiries, account concerns, or data-related requests may be sent to [email protected].