Privacy Policy

Several forms and interactive tools on this website are designed for client demonstration purposes:

• Contact Inquiries: When you submit an inquiry via the Contact form (/contact), your entered details (name, contact email, phone number, interested service, package tier, and project requirements) are transmitted over TLS to our NestJS backend on Cloud Run and recorded in Google Cloud Firestore Native mode (asia-south1 Mumbai region). Inquiries submitted by unauthenticated guests are recorded as guest inquiries and are never linked to any customer account simply by email match. Inquiries submitted by signed-in users are linked to their authenticated account UID, allowing them to view progress and reply via their Client Portal. Durable abuse protection uses non-reversible SHA-256 IP hash slices without storing raw IP addresses.
• Account & Dashboard: The login and register pages operate in demonstration mode when live Firebase configuration is unavailable. In demonstration mode, entering sample details creates a temporary in-memory session for UI evaluation without transmitting data to a remote backend. If Firebase Authentication is enabled, sign-in or registration information is sent to Firebase for authentication processing. Depending on the configured Firebase persistence mode, the Firebase SDK may retain authentication state and tokens in browser-managed storage. This application does not intentionally store raw account passwords in its own localStorage or custom session system.
• Direct Order System & Project Scoping: When an authenticated client submits an order via the Direct Order Wizard (/order), project specifications (customer contact, business name, preferred contact method, objective, detailed scope, and budget) are transmitted over TLS to our authenticated NestJS backend on Cloud Run and stored in Google Cloud Firestore Native mode (asia-south1 region). Direct client access to the database is blocked by security rules; all access requires valid Firebase authentication ID tokens.
• Newsletter Notice: The newsletter section displays an informative status notice only and does not collect or transmit email addresses to an external mailing list provider.

We minimize browser-side storage. The application uses standard browser storage for user preferences, authentication persistence where configured, and the specific attribution state disclosed below:

• localStorage.getItem('theme'): Remembers your dark/light appearance preference across visits.
• localStorage.getItem('language'): Remembers your language selection (English or Bengali).
• Client State & Authentication Persistence: In demonstration mode, active UI sessions exist solely in browser memory and are not persisted to disk. If Firebase Authentication is enabled, the Firebase SDK may maintain authentication state and tokens in browser-managed storage (such as IndexedDB or localStorage) according to its configured persistence mode. This application does not store account passwords in its own localStorage or client storage.
• Affiliate Attribution: When the official affiliate program is active and a visitor uses an approved AJ referral link, the browser may store an expiring, server-signed attribution token in localStorage under aj_affiliate_attribution_v1. The token contains approved referral attribution for a later eligible purchase; invalid or expired tokens are discarded. Self-referrals are not eligible.

Third-party advertising is currently disabled. The codebase contains a fail-closed AdSense integration, but it does not load the ad script or request ads unless explicit production activation and consent-readiness gates are enabled.

This website loads certain imagery and static demonstration assets from third-party content distribution networks (including Unsplash at images.unsplash.com).

When your browser retrieves these assets, standard technical request information (such as your IP address and browser user agent) is transmitted to the third-party asset provider as an inherent part of HTTP content delivery.

This website is hosted on Firebase Hosting (Google Cloud Platform). Hosting and third-party providers may process technical request information according to their own services and policies.

This may include standard HTTP request data such as IP addresses, browser headers, referring URLs, timestamps, and requested paths as part of ordinary web traffic delivery, routing, performance optimization, and DDoS mitigation.

Our website may contain links to external websites, developer tools, or documentation. Clicking these links navigates away from our site to third-party domains governed by their own independent privacy notices and terms. AJ IT Solution does not control and assumes no responsibility for the privacy practices or content of external destinations.

The Social Automation SaaS can store workspace configuration, drafts, schedules, publishing targets, connected-account metadata, job history, AI usage and credit ledger records, subscription or credit-purchase records, and audit metadata needed to operate the service.

Meta access tokens used for connected Facebook Pages or Instagram Professional accounts are stored server-side in encrypted form and are not returned to the browser after connection. Disconnecting a Social Automation connection marks it disconnected and deletes the encrypted token stored for that connection.

Source images uploaded for AI generation are stored in private Google Cloud / Firebase Storage paths with short-lived signed access. Generated AI media may be copied into AJ IT Solution-managed private storage so approved media remains available for later scheduling. AI text, image, and video requests may also be sent to the explicitly configured third-party AI provider when the corresponding production feature is enabled.

