Privacy Policy

1. Scope and roles

This Privacy Policy applies to elqorinpocket.com, project inquiries, discovery and delivery activities, support communications, and software or AI-assisted workflows where Elqorin Pocket processes information as part of a client engagement.

Depending on the engagement, Elqorin Pocket may act as a business that determines how limited website and sales information is used, or as a service provider/processor acting on documented instructions from a business client. A signed service agreement, statement of work, Data Processing Addendum, or application-specific privacy notice may define more specific obligations.

2. Information that may be collected

The information handled depends on the workflow being developed or supported. Categories may include:

• business contact information such as name, company, role, business email, phone number, and project details;
• technical information such as device type, application version, browser information, IP address, logs, timestamps, error reports, and security events;
• workflow data such as forms, tasks, reports, schedules, records, CRM fields, inventory information, maintenance records, or other operational data;
• user-submitted content such as photographs, images, documents, voice recordings, transcriptions, notes, attachments, and structured business data;
• authentication and access information needed to provide user accounts, permissions, or role-based access;
• project and commercial records such as statements of work, approvals, change requests, invoices, support tickets, and acceptance records.

3. How information is used

Information may be used to respond to inquiries, scope projects, design and develop applications, test functionality, provide hosting or integration support, monitor reliability, investigate errors, secure systems, maintain records, and support contracted business workflows.

When AI functionality is included, information may also be used for tasks such as extraction, transcription, summarization, classification, image or document interpretation, generation of structured output, workflow assistance, or preparation of drafts for human review.

4. Private AI and processing architecture

Elqorin Pocket uses the term “private AI” to describe a privacy-conscious architecture, not a universal promise that all processing stays on a device. The planned approach is to use on-device models where practical and controlled cloud AI services when the task requires greater capability.

Elqorin Pocket does not state that data is never used for model training unless the actual service tier, configuration, and contractual terms support that statement for the specific project.

5. Service providers and subprocessors

Elqorin Pocket may use managed hosting, database, authentication, communications, monitoring, analytics, source-control, AI, storage, or integration providers to deliver a contracted solution. The exact provider set varies by project.

Where a client requires a formal subprocessor list, notice procedure, or restrictions on international transfers, those requirements should be addressed in the project agreement or DPA before production processing begins.

6. Security measures

The planned security approach includes data minimization, encrypted transmission, secure credentials, role-based or least-privilege access, managed infrastructure, source control, logging, testing, and separation of development, test, and production environments where appropriate.

No system can be guaranteed absolutely secure. Security obligations, incident procedures, recovery expectations, and client responsibilities should be documented according to the nature of the application and data involved.

7. Sensitive and regulated information

Elqorin Pocket does not assume that every project is suitable for regulated or highly sensitive information. Before such information is introduced, the client and Elqorin Pocket should determine whether the proposed architecture, providers, contractual terms, and safeguards are appropriate.

Highly sensitive or regulated information should not be placed into AI services unless its use is contractually approved and technically protected for that workflow.

8. Retention and deletion

Retention periods depend on the purpose of processing, project requirements, active support needs, security records, accounting obligations, backup practices, dispute handling, and applicable law. Application data should follow a project-specific retention schedule rather than an indefinite default.

Deletion requests may be subject to identity verification, contractual responsibilities, legal retention requirements, and backup lifecycle limitations. Additional detail is provided in the Data Retention & Deletion Policy.

9. App Store and Google Play disclosures

If an application is distributed through Apple App Store or Google Play, the app’s privacy disclosures, permissions, data-safety information, tracking declarations, and account-deletion options must match the application’s actual behavior.

Store disclosures are maintained per application and may be more specific than this website Privacy Policy. If an app allows account creation, the project should include the deletion method required by the applicable platform and law.

10. Business customers and end users

Many Elqorin Pocket projects are built for business clients. In those cases, the client may control the end-user relationship and determine the purpose of processing. End users may need to direct access, correction, deletion, or similar requests to the client that operates the application.

11. International processing

Elqorin Pocket is based in Colorado and primarily serves U.S. business customers. International processing may occur where a client, user, or service provider is located outside the United States. Where GDPR or comparable transfer rules apply, the relevant transfer mechanism and contractual terms should be addressed in the applicable DPA.

12. Privacy requests and changes

Requests regarding access, correction, deletion, restriction, or other privacy matters should identify the relevant application, client business, account, and request type. Elqorin Pocket may need to verify identity and authority before acting.

This Policy may be updated as services, providers, application behavior, or legal requirements change. The Last Updated date identifies the current version.