Read-only access
You may read public religious, project, policy and ledger information without connecting a wallet. Read-only viewing does not itself prove wallet control, identity or acceptance of an unrelated transaction.
Terms v3.0.0 · Effective 2026-08-31
Use JCS where permitted.Own your choices and your risk.
These Terms allocate responsibility across the current JCS faith, fellowship and XRP Ledger ecosystem. JCS is non-custodial, public-ledger actions can be irreversible, experimental features can fail, and official JCS cannot control what a third party later forks, modifies, augments, wraps or republishes.
Core rule: use is voluntary. Review every wallet request, protect other people’s privacy, do not rely on JCS as a professional adviser or guaranteed service, and do not treat religious language, software, NFTs, metrics or roadmaps as a promise of financial, legal, technical or spiritual outcomes.
Liability language cannot lawfully erase every possible claim. These Terms use the strongest defensible structure without pretending mandatory law can be waived: conspicuous AS-IS warranties, assumption of inherent risk, user responsibility, downstream-modification separation, excluded damage categories, indemnification and a monetary cap—each only to the maximum extent applicable law permits.
Terms contents
1. Acceptance, electronic assent, and notice
These Terms govern access to and use of JCS-controlled pages and application features. They apply to read-only use to the extent applicable and, more importantly, to interactive actions such as connecting a wallet, preparing or approving a transaction, minting an NFT, publishing a prayer or testimony, creating a reply or Amen reaction, using a Private Capsule receipt, or otherwise instructing JCS software to perform an action.
Interactive acceptance
When an interactive JCS surface conspicuously states that clicking, submitting, connecting, signing or proceeding constitutes agreement to these Terms, taking that action manifests assent to the then-current Terms and Privacy Policy.
Decline
If you do not agree, do not use transaction-capable, publishing, account or other interactive features. You may stop using JCS at any time, subject to irreversible records already created on public networks.
Contract-formation design: JCS intends interactive surfaces to use conspicuous, action-linked notice rather than relying only on a footer link. The browser acknowledgment below is optional local evidence and does not substitute for action-specific notice on other pages.
No local Terms acknowledgment recorded.
2. Project identity, religious purpose, and no implied legal status
Jesus Christ Saves Token (JCS) is a Christ-centered XRP Ledger project and application ecosystem intended to support Scripture, prayer, testimony, public verification, responsible fellowship and related technology. The mission is religious and educational; technology is a tool rather than a source of salvation, sacramental authority or human worth.
Use of JCS does not create church membership, ordination, clergy status, a pastoral relationship, a fiduciary relationship, charitable-beneficiary status, agency, employment, partnership, joint venture or authority to act for JCS.
Legal-status boundary: describing JCS as a Christian ministry does not itself create or prove status as a church, nonprofit corporation, public charity, tax-exempt organization, integrated auxiliary or organization recognized under Internal Revenue Code §501(c)(3). No payment is tax deductible unless JCS separately provides legally sufficient written confirmation.
3. Eligibility, authority, and lawful use
- Transactional and public-publishing features are intended for adults with legal capacity, or users acting with any legally required parent/guardian involvement.
- You must have authority to control the wallet, funds, tokens, NFTs, names, handles, text, files and other material you use or submit.
- You may not use JCS where your activity is prohibited by applicable law, binding court order, sanctions restriction, contractual duty or binding platform rule.
- You are responsible for assessing whether public Christian expression, blockchain use, token activity or wallet association creates legal or personal risk in your location.
- You must not use another person’s identity, wallet, device, private content or credentials without lawful authorization.
4. What JCS provides—and what each surface is
About, Privacy, Security, Metrics, public Account Readiness
Primarily read-only information and public-ledger observation. These pages are not supposed to create signing requests merely because they are viewed.
Main portal and Sign the Ledger
May prepare JCS trustline, trade, offer, cancel, NFT or public-registry transactions for independent Xaman review and user approval.
Private Capsule
Browser-local encryption/decryption workflow with an optional neutral public receipt. It is experimental and is not a guaranteed secure-messaging service.
JCS is an interface and ministry resource. Unless a separately executed written agreement expressly says otherwise, JCS does not operate the XRP Ledger, control validators, custody user funds, guarantee execution, provide brokerage or exchange custody, create an escrow, guarantee a market, guarantee a response to prayer or guarantee that a third-party service will remain available.
5. Xaman authorization, wallet control, and signing responsibility
Non-custodial boundary
JCS should never need your seed phrase, recovery phrase, private key, Xaman passcode or device passcode. Xaman controls wallet authorization and signing.
Your approval is decisive
A transaction template prepared by JCS is only a proposal. You must review the actual Xaman request before approving it.
Review every field
Review network, account, transaction type, destination, issuer, currency, amount, fee, slippage/offer terms, NFT fields, Destination Tag, memos and verification challenge where present.
Device and credential responsibility
You are responsible for wallet security, backups, device security, malicious extensions, screen sharing, phishing and access control. JCS cannot restore a lost secret or reverse a valid transaction.
6. Public XRP Ledger records, permanence, and religious privacy
XRPL is a public decentralized network. Wallet addresses, validated transactions, balances, trust lines, offers, NFT identifiers, memos and related metadata can be copied, indexed, analyzed, archived and redistributed by persons outside JCS control.
- JCS cannot privately erase or rewrite a validated XRPL transaction.
- Removing content from a JCS interface does not remove it from XRPL, explorers, archives, screenshots or independent copies.
- Shortening or hiding an address in the interface does not make the underlying wallet anonymous.
- A public prayer, testimony, reply, NFT, memo or wallet association can reveal or strongly imply Christian religious activity.
High-risk believer warning: do not publish exact location, safe-house information, travel or extraction routes, congregation, employer, school, family identifiers, vulnerable third-party identities or other facts that could expose a person to persecution, retaliation, stalking, detention or physical harm.
7. Transaction status, validation, and evidence limits
A QR code, Xaman handoff, signature, submission, local confirmation message, pending hash or unvalidated server response is not by itself a successful final transaction. When a JCS workflow represents settlement or completion, the intended security boundary is a matching transaction in a validated XRPL ledger with the expected result and fields.
JCS evidence exports, receipts, hashes, NFT fingerprints and timestamps can document technical observations. They do not automatically prove legal identity, beneficial ownership, authorship, truth, authenticity, title, contract performance, regulatory compliance, damages, liability, pastoral authority or admissibility in a legal proceeding.
8. JCS token, NFTs, DEX, AMM, price, liquidity and regulatory risks
Volatility
JCS, XRP, NFTs and related assets can rise, fall sharply, become illiquid or lose all market value.
Execution risk
Order books and AMMs can produce slippage, partial fills, stale quotes, failed transactions or materially different execution from a preview.
No promised market
No person must purchase, redeem, list, support, market-make or maintain liquidity for JCS or a JCS NFT.
Regulatory/tax change
Law, tax treatment, platform access, sanctions rules and regulatory interpretations can change without notice and vary by jurisdiction.
No equity or deposit
JCS and JCS NFTs are not represented by these Terms as stock, debt, insured deposits, bank accounts, ownership of the ministry or guaranteed-return products.
Metrics are informational
Prices, holder counts, obligations, liquidity, network value and similar calculations can be incomplete, delayed or wrong and are not appraisals or investment advice.
You decide independently whether any token, NFT, trust line, offer, swap or transaction is appropriate. Religious language is not a financial guarantee.
9. Prayers, testimonies, replies, reactions, names and other user content
You retain whatever legal rights you hold in your original content. By deliberately submitting content for public JCS display or signing it into a public XRPL transaction, you grant JCS a nonexclusive, worldwide, royalty-free license to reproduce, format, display, index, link, translate for accessibility, distribute and preserve that public content as reasonably necessary to operate, explain, secure and archive the JCS service.
You represent that you have authority to submit the content and that it does not unlawfully infringe another person’s intellectual-property, privacy, publicity, confidentiality or other rights. Do not expose another person’s medical, legal, financial, family, location or identity information without lawful authority and informed permission.
JCS may hide, filter, decline to feature or stop indexing content on JCS-controlled interfaces for safety, policy, legal, security or ministry reasons. JCS cannot remove the underlying validated public-ledger transaction.
10. Private Capsule, encrypted material, and high-risk communications
The Private Capsule is an experimental browser-local encryption workflow. It does not create guaranteed anonymity, guaranteed delivery, a protected emergency channel, attorney-client privilege, clergy privilege, medical confidentiality or protection from malware, a compromised device, hostile extensions, physical seizure, coercion or traffic analysis.
- Keep transport ciphertext and recovery key separate when safety requires it.
- Do not place escape plans, safe-house addresses, exact current location, identity documents, wallet secrets or vulnerable third-party identities into a public NFT or XRPL memo.
- Minting an optional neutral receipt associates the submitting wallet with that public receipt event; do not mint it if wallet linkage itself is dangerous.
- JCS does not maintain a universal recovery key or hidden decryption backdoor and may be unable to recover lost Private Capsule material.
11. Prayer Map, public cohorts, and location limitations
A prayer-focus country or region identifies what a prayer concerns; it is not proof of where the signer lives, travels, worships or is physically located. JCS does not treat wallet addresses, IP addresses, XRPL endpoints, relay paths, browser data or prayer-focus labels as reliable person-location evidence.
Thresholded cohort display is a privacy mechanism, not a guarantee against re-identification. Users and third parties must not use JCS to dox, track, triangulate, stalk or infer the physical location of believers.
12. No investment, legal, tax, medical, mental-health, security, emergency or pastoral advice
JCS content, code, metrics, prayers, testimony, Scripture references, roadmaps, risk notices, security guidance and third-party links are informational, religious, educational or technical. They are not personalized investment, legal, tax, accounting, medical, mental-health, emergency, law-enforcement, evacuation, cybersecurity-consulting or pastoral advice.
JCS does not promise a miracle, answered prayer, healing, spiritual standing, salvation, legal outcome, safety outcome, financial result, feature delivery or adoption event. Seek appropriate qualified assistance for matters that require it.
13. Prohibited conduct
Wallet/security abuse
No phishing, credential theft, malicious payloads, unauthorized wallet access, seed requests, malware, denial of service or exploitation outside the Security Policy.
Fraud/market abuse
No wash trading, deceptive guarantees, exploit-based trading, market manipulation, false listings, impersonation or fabricated endorsements.
Human harm
No threats, stalking, doxxing, exploitation, coercion, extortion, unlawful discrimination, targeted harassment or publication of dangerous identifying information.
Illegal use
No money laundering, sanctions evasion, terrorist financing, stolen property, prohibited fundraising or other unlawful activity.
Religious coercion
No using prayer, Scripture, crisis, ministry status or spiritual claims to force trading, donations, disclosure, group participation or personal submission.
Automation abuse
No scraping, bots, polling, AI agents or automated requests that violate robots/discovery policy, the proprietary LICENSE, third-party terms, rate limits or system availability.
14. Network fees, prices, taxes, donations and recordkeeping
XRPL transactions may involve network fees, XRP, token amounts, spreads, slippage, AMM fees or third-party charges. Review the final wallet request. JCS does not control network fees or third-party pricing.
A token purchase, swap, NFT mint, trustline, registry payment, platform fee or other ledger amount is not automatically a charitable donation. You are responsible for your own taxes, valuation, gains/losses, reporting, recordkeeping and professional advice.
15. Third-party services, infrastructure and external content
JCS may interoperate with Xaman, XRPL nodes/validators, explorers, Sologenic, XPMarket, Bithomp, GitHub, hosting providers, DNS/certificate providers, market-data services, media hosts, email/social platforms and other independent services. They are not controlled by JCS.
JCS does not guarantee their accuracy, legality, timeliness, security, privacy, uptime, custody, fees, moderation, transaction handling, compatibility or continued availability. A reference or integration does not imply endorsement, partnership, agency, sponsorship, certification or shared control.
16. AI systems, automation, generated output, and machine discovery
Machine-readable manifests, robots directives, structured data, APIs, public HTML and AI-oriented discovery files improve discoverability; they do not grant intellectual-property permission beyond the repository LICENSE and applicable law.
AI-generated summaries, code suggestions, translations, classifications or automated-agent actions can be incomplete or wrong. You are responsible for independently reviewing any AI or automated output before using it for transactions, legal decisions, security decisions, publication or downstream software.
Unauthorized model training, embeddings, datasets, derivative product development or other reuse of proprietary JCS source may be restricted by the repository LICENSE even when a crawler can technically access the material.
17. Intellectual property, branding, and repository LICENSE
Unless otherwise stated, JCS original source, page designs, workflows, documentation, branding, graphics, project text, machine-readable descriptors and other covered materials are proprietary and protected to the extent provided by law. Public visibility does not make the repository open source, free software, Creative Commons, public domain or a general noncommercial license.
The complete repository LICENSE controls copying, modification, redistribution, deployment, white-labeling, derivative works, AI training and other source/content reuse. These Terms do not broaden that grant.
Third-party libraries, Scripture translations, public-domain media, service marks and other independently owned material remain subject to their own rights and licenses.
18. Forks, mirrors, modifications, augmentations, wrappers and downstream use
A fork, mirror, modified source tree, AI-generated alteration, injected script, browser extension, wrapper, self-hosted deployment, derivative NFT, cloned metadata file, third-party xApp, bot, autonomous agent, integration, repackaged application or any other augmented version is not the official JCS service merely because it contains JCS code, text, branding, identifiers or ideas.
To the maximum extent permitted by law, JCS and the Covered Parties have no responsibility or liability for the design, operation, security, transactions, statements, losses, legal compliance, privacy practices, downstream data use or other consequences of a modified, augmented, mirrored, repackaged or third-party version that JCS does not operate and expressly control.
Modification or downstream use does not create a JCS warranty, support obligation, maintenance duty, fiduciary duty, agency, partnership, endorsement, certification, custody arrangement or assumption of liability. Security assumptions and validations for the official release may no longer apply after any alteration.
Nothing in this section grants permission to create such a version. Permission is governed solely by the repository LICENSE and applicable law. Even an express copyright or oversight permission is permission to use covered material, not a warranty, certification, support commitment, endorsement or assumption of responsibility for the downstream implementation unless JCS separately agrees in a signed writing. Unauthorized reuse may itself violate JCS rights while still remaining entirely at the downstream actor’s risk.
19. Third-party, public-domain, statutory and public-ledger rights
JCS claims no ownership merely because third-party or public-domain material is displayed or referenced through JCS. Public XRPL facts remain subject to the XRP Ledger protocol and applicable law. Statutory rights, fair use, compulsory legal process and other rights that exist independently of the JCS LICENSE remain governed by law rather than these Terms.
20. Availability, experimental features, changes and no maintenance promise
JCS may add, modify, pause, repair, restrict, replace, deprecate or discontinue any controlled page, feature, metric, data source, media source, integration or experimental workflow at any time. Features labeled experimental, beta, preview, local-first or planned may fail, change substantially or never reach production.
JCS does not undertake a general duty to preserve backwards compatibility, support an old browser, maintain a third-party integration, restore a local draft, provide technical support, keep a market liquid or continue a particular feature indefinitely.
21. Security responsibilities and vulnerability reporting
No website, wallet, network, browser, email system, blockchain, encryption implementation or device is guaranteed secure. You must use current software, review Xaman requests, protect credentials, avoid suspicious links and stop if a request differs from your intent.
Security testing is governed by the current JCS Security Policy. These Terms do not authorize testing of third-party systems or activity outside that policy. If you discover a vulnerability, use the published security contact and avoid exposing real users or persecuted believers.
22. Privacy, religious information, legal process and compelled disclosure
Data handling is governed by the current Privacy Policy, including its special treatment of religious-expression data, persecuted-believer safety, public/private separation and legal-process protocol.
JCS may preserve or disclose information when required by valid binding law or legal process. Where legally permitted, JCS intends to verify authority, narrow overbroad demands, disclose only responsive information actually in its possession/custody/control, preserve available objections, and avoid creating new surveillance, location-inference or decryption capabilities merely because a request is possible.
Nothing in these Terms promises that any communication is privileged or immune from lawful process.
23. Disclaimer of warranties
To the maximum extent permitted by applicable law, JCS, its official pages, content, code, transaction builders, metrics, risk indicators, prayer/testimony interfaces, NFTs, Private Capsule functions, maps, media, machine-readable files, documentation and links are provided “AS IS,” “WITH ALL FAULTS,” and “AS AVAILABLE.”
To the maximum extent permitted by law, JCS disclaims all express, implied and statutory warranties not expressly stated in a separately executed written agreement, including merchantability, fitness for a particular purpose, title, non-infringement, quiet enjoyment, accuracy, completeness, security, availability, compatibility and error-free operation.
JCS does not warrant that a transaction will validate, a quote will remain available, code contains no defect, encryption cannot be compromised, an NFT or hash proves a legal fact, a third party will behave properly, a prayer will receive a particular answer, or any project objective will occur.
Some laws do not permit some exclusions. Any exclusion is limited to the maximum lawful extent.
24. Knowing assumption of risk and responsibility for your choices
By choosing to use interactive JCS features, you knowingly accept the inherent risks of public blockchains, self-custody, irreversible transactions, wallet/device compromise, token volatility, liquidity limitations, public religious association, third-party outages, software defects, regulatory change and experimental technology.
To the maximum extent permitted by law, you assume responsibility for risks arising from your wallet, device, transaction approvals, public disclosures, content, trading choices, configuration, security practices, jurisdiction, use of experimental features and use of any modified or augmented version.
This assumption-of-risk clause does not waive rights or claims that applicable law does not permit a user to waive.
25. Limitation of liability
To the maximum extent permitted by law, JCS and its operators, maintainers, developers, contributors, volunteers, ministry participants, content providers, licensors, affiliates, successors and agents (“Covered Parties”) will not be liable for indirect, incidental, special, consequential, exemplary or punitive damages; lost profits, revenue, opportunity, data, goodwill or business; wallet, token, NFT or key loss; public-disclosure harm; price movement, slippage or liquidity loss; phishing, malware or device compromise; third-party service failure; network failure; user error; loss arising from an unauthorized fork or modified/augmented version; or inability to access or use JCS.
Where liability cannot lawfully be excluded, the aggregate liability of the Covered Parties arising from the JCS-controlled service will, to the maximum extent permitted by law, not exceed the greater of (a) direct fees you actually paid to JCS for the specific JCS-controlled service giving rise to the claim during the previous twelve months, excluding network fees and amounts transmitted to users, counterparties, AMMs, validators or third parties, or (b) US $100.
The limitations apply regardless of legal theory and even if a Covered Party was advised that loss was possible, but do not exclude or limit liability, remedies or statutory rights to the extent applicable law prohibits exclusion or limitation, including any non-waivable liability for fraud, willful misconduct, gross negligence, certain personal injury or other protected claims where applicable.
26. Indemnification
To the extent permitted by law, you agree to defend, indemnify and hold harmless the Covered Parties from third-party claims, liabilities, judgments, penalties, damages and reasonable costs arising from your violation of these Terms or law; your wallet use or authorized transaction; your content or public disclosure; your infringement of another person’s rights; your fraud, impersonation or security abuse; or your operation, distribution or use of an unauthorized or non-JCS-controlled modified/augmented version.
JCS may control the defense of a covered claim where legally appropriate. You may not settle a claim imposing an admission, payment, obligation or restriction on JCS without written consent.
27. Force majeure and events outside reasonable control
To the maximum extent permitted by law, JCS is not responsible for delay, outage, nonperformance or loss caused by events outside its reasonable control, including blockchain/network events, validator/node failure, third-party API or wallet outages, DNS/CDN/hosting failures, Internet disruption, cyberattack, government action, legal restrictions, sanctions, natural disaster, war, civil disorder, labor disruption, utility failure or similar events.
28. Informal dispute resolution, governing law and forum
Before filing a non-emergency claim involving a JCS-controlled page, send written notice to jesuschristsaves@gmail.com describing the claim, relevant page/transaction, date, facts and requested remedy, and allow thirty days for a good-faith attempt to resolve it.
This version intentionally does not invent a legal entity, principal place of business, mandatory arbitration clause, class-action waiver or exclusive forum that has not been formally established. Governing law, jurisdiction and venue therefore remain determined by applicable mandatory law, actual operator/entity facts and any separately valid written agreement.
Nothing prevents emergency injunctive relief, reporting crime or fraud, responding to legal process, exercising non-waivable consumer rights or using an available governmental complaint process.
29. Suspension, termination and survival
JCS may block, restrict, suspend or terminate access to JCS-controlled interactive services where reasonably necessary for security, abuse prevention, legal compliance, maintenance or protection of users and the ministry. Such action does not control the decentralized XRP Ledger or erase public transactions.
Provisions concerning public-ledger permanence, user content, intellectual property, modified/downstream use, disclaimers, assumption of risk, liability, indemnification, disputes, legal process and other provisions that by nature should survive continue after access ends.
30. General contractual terms
- Entire site-use agreement: These Terms and incorporated Privacy/Security/License boundaries are the site-use framework unless a separate valid written agreement expressly controls a subject.
- Order of documents: the Privacy Policy controls personal-information handling; the Security Policy controls vulnerability-research authorization; the repository LICENSE controls copying/modification/reuse rights; these Terms control website/application use and risk allocation.
- Severability / reformation: an invalid or unenforceable provision will be limited or reformed to the minimum extent necessary where law permits, and remaining provisions continue.
- No waiver: failure to enforce a provision once is not a permanent waiver.
- No third-party beneficiaries: except where law requires otherwise, these Terms do not create enforcement rights for unrelated third parties.
- No implied duties: roadmaps, support replies, code comments, AI output, documentation, examples and public statements do not create fiduciary, maintenance, warranty, advisory or service-level duties unless a separate signed agreement expressly does so.
- Assignment: you may not assign these Terms without consent. JCS responsibilities may be assigned as part of a lawful succession or restructuring.
- Electronic records: electronic notices, records and acknowledgments may be used where legally permitted.
- Prospective updates: revised Terms apply prospectively when posted with a new effective date, subject to mandatory law and any additional assent required for material changes.
31. Contact
Email JCSTerms, support or dispute notice · never send wallet secretsOfficial JCS account on X@JesusCS_token · do not post private legal/security material publicly
Never send: seed phrase, recovery phrase, private key, device passcode, unnecessary government identification, Private Capsule recovery key or another person’s sensitive information.
32. Controlling documents and machine-readable terms boundary
PrivacyReligious safety, personal data and legal processSecurityVulnerability reporting and research boundaryRepository LICENSECopying, modification, redistribution and AI reuse rightsAI ManifestMachine-readable project discovery; not a source license
Machine-readable Terms contract
/jcs-terms-service-boundary-v1.json\nSchema: jcs-terms-service-boundary-v1\nRelease: 3.0.0Legal-review boundary: this document is a project Terms draft and operating specification, not a legal opinion. Its protections depend on applicable law, contract formation, operator/entity facts and actual system behavior. Qualified counsel should review it before JCS relies on it as a final legal instrument.
“Moreover it is required in stewards, that a man be found faithful.”
— 1 Corinthians 4:2, King James Version
— 1 Corinthians 4:2, King James Version