Social Automation billing can include admin-created subscription plans and AI credit packages. Purchase requests may contain payment method, transaction/reference details, customer notes, package/plan snapshots, review status, and audit records. Customer views mask payment references; authorized administrators may access the information required to review a submitted payment.

For connected-account and account-level deletion instructions, see the Data Deletion Instructions page.

Client Finder Pro stores lead and CRM information that an authenticated workspace user explicitly saves, such as business/contact labels, contact details, source references, notes, tags, CRM stage, follow-up information, outreach drafts, team membership, and usage-meter records. Access is scoped to the relevant Client Finder workspace and role.

When the optional Google Places discovery feature is enabled, a user's search query and optional region/language settings are sent server-side to Google Maps Platform. Returned place information is displayed for review and is not automatically copied into the Client Finder CRM. By default, Client Finder retains only the Google Place ID reference together with labels, notes, or other CRM information entered by the user. Google Maps Platform may process technical request information in accordance with Google's own policies.

The optional Client Finder Quick Capture browser extension does not read current-page metadata merely because its popup is opened. The user first sees an in-extension privacy/data-use notice and must explicitly choose Use Current Page. Only then can the extension read the current public page URL/title, sanitize the URL, and prepare the user-directed review flow. Its optional Website Check reads only a small set of technical page signals (such as HTTPS, mobile viewport/meta-description/canonical presence, H1 count and a bounded call-to-action signal); raw scanned page text is not retained. If the user chooses Add to Queue, up to 25 sanitized capture items may be stored locally in the browser extension until opened or cleared. Queue items are not automatically saved as CRM leads and the extension does not run a background crawler or automatically send messages.

Client Finder Pro Quick Capture uses extension-obtained data only for this disclosed single-purpose review workflow. It does not use or transfer that data for personalized advertising, retargeting, unrelated profiling, or data-broker resale. The extension is designed to comply with the Chrome Web Store User Data Policy, including the Limited Use requirements; material changes to extension data practices must be disclosed before release.

Client Finder can also import a public or published Google Sheet through its CSV export when a workspace user explicitly provides the Sheet link. This feature does not access private Google Sheets accounts or files and does not use a Google Sheets OAuth grant; imported rows remain subject to normal Client Finder review and duplicate controls.

Google Maps Platform features are subject to Google's applicable terms and privacy practices. See the Google Maps Platform Terms and Google Privacy Policy.

When Client Finder AI assistance is enabled in FREE-ONLY mode, AJ IT Solution uses Google Gemini 3.5 Flash-Lite through a dedicated Gemini Free Tier project. Google currently states that Free Tier content may be used to improve its products. For that reason, Client Finder minimizes the provider payload to business-level context only: individual contact names, email addresses, phone numbers, private notes, review context, opportunity notes, freeform outreach goals, and full website paths/query strings are excluded before the request is sent. AI generation is user-triggered, subject to workspace usage limits, and never sends messages automatically.

Users should still avoid entering sensitive, confidential, or personal information into fields intended for AI-assisted use. Client Finder AI remains unavailable unless the dedicated Free Tier configuration and owner data-use approval gates are explicitly enabled.

Digital-resource checkout and the affiliate program are fail-closed features and may remain disabled. If digital-resource checkout is activated, an authenticated customer's AJ account identifier, verified email, selected resource, provider price identifier, provider transaction identifier, entitlement status, and operational timestamps may be stored so AJ IT Solution can verify payment and deliver access.

Payment checkout is handled by the configured commerce provider. AJ IT Solution sends the provider the selected catalog item and limited transaction metadata needed to bind the checkout to the AJ account and resource. Optional affiliate metadata may include an approved affiliate identifier, referral code, and program terms version. Payment-card or bank-account credentials entered into the provider checkout are processed by that provider rather than stored as raw card/bank credentials in the AJ IT Solution application.

Signed provider webhooks are used to verify completed transactions and later adjustments. AJ IT Solution may retain transaction, entitlement, refund/adjustment state, and audit records needed to prevent duplicate access, handle refunds or chargebacks, and reconcile digital-resource delivery.

If the affiliate program is active, approved referral attribution may be associated with an eligible transaction. Affiliate applications can contain account email, display name, website, promotion-channel information, application notes, review status, and referral-code records. Commission records may contain the affiliate identifier, referral code, resource, eligible revenue basis, commission amount, currency, status, and adjustment history.

Google AdSense is not currently active. AJ IT Solution keeps the integration disabled unless a real publisher account, approved ad slots, and the required consent-management configuration are ready. No placeholder publisher ID is used.

If you have any questions about this privacy disclosure, data handling on this website, or would like to discuss digital services, please contact us directly: