Leonidas Credit Policy
Effective Date
June 3, 2026
Applies To
Public website content, company policy pages, educational materials, product and platform descriptions, market commentary, stakeholder communications, and correction or feedback submissions received by Leonidas Credit.
-
Purpose
This Policy sets a simple, consistent process. First, it shows how we receive actionable feedback. Then it explains how we publish information responsibly. Finally, it describes how we correct material errors once we find them. Our goal is clear, useful, and responsible information. We write it for regulated cannabis operators, financial institutions, service providers, regulators, and other stakeholders.
-
Scope
This Policy applies to general information we publish or distribute. That includes website pages, policy statements, educational resources, platform descriptions, public articles, presentations, and stakeholder communications. However, it does not replace other commitments. Any contract, privacy policy, terms of service, regulatory obligation, or legal requirement that applies to Leonidas Credit still governs.
-
Actionable Feedback
Actionable feedback is specific, good-faith information that we can reasonably evaluate. For example, it might flag a question, a concern, a potential error, a usability or accessibility issue, a product improvement, a communication gap, or a data concern. Feedback works best when it includes the relevant webpage or document, the date, a description of the issue, the requested change, and any supporting information.
-
How to Submit Feedback
Submit feedback by email to admin@leonidascredit.com. So that we can review it quickly, include your name and organization, your contact information, the subject of the feedback, and the affected webpage or communication. Also add a clear description of the issue or recommendation, plus any supporting information.
-
Feedback Review
We review actionable feedback in good faith. Depending on the subject, we route it to the right people. Those advisors may handle product, operations, compliance, legal review, security, marketing, website management, or executive oversight. If we need more information to evaluate a submission, we will ask for it.
-
Publishing Principles
We aim to publish information that is accurate, clear, relevant, and useful. Public content should read professionally and avoid misleading statements. It should also separate general information from legal or financial advice, so readers understand the difference. Above all, it should reflect our role in the regulated cannabis finance and data environment.
-
Content Standards
We aim to publish content that is fair, balanced, and understandable. Therefore, our content avoids unsupported claims, unnecessary exaggeration, and discriminatory language. It also avoids confidential or private customer information. Finally, it avoids statements that could confuse readers about our services, obligations, regulatory status, or commercial relationships.
-
Sources and Support
Where appropriate, we may rely on outside and internal sources. These include public data, third-party research, regulatory materials, customer-authorized information, internal analysis, market observations, and subject matter review. However, we avoid presenting estimates, projections, opinions, or preliminary observations as settled facts.
-
Product and Market Descriptions
Before we publish them, we review descriptions of our products, services, workflows, integrations, data practices, reporting tools, and market opportunities for clarity and accuracy. We also avoid promises we cannot back up. So we do not commit to features, timelines, financing outcomes, regulatory treatment, payment outcomes, or customer results unless the claim is approved and supported.
-
Corrections Policy
We correct material errors in public content once we find and verify them. A material error takes several forms. For example, it might be an inaccurate fact, an outdated description, a broken or misleading reference, incorrect contact information, or an inaccurate product description. In short, it is any issue that could affect how a reader understands the content.
-
Correction Requests
A correction request should identify the specific content and explain why it may be inaccurate or misleading. It should also provide supporting information and describe the requested fix. However, we may decline a request when it is unsupported, incomplete, duplicative, or abusive. We may also decline when it is unrelated to our content, or based on a disagreement with opinion, framing, or business judgment rather than a verifiable error.
-
Correction Review Process
We review correction requests in good faith. To do so, we compare the content against trusted references. These may include our records, public sources, internal documentation, customer-authorized information, regulatory materials, or subject matter input. If we confirm a material error, we may revise, clarify, remove, replace, or update the content.
-
Updates and Clarifications
We handle some changes as routine updates rather than corrections. For example, a routine update might refresh a date, improve wording, add context, or revise an example. It might also update a product description, change policy language, or add new contact information. These changes often reflect business, legal, regulatory, or operational developments.
-
Transparency
When appropriate, we may note that content has been updated or corrected. However, we do not maintain a public change log for every edit, formatting change, or routine update. Instead, we choose the best way to communicate a correction based on how significant the issue is.
-
Independence and Conflicts
We avoid content that creates a false impression. For example, it should not wrongly suggest independence, endorsement, partnership, a customer relationship, regulatory approval, or third-party support. When it is relevant, we may disclose material relationships or context, so readers understand the nature of a statement.
-
Respectful Communications
We expect feedback and correction requests to be professional and respectful. Therefore, we may disregard or restrict abusive communications. Examples include threats, harassment, discriminatory language, personal attacks, profanity, spam, malicious content, or repeated submissions meant to disrupt our operations.
-
Non-Retaliation
We do not tolerate retaliation. This protects anyone who submits feedback, requests a correction, asks a question, or takes part in a review in good faith. However, it does not stop us from addressing submissions that are knowingly false, abusive, unlawful, or made in bad faith.
-
No Guarantee of Action
Submitting feedback or a correction request does not require us to act. For instance, no single outcome is guaranteed. We are not obligated to make a product change, a policy change, or a website change. Nor are we required to issue a public statement, open an investigation, amend a contract, or provide a refund or credit. Instead, we keep the discretion to decide whether and how to address each submission.
-
Policy Review
We may review, revise, or update this Policy from time to time. We may also adopt additional procedures, intake forms, review workflows, editorial standards, or escalation processes that support it.
-
No Creation of Legal Rights
This Policy is a public statement of our process and intent. Therefore, it creates no new rights. It does not establish contractual rights, employment rights, or third-party beneficiary rights. Nor does it provide legal advice, financial advice, regulatory advice, a service-level agreement, or a guarantee of any outcome.