Privacy Policy

About this policy

PocketFab LLC operates PocketFab.ai. This policy describes information used by our website and related software registration, activation, processing, and support services.

Information you provide

When you register software, we collect your email address and selected operating system to verify your address and deliver setup codes and the matching download. Activation uses installation identifiers, public keys, and license status to associate a grant with its installation. If you contact us, we receive the information you include in your message.

Uploaded photos, scans, and designs

Uploaded photos, scans, and designs are processed to provide the requested service and are deleted after processing. PocketFab staff do not access this uploaded content. We do not send it to outside AI services or use it to train AI models.

Operational information

Our services process technical information needed to deliver downloads, activate software, establish connections, diagnose faults, and protect against abuse. Depending on the service, this can include IP addresses, request times, browser or software information, installation identifiers, and connection or error records. These records are distinct from uploaded content and from the content of voice or video communications.

Secure Intercom maintenance diagnostics

Secure Intercom automatically produces limited server-side maintenance statistics from service operations. These statistics count software requests and state changes by day, operation, result and predefined error category. They may include an approved public software release label when available, together with collection and refresh timestamps. We use them to detect faults, investigate reliability problems and assess whether repairs are working. Request counts do not establish how many people used the service or how many conversations occurred.

The persistent maintenance counters do not include names, email addresses, IP addresses, installation identifiers, participant identifiers, call identifiers or invitation identifiers. They do not contain audio, video, recordings, transcripts or message content, and are not designed to record who communicated with whom. The service may temporarily use operational identifiers in memory to derive counts without adding those identifiers to the persistent counter records.

Registration, activation, licensing, contact, signaling and other operational records are separate from these counters and may include identifiers needed to operate the service. The limits stated for the counters do not mean that all service records are anonymous or that the service processes no metadata. We treat information as anonymous only where people cannot reasonably be identified, taking account of other information reasonably available.

The maintenance processing described here does not authorize recording or transcription of communications, use of private communications for advertising or AI model training, or profiling of individual communication relationships. Separate operational records remain subject to their disclosed purposes and safeguards.

Optional support information

Automatic maintenance counters are separate from information you choose to submit in a support request. Do not send passwords, private keys, active setup codes or recordings of other people without appropriate authority and an authorized process.

Any separately offered support-report function will explain what it includes and how you can review and choose whether to submit it. Declining an optional report does not itself cancel activation or waive contractual or statutory remedies, although it may limit the information available to investigate a particular fault.

Tracking and marketing

We do not use advertising tracking or track people across websites or applications for marketing. We do not sell personal information or share customer information for marketing. We use the limited maintenance statistics described above to operate and repair Secure Intercom. We do not use those statistics to profile individual communication habits or build a map of who communicates with whom. Functional storage used for service operation, such as sign-in or application settings, is separate from advertising tracking.

How information is used and handled

We use registration, activation, and support information to provide the requested services, verify eligibility, issue and manage licenses, respond to requests, and protect service operation. Hosting and email delivery involve infrastructure providers processing information needed to operate those services. This does not authorize use of uploaded content by outside AI services. Information may also be disclosed when required by applicable law.

Processing for organizational customers

Where PocketFab processes personal data on an organizational customer's behalf under an applicable data processing agreement, that agreement and lawful documented customer instructions continue to govern processing within their scope. Affected individuals may include the customer's authorized users and other individuals whose operational information is lawfully processed to provide the covered Services.

Within that agreed scope, maintenance processing may include transient in-memory comparison of operational installation, contact and signaling identifiers and technical event data, aggregation, restricted storage, authorized support review and deletion. The maintenance description does not itself expand the authorized operational source categories or their retention. Underlying source processing remains subject to the applicable data processing agreement even where an aggregate output is assessed as anonymous.

We apply access restrictions, data minimization and retention controls appropriate to this processing. This policy does not authorize us to repurpose personal data processed on a customer's behalf for independent analytics. Any distinct processing in which PocketFab determines its own purposes requires a separately established role, lawful basis and transparent disclosure.

Return and deletion at termination, authorized processing locations, subprocessors, transfer safeguards, security measures, assistance duties, incident obligations and audit rights remain governed by the applicable data processing agreement and law. This policy does not authorize a new subprocessor or international transfer, override mandatory transfer clauses, or amend a negotiated agreement outside its agreed amendment process.

These maintenance disclosures do not transfer ownership of customer information, expand the content license in Section 6 of our Terms, create a charge or subscription, reduce agreed security or change an agreed service level. Publication of this policy does not by itself constitute customer consent or acceptance of an amendment to a separate agreement.

Retention and deletion

Uploaded photos, scans, and designs are deleted after processing. Registration, activation, support, and operational records are separate from those uploads; the upload deletion rule does not mean these records are deleted at the same time.

Secure Intercom maintenance reports use a rolling window of seven daily buckets. Older buckets are excluded from newly generated reports, and an hourly cleanup process removes expired counters from the active diagnostic tables. This is a limit on these maintenance counters, not a promise that every operational record or every copy is erased after seven days.

All backups are retained for no longer than 60 days and are deleted or expire within that period. This maximum applies to backups containing maintenance information and to snapshots retained as backups. Restoring a backup must not reintroduce expired diagnostic records into normal use without applying the applicable retention controls.

Operational logs, support correspondence, exported reports and other copies held outside backups are separate records. The seven-daily-bucket maintenance window and the 60-day backup maximum do not establish the retention period for those separate records. We retain personal data in those records only as long as necessary for the relevant service, security or support purpose and applicable legal requirements. This policy does not create an indefinite retention right.

Where applicable law requires preservation of particular information, we restrict the preserved information to the relevant legal purpose and retain it only as required. This does not create a general exception to the 60-day backup limit.

To ask about retention of records associated with you or request deletion, contact operations@pocketfab.ai. We will explain any service or legal requirement that affects the request.

Your requests

Contact operations@pocketfab.ai with privacy questions or requests to access, correct, or delete information associated with you. Include enough information to identify the relevant account or installation, but do not send passwords, private keys, or activation secrets. We may need to verify your identity before acting on a request. Additional rights may apply depending on where you live.

Security

We use safeguards intended to protect information, including encrypted connections and signed activation mechanisms where applicable. No online service can guarantee absolute security.

Changes and contact

We will publish changes on this page with the actual revision date. Questions about this policy should be sent to operations@pocketfab.ai.