Privacy Policy

This Privacy Policy explains how Apex Software Solution, operating Kershi, collects, uses, shares, stores, and protects information when you use our website, dashboard, mobile application, developer API, SDKs, support channels, documentation, and related services.

Kershi handles transaction verification workflows for businesses and developers. That means privacy, security, auditability, and responsible data handling are core product requirements, not optional features.

Our Privacy Commitments

We do not sell or rent personal information.

We use service data to operate, secure, support, and improve Kershi.

We do not voluntarily disclose customer data to government offices without valid legal process.

We perform recurring security checks, access reviews, dependency reviews, and operational monitoring.

1. Information We Collect

We collect only the information needed to provide, secure, maintain, support, and improve Kershi. The exact information depends on how you use the website, dashboard, mobile application, developer API, SDKs, support channels, documentation, and related services.

1.1 Account And Contact Information

When you create an account, join a team, request onboarding, contact support, or manage billing, we may collect account and business contact details.

Name, business name, email address, and phone number.

Login credentials, authentication details, team membership, and role information.

Support messages, onboarding notes, enterprise sales details, billing records, plan information, and subscription status.

1.2 Verification Request Data

When you use Kershi to verify a transaction, we process the fields needed to submit, track, resolve, and audit that verification request. Required fields vary by bank, wallet, provider, and verification route.

Transaction reference numbers, receipt numbers, account suffixes, phone numbers, selected bank, wallet, or provider, and provider-specific request fields.

Transaction metadata, request history, verification status, request IDs, processing status, queued and completed timestamps, and verification logs.

Provider-returned details where available, such as amount, currency, timestamp, sender or receiver names, sender or receiver account details, reference numbers, and status messages.

1.3 API, Dashboard, And Usage Data

For API and dashboard users, we collect operational records that help authenticate requests, enforce usage limits, support teams, troubleshoot errors, and make the product more reliable.

API key metadata, key permissions, API usage counts, credit usage, quotas, rate limits, request timestamps, and endpoint activity.

Error codes, webhook delivery attempts, dashboard activity, verification history, exports, reports, analytics, and team activity records.

Configuration data such as webhook URLs, integration settings, team invitations, and permission changes.

1.4 Device, Technical, And Log Data

We collect technical records to keep the service reliable, detect abuse, investigate incidents, and improve user experience across the web, API, and mobile app.

IP address, browser type, device type, operating system, app version, referring URLs, pages viewed, session events, crash logs, security logs, timestamps, authentication events, and request identifiers.

Performance, uptime, latency, queue health, provider availability, and error telemetry used for reliability and security monitoring.

1.5 Cookies And Local Storage

We may use cookies, local storage, and similar technologies for authentication, security, session management, saved preferences, analytics, service improvement, and abuse prevention.

1.6 Communications

If you contact us, request pricing, submit a form, or communicate through support channels, we may collect your name, email address, phone number, business details, message contents, attachments, and related support context.

2. How We Use Information

We use information for legitimate product, security, support, compliance, and reliability purposes. We do not use verification data to sell advertising profiles, and we do not sell personal information.

Provide, operate, maintain, monitor, and improve Kershi.

Process verification requests and return results, status updates, history, reports, and exports.

Authenticate users and API requests, manage accounts and teams, enforce permissions, and secure API keys.

Manage plans, credits, quotas, subscriptions, billing records, invoices, and account operations.

Send webhooks, service notifications, support responses, security alerts, and operational messages.

Detect, prevent, investigate, and respond to fraud, abuse, misuse, unauthorized access, suspicious verification activity, and security incidents.

Measure uptime, latency, queue health, provider performance, reliability, and product quality.

Improve user experience by analyzing aggregated or de-identified usage patterns, reducing errors, improving flows, and making the dashboard, mobile app, API, SDKs, documentation, and support experience easier to use.

Comply with legal, tax, accounting, audit, contractual, and recordkeeping obligations.

Enforce our Terms of Service and protect Kershi, customers, users, partners, and the public.

3. How We Share Information

We do not sell or rent personal information. We share information only where necessary to provide the service, follow your instructions, protect the service, or comply with legally binding obligations.

3.1 Banks, Wallets, Payment Partners, And Upstream Providers

We may share verification inputs and related metadata with supported banks, wallets, payment providers, or upstream systems when needed to process a verification request, check a transaction, return a result, or troubleshoot a provider-side issue.

3.2 Service Providers

We may use trusted vendors that help us operate Kershi, including hosting, infrastructure, analytics, monitoring, support, email or SMS delivery, billing, security tooling, app distribution, and operational systems.

These providers may process information only as needed to provide services to us and are expected to follow appropriate confidentiality, access control, and security restrictions.

3.3 Legal, Safety, And Government Requests

We do not voluntarily provide customer or user data to any government office, agency, or public authority for unrelated monitoring, profiling, or general access.

