Privacy Policy

Service and contact

This policy covers Alisha AI Business Rescue at alishabdigitals.com, its API and account pages at api.alishabdigitals.com, and its connected ChatGPT business tools. The service is operated by 2KS Technologies Inc. Contact info@2kstechnologies.com for privacy questions or requests.

Information we handle

GitHub sign in supplies your GitHub account ID and login name. Alisha stores customer account records, trial dates, plan and access status, project usage, and applicable Stripe customer, subscription and lifetime purchase references.

Business tools receive the process information you submit, including business name, industry, goals and optional details such as workforce size, revenue and current systems. Completed assessment results can contain that business information. Alisha stores the result, project ID, completion time and a hash of assessment inputs for project counting and repeat requests. An input hash does not make stored assessment content anonymous.

Authentication records include hashed access tokens and website session identifiers, expiry times, authorization codes, approved OAuth clients and callbacks, PKCE challenges, and permitted scopes and resources. Purchase records include Checkout references, accepted purchase terms and consent times. Stripe event references support payment synchronization and duplicate-event prevention.

Verified deletion requests store the customer association, immutable GitHub account ID, selected scope, support reference and verification time. Support messages contain the information you choose to email. Hosting and application logs may contain technical request and error information for operation, security and troubleshooting.

Optional Alisha email updates

The optional Alisha updates signup collects your email address, campaign identifier, consent wording and version, signup time, status and unsubscribe time. It is separate from account access and billing. New addresses remain pending verification before campaign delivery. Submitting an existing address does not cancel an earlier unsubscribe request.

2KS Technologies Inc. uses the list for Alisha product news, practical business automation tips and offers. No advertising pixels or third party marketing platform is configured by this signup. You can unsubscribe without signing in or contact info@2kstechnologies.com. Signup records currently have no automatic deletion schedule; email support to request access, correction or deletion. Suppression records may need to remain so we can honor an opt out.

How information is used

Alisha uses this information to sign you in, provide business planning outputs, apply trial and paid access rules, count completed assessments, reuse completed results, synchronize billing, investigate errors and handle support and privacy requests. Do not submit passwords, authentication codes, API keys, payment card details, named patient records or other restricted information to business tools. Describe sensitive processes with anonymous or sample information.

Connected providers and access

The current integrations are GitHub for sign in, Stripe for Checkout, subscriptions and Billing Portal, Hostinger for hosting, and OpenAI for the ChatGPT environment in which you use the connection. Information you provide in ChatGPT is also handled by OpenAI under its own policies. Authorized service operators handle support and service administration.

Payment card information is entered on Stripe pages rather than collected by Alisha business tools. The current Alisha frontend uses first party scripts and essential account cookies; it does not include configured advertising pixels or analytics trackers. Provider services have their own privacy, processing and retention practices. This policy does not promise that all provider processing or storage occurs in the United States.

Cookies and security

The account website uses Secure, HttpOnly, SameSite cookies for sign in and account sessions. A website session expires after eight hours; signing out removes the current session. Expired session records are removed during a later successful website login.

The implementation uses HTTPS URLs, PKCE for OAuth, signed authorization state, account ownership checks, hashed authentication tokens, expiring sessions and signed Stripe webhook verification. These controls reduce risk but do not guarantee security or establish a compliance certification.

Assessment retention

Completed assessment business content is retained for 12 calendar months in the active database. A daily cleanup removes expired content, and a request for an expired result also removes it immediately. A minimal record containing the customer association, project ID, input hash and completion time remains to prevent a repeat request from being counted as a new project. Expired results cannot be retrieved or rebuilt through a retry.

Other retention and backups

Access tokens expire after one hour. Authorization codes expire after five minutes; expired codes are removed during token processing and scheduled cleanup. Scheduled cleanup removes access token records after they have been expired or revoked for more than 30 days. Access expiry is different from deletion of a stored record.

Customer account records, billing and consent records, minimal project records, support request records and support messages do not currently have a uniform automatic deletion period. These records remain subject to the manual request and review process below. This policy does not promise their removal on a fixed schedule.

Assessment cleanup and account requests do not automatically erase provider backups or hosting logs. The configured Hostinger database backup retention period has not yet been verified. Copies may remain in provider backups after removal from the active database. Ask support about the scope and limitations of a specific request; no numerical backup deletion deadline is promised here.

Access, correction and deletion requests

Email info@2kstechnologies.com to request access, correction, assessment removal or account closure. For deletion, use the subject “Alisha account data deletion request” and include your GitHub login and requested scope. You can sign in to your Alisha account and generate a verified support request reference to include in the email.

Support verifies ownership and reviews the requested scope before acting. Email submission or generation of a reference does not itself delete data, cancel a subscription or authorize someone to access an account. Removal is a manual support process. Records that need to remain for billing synchronization, security, transaction evidence or applicable retention obligations require a scope review. Support will explain any retained categories and backup limitations for the request.

If you request account closure and have a recurring subscription, also address renewal through Billing Portal or the support cancellation process. Data removal and subscription cancellation are separate actions. A request does not create a refund entitlement. This policy does not state a fixed completion deadline; any applicable legal requirements still apply.

Policy updates

Updates to this policy will be posted here with a new version and effective date. Check this page when considering use of the service or making a privacy request. For questions about a change or how your information is handled, contact support.