Skip to content
InnovappSoft
KeyCard BBMThe ecosystem created by InnovappSoft.Our storyLaunch, metrics and platform presence.App StoreDownload KeyCard BBM for iOS.Google PlayDownload KeyCard BBM for Android.
Discover our products
Portal UsuarioYour SIM, data and minutes in one Android app.
Download on Google Play
Developer portalConnect your platform to our API.DocumentationIntegrate the catalog and purchases.Request accessIntegrate our catalog and access the commission program.
How it works
Telegram communityMeet other users and our team.WhatsApp communityA place to stay connected.Official channelsProduct updates and announcements.
Follow InnovappSoft
Help centerFind our official support channels.Frequently asked questionsLearn about our company and how to partner.Contact usOur team is here to help.
Policies and transparency
KeyCard BBM
Legal

Account Security Policy.

Available security methods and optional 2FA, email reset and shared responsibilities under applicable law.

00 Published version

Updated: 20/11/2026

Version 2026-11-20.1 · Effective: 20/11/2026. Available security methods and optional 2FA, email reset and shared responsibilities under applicable law.

Contact
  1. 01

    General information

    This Account Security Policy establishes user responsibilities and the measures INNOVAPPSOFT LLC may apply to protect accounts, credentials, devices, sessions, purchases, KeyCoin balance, and related services.

  2. 02

    User responsibility

    Users are responsible for keeping their account, password, device, sessions, authentication methods, and any access information secure.

    All activity performed from an account may be considered the responsibility of the account holder, including purchases, KeyCoin balance use, settings changes, and actions performed from linked devices or sessions.

    Users must notify through platform-enabled channels if they suspect unauthorized access, device loss, credential theft, unknown activity, or security compromise.

  3. 03

    Credentials and access

    Users must use secure credentials, avoid sharing passwords, avoid reusing compromised keys, and not allow third parties to access their account.

    Selling, lending, renting, assigning, transferring, or allowing another person to use an account is prohibited.

    Users must protect their credentials and devices, avoid sharing access and promptly report suspected compromise. Losses attributable to a user’s failure to take reasonable precautions will be assessed according to the evidence and applicable law. Choosing not to enable optional 2FA can increase account risk; it does not exclude INNOVAPPSOFT LLC’s own security, privacy, breach-notification or other non-waivable legal duties.

  4. 04

    Devices and sessions

    The platform may collect and analyze technical information from devices, sessions, IPs, operating system, app version, internal identifiers, and activity to protect accounts and prevent fraud.

    We may limit, close, invalidate, or review sessions when suspicious activity, unusual device changes, access from inconsistent locations, risky IPs, or abuse-related patterns are detected.

    Users must close unrecognized sessions and keep devices protected with lock screens, updates, trusted software, and reasonable security measures.

  5. 05

    Authentication, KYC, and additional controls

    We may require additional authentication, 2FA verification, security confirmations, device validations, KYC verification, or additional documentation before allowing certain operations.

    These measures may apply to purchases, sensitive changes, information changes, new access, account recovery, or risk activity.

    Refusal to complete security or KYC controls may result in restrictions, temporary blocking, operation rejection, or account suspension.

  6. 06

    Suspicious access

    Access may be considered suspicious when there is an unusual change in location, device, IP, behavior, connection method, browsing pattern, or attempt to evade controls.

    The use of VPNs, proxies, Tor, anonymous networks, data center IPs, or IP-hiding tools is prohibited and may trigger restrictions, blocks, manual review, or suspension.

    Repeated login attempts, frequent session changes, automated activity, abnormal technical patterns, or fraud-related access may also be treated as risk signals.

  7. 07

    Sensitive operations

    Certain operations may be considered sensitive, including digital product purchases, KeyCoin balance use, top-ups, account changes, KYC verification, and security modifications.

    INNOVAPPSOFT LLC may pause, block, or request additional confirmation before processing sensitive operations when risk, unusual activity, dispute, violation, or fraud indicators exist.

    Approval of a sensitive operation may depend on identity verification, internal review, AML/CTF controls, external provider availability, or technical validations.

  8. 08

    Account recovery

    Account recovery may require additional validations to confirm the identity of the account holder.

    We may request account information, KYC verification, device checks, activity history, internal confirmations, or any other element necessary to protect the user and the ecosystem.

    If ownership cannot be sufficiently verified, INNOVAPPSOFT LLC may reject or limit the recovery process.

  9. 09

    Unauthorized use

    Users must review their account and report unknown activity as soon as it is detected.

    INNOVAPPSOFT LLC may review unauthorized use cases but does not guarantee reversal of operations, balance recovery, or favorable resolution when an operation has already been completed, delivered, or processed by third parties.

    Responsibility may fall on the user when unauthorized access results from shared credentials, phishing, negligence, malware, unsafe devices, or failure to follow basic security measures.

  10. 10

    Preventive blocking

    INNOVAPPSOFT LLC may apply preventive blocks, temporary restrictions, balance holds, session closure, token invalidation, or feature limitations to protect accounts, balances, and operations.

    These measures may be applied without prior notice when there is risk of fraud, unauthorized access, suspicious activity, policy violation, investigation, chargeback, AML/CTF review, or legal requirement.

    A preventive block does not confirm fraud; it is a security measure while a review is completed.

  11. 11

    Updates to this policy

    INNOVAPPSOFT LLC may modify this Account Security Policy at any time to adapt it to technical, operational, legal, regulatory, security, fraud, or compliance changes.

    Changes take effect once published or from the moment indicated by the platform.

    Material changes that require renewed acceptance will be identified by version, summary and effective date. We will request an affirmative confirmation in the app and keep a record of the specific version. Publication, an email or continued use alone does not create that record.

  12. 12

    Optional two-step verification and account protection

    Two-step verification is optional. Each user chooses which available methods to configure or whether to use the account without a second factor. We strongly recommend enabling at least one available method, using a unique password and reviewing active sessions. Do not share authentication codes, recovery information or access credentials.

    Depending on the app version, device and availability, the platform offers email codes, an authenticator application, linked Telegram, a security PIN and Passkeys. Passkeys are an access method and a PIN alone does not provide the same protection as an independent authenticator. WhatsApp codes are not available until that integration is configured and enabled. The app and its current settings show the methods actually available.

    Email-based 2FA previously configured was reset and disabled because of delivery problems. Other selected methods remain configured. Users may voluntarily reconfigure an available method after confirming access to it. Support may reset a method only through the authorized recovery process after verifying account ownership. Primary credentials and operational identity checks remain applicable.

    Users must protect their credentials and devices, avoid sharing access and promptly report suspected compromise. Losses attributable to a user’s failure to take reasonable precautions will be assessed according to the evidence and applicable law. Choosing not to enable optional 2FA can increase account risk; it does not exclude INNOVAPPSOFT LLC’s own security, privacy, breach-notification or other non-waivable legal duties.

  13. 13

    Version, effective date and explicit confirmation

    Material changes that require renewed acceptance will be identified by version, summary and effective date. We will request an affirmative confirmation in the app and keep a record of the specific version. Publication, an email or continued use alone does not create that record.

    The page displays its publication and effective dates, version and change summary. A version-specific link preserves the exact published text. Newly published documents do not retroactively change the record of an earlier confirmation. Required confirmation may restrict access to ordinary app functions, while account recovery, security, support and the exercise of privacy rights remain available.

InnovappSoft
KeyCard BBMOur storyPortal UsuarioDevelopersDocumentationFAQCommunitySupportAbout us
© 2026 INNOVAPPSOFT LLC
Terms and conditionsPrivacyCookiesAcceptable useAccount securityComplianceAML / CTFRefundsSuspension and holdsProvidersKeyCoin policy
Back to top

KeyCoin (KC) is an internal purchase unit exclusive to KeyStore within the KeyCard BBM ecosystem. KeyCoin is not legal tender, is not fiat money, is not a bank deposit, does not generate interest, is not insured by any financial entity and is not accepted by third parties outside the ecosystem. Balances are not insured by the FDIC or any public agency, and are not issued or backed by the United States Government.