Optional paid SDK access
Plans & usage
My Credit Signal is operated by 14985354 CANADA INC. Production is CA$19.99 per monthly billing period for 1,000 authorized parse starts; Scale is CA$49.99 for 5,000. The final amount, currency and any applicable tax appear before you confirm payment in Stripe. Each plan covers one developer account, with shared usage across its server keys.
A start is counted when the access API authorizes a new request ID, before local document reading. Reading failures, partial extraction and cancellation after authorization still count. A retry of the same request ID within the same allowance period does not count again. Allowances do not roll over. At the cap, new authorizations stop; there are no automatic overage charges.
Paid windows follow the subscription’s monthly billing dates, shown in your console in UTC. Free Developer uses UTC calendar months. Key rotation and disabling/re-enabling access do not reset usage. Ending a paid plan returns to the Free allowance with that calendar month’s starts retained.
Renewal, cancellation & plan changes
Paid subscriptions renew monthly until canceled. Use Developer Console → Manage billing to cancel renewal before the next billing date. A cancellation at period end preserves paid access through the paid term, unless a refund, dispute, suspension or other payment issue applies. Disabling API access or revoking keys does not cancel billing.
For the initial release, changing between paid tiers requires ending the current term and selecting the new tier afterward. No mid-period prorated upgrade or downgrade is offered. A failed payment does not grant a new paid allowance. Your free consumer analyzer and calculators remain independent of SDK payments.
Production-use permission
While a paid subscription is active and its current term is paid, My Credit Signal grants the account holder non-exclusive permission to use, adapt and self-host its SDK as part of the holder’s application and serve necessary browser assets to that application’s users, within the account allowance. Preserve copyright and third-party notices. This does not permit selling or sublicensing the parser as a competing standalone service, sharing server credentials between unrelated businesses or bypassing access limits. Third-party components retain their own licenses.
When paid access ends, the free development/evaluation license remains available within its scope; it does not provide continuing paid production rights. Enterprise/offline use requires a separate written agreement. There is no uptime, response-time, custom development or priority-support commitment in these volume plans.
Review and limitations
Extraction is partial and requires human review. Supported scope is conservative English-label Equifax, Experian and TransUnion reports, one bureau at a time, as documented in the quickstart. Do not rely on output alone for underwriting or credit decisions. The SDK is provided as-is without an accuracy or fitness guarantee; local processing is not a compliance certification or exemption. You remain responsible for lawful document access, consent, your application’s security and any downstream use or storage.
Billing questions & failed starts
For duplicate charges, a My Credit Signal authorization-service failure or a billing concern, contact us with the developer account email, approximate time and random authorization ID if available. Do not attach a credit report. We review billing corrections, service credits and refunds individually; no automatic refund is promised for unsupported files, local OCR failures or unused allowance. This does not limit rights that applicable law requires.
A refund or payment dispute pauses paid authorizations while the billing issue is reviewed. It does not erase the usage record or cancel renewal by itself. Cancel renewal separately in Manage billing if you do not want the next term.
Data used for billing
Stripe hosts payment entry and may collect billing contact and payment information. My Credit Signal stores developer-account references, Stripe customer/subscription and payment-issue references, subscription state and dates, accepted terms version and time, and usage counts/random request IDs. We do not send credit reports, extracted financial fields, filenames or end-customer identities to Stripe. Card details are not collected by the SDK.
Authorization identifiers follow the 90-day usage-ledger retention; inactive, unreferenced aggregate usage windows and resolved payment-issue records follow the 13-month policy. Active account/subscription references and unresolved billing issues remain while needed to administer access. Stripe transaction records, legal retention obligations and provider backups have separate retention. Contact us for account deletion: billing records must be reviewed first so deleting a login cannot leave an ongoing subscription behind.