Privacy Policy
Effective September 24, 2026 · SHA-256 062e59e548c798f01a49f218042cd108ebb986d7963fc6d5f596495d6eacac6e
This Privacy Policy explains how Applifyer, LLC, 131 Continental Dr, Suite 305, Newark, DE 19713, United States, processes personal data in connection with Farka. It is a notice, not a request to consent to processing that is necessary for the service contract or another lawful basis.
Roles and scope
Customers generally determine the purpose and means of processing uploaded training data, with Applifyer acting on documented instructions. Applifyer acts as controller for account, authentication, security, billing, support, legal, and service-operation data.
Data collected
We process account and membership details, authentication and security records, datasets and prompts supplied by customers, model configurations and artifacts, usage and billing records, support communications, and limited cookie-free product analytics.
- Product analytics excludes account IDs, emails, typed content, dataset names, prompts, and training material.
- Session replay and heatmaps are disabled. Advertising measurement is off by default and requires a separate choice.
Purposes and legal bases
We process data to provide and secure the service, execute customer instructions, meter and bill usage, provide support, improve reliability, prevent abuse, and meet legal duties. Depending on context, the legal basis is contract, legitimate interests, legal obligation, or separately requested consent.
Customer model training
We do not use customer datasets to train a general-purpose model or a model for another customer unless the customer separately requests and authorizes that use in writing.
Processors and recipients
Configured GPU, storage, payment, identity, email, deployment, analytics, optional advertising measurement, and observability providers receive only data needed for their function. The categories of provider, what each receives, and where each sits are published at farka.ai/subprocessors. Named providers, sub-processor terms, and processing terms for a specific deployment are available through Data control or a signed data-processing agreement.
Data residency
A training run may be pinned to the European Union or the United States. Pinning is enforced rather than advisory: compute is selected only from capacity resolved to the requested jurisdiction, there is no fallback to capacity outside it, and a run that cannot be placed in region fails instead of relocating. Each run records the jurisdiction it executed in within its training specification and export bundle.
- Pinned residency is offered only on a deployment whose application, database, logs, and object storage are all declared in that jurisdiction.
- A deployment that has not declared them offers automatic placement only, which carries no residency commitment and is recorded as carrying none in the quote and in the run evidence.
International transfers
Location depends on the declared application, database, logging, backup, and object-storage regions of the deployment, and on the residency selected for each training run. Where personal data leaves its region of origin, transfers rely on adequacy decisions or contractual and supplementary safeguards.
Retention
Account and operational data is kept while needed for the service, security, billing, disputes, or law. Dataset and artifact retention follows workspace controls and quotes. Deleted primary data may remain in bounded backups until scheduled expiry.
Security
We use encryption in transit, access controls, tenant ownership constraints, secret separation, audit evidence, bounded retention, and incident procedures. No system can guarantee absolute security.
Rights
Subject to applicable law, individuals may request access, portability, correction, deletion, restriction, objection, withdrawal of consent, and regulator review. Farka does not sell customer training data. Requests can be submitted in Settings, Data control, or by email.
Cookies and analytics
Essential session cookies authenticate and secure users. Private cookie-free analytics honors Do Not Track and records only bounded page and performance information without query strings or fragments.
Optional advertising measurement
Visitors arriving from a Google ad can separately allow Google Ads measurement. Only after that choice do we load the Google tag, which may store an ad click identifier and report a completed workspace signup to Google. The conversion event contains no email, account ID, prompt, dataset, or model artifact. Declining does not limit Farka, and the choice can be changed from the marketing site.
We remember the choice for 30 days in a first-party cookie shared by farka.ai and app.farka.ai. Google processes the ad click and conversion under its own privacy terms and may process this data outside the deployment region. Do Not Track and Global Privacy Control prevent the tag from loading. This optional choice is separate from acknowledgement of this policy and acceptance of the Terms.
Children
Farka accounts are for people aged 18 or older. Customer datasets may contain information about minors only where the customer has the required rights, lawful basis, and safeguards. This is distinct from allowing a minor to hold an account.
Policy changes
We notify users of material changes. A material version is shown in-product for acknowledgement before protected product use continues; acknowledging the notice does not convert contract-based processing into consent.
Contact
Privacy questions and rights requests may be sent to edihasaj@gmail.com.