We may disclose information only when we believe disclosure is required by valid legal process, such as a court order, warrant, subpoena, or comparable legally binding request; or when necessary to protect rights, safety, security, investigate fraud or abuse, or enforce our agreements. Where legally allowed and appropriate, we review requests before disclosure and seek to limit disclosure to the information required.

3.4 Business Transfers

If Kershi is involved in a merger, acquisition, financing, reorganization, sale of assets, or similar transaction, information may be transferred as part of that transaction subject to appropriate continuity and confidentiality protections.

3.5 With Your Direction

We may share information when you direct us to do so, including when you configure webhook URLs, invite team members, export reports, connect integrations, authorize support access, or ask us to assist with an account or verification issue.

4. Data Retention

We retain information for as long as needed to provide Kershi, operate verification workflows, maintain security, support billing and accounting, resolve disputes, enforce agreements, prevent fraud, improve reliability, and comply with legal obligations.

Verification logs, API activity, security records, webhook logs, support records, billing records, and audit records may be retained for operational, fraud-prevention, compliance, and reliability purposes.

When information is no longer needed, we may delete it, anonymize it, de-identify it, aggregate it, or restrict access according to our retention practices and legal requirements.

5. Security

Kershi is built for transaction verification workflows, so security is treated as a core operating requirement. We use administrative, technical, and organizational safeguards designed to protect information from unauthorized access, loss, misuse, alteration, and disclosure.

Encrypted transport for service communication where applicable.

Authentication, session controls, role-based access, permission-scoped API keys, and key rotation or revocation workflows.

Infrastructure monitoring, security logging, request identifiers, rate limits, abuse detection, and operational alerts.

Internal access restrictions, least-privilege practices, and review of sensitive operational access.

Recurring security reviews, dependency checks, configuration reviews, incident review practices, and reliability checks across critical request paths.

Operational metrics and logs that help detect unusual behavior, provider failures, uptime regressions, and unauthorized access attempts.

No internet service, API, dashboard, mobile application, or storage system can be guaranteed to be completely secure. You are responsible for protecting your account, devices, team access, API keys, webhook endpoints, and integrations.

6. Your Responsibilities

Because Kershi processes transaction and verification-related data, customers and API users must use the service responsibly and lawfully.

Obtain any required authorization before submitting verification data.

Provide legally required notices to customers, staff, end users, or affected parties.

Use verification results responsibly and avoid using them for unrelated profiling, harassment, or unlawful decisions.

Limit dashboard, mobile app, and API access to authorized staff.

Protect login credentials, API keys, webhook secrets, devices, and integration endpoints.

Configure secure webhook URLs and review integrations that receive verification results.

Comply with applicable privacy, banking, payment, consumer protection, accounting, tax, employment, and data protection laws.

7. Your Choices And Rights

Depending on applicable law and your relationship with Kershi, you may have rights regarding personal information we control.

Request access to personal information.

Request correction of inaccurate information.

Request deletion of information.

Object to or restrict certain processing.

Request a copy of certain information.

Withdraw consent where processing is based on consent.

These rights may be limited by legal, security, fraud-prevention, contractual, accounting, tax, audit, and recordkeeping requirements. To make a privacy request, contact us using the official support details on this page.

8. Cookies And Analytics Choices

You may be able to control cookies through your browser settings. Blocking some cookies may affect login, dashboard functionality, API management, security features, saved preferences, analytics quality, or service performance.

Where analytics are used, they are intended to understand product reliability, user experience, and service quality. We do not use analytics to sell personal information.

9. Children's Privacy

Kershi is intended for businesses, developers, operational teams, and authorized users. It is not directed to children. We do not knowingly collect personal information from children. If you believe a child has provided personal information to us, contact us so we can review and take appropriate action.

10. International Data Processing

Your information may be processed in Ethiopia or in other countries where we, our infrastructure providers, or service providers operate. Data protection laws in those countries may differ from the laws where you are located.

Where required, we use appropriate safeguards for cross-border processing and expect service providers to process information only for authorized service purposes.

11. Third-Party Links And Services

Kershi may link to third-party websites, app stores, SDK repositories, banks, wallets, payment providers, documentation, or integrations. We are not responsible for the privacy practices, security, content, or availability of third-party services.

12. Changes To This Privacy Policy

We may update this Privacy Policy from time to time. When we make changes, we will update the effective date or provide notice where appropriate. Continued use of Kershi after the updated policy takes effect means you acknowledge the updated policy.

13. Contact Us

For privacy questions, data requests, or security-related privacy concerns, contact Kershi through the official support channel below.

Kershi

Email: support@kershi.pro.et

Website: Kershi

Privacy questions are reviewed in context so we can confirm identity, account authority, and any legal or security restrictions before responding.