Privacy Policy | Takeloft

01 The service covered by this policy

FM DISTRIBUTORS ( PRIVATE ) LIMITED is responsible for the personal information it processes in operating Takeloft. Our address is h 4 street 42 muhammadi muhallah wassan pura, Lahore - 54000, Pakistan. You can reach the team responsible for privacy enquiries at contact@takeloft.app. Where an applicable data protection law uses the term controller, we act in that capacity for the purposes we determine and describe here.

This policy covers our official website at https://www.takeloft.app, the Takeloft Android app, its image-to-video and image-to-image functions, and our handling of purchase, support and privacy enquiries. Personal information includes details that identify you directly and information that can reasonably be linked to you, your device or your use of the service. A device reference or identifiable photograph may therefore be personal information even without a name.

Takeloft is in development, with Google Play availability coming soon. The website presents the product and its policies; it does not process creative requests or take payments. Descriptions of app handling apply when the relevant app functions become available. Website campaign artwork illustrates a visual direction and is not an app screenshot, an available template or evidence of a result produced by the app.

Reading this policy is not permission for every possible use of your information. A separate disclosure, permission or consent remains necessary wherever the activity and applicable law require one. Information about an independent service you visit is governed by that service's own notice as well as any obligations that continue to apply to our disclosures.

02 What happens when you request a creation

Takeloft uses self-hosted generation models on servers we operate. Selected input material is processed there to produce the image or video you request. Self-hosting does not mean that generation happens entirely on your phone. We do not send your creative material to an external AI generation provider.

Photo input is selected through Android's system Photo Picker. You choose the images to make available for a request; this is not permission to read your entire photo library. Supplying an image lets us process that chosen material for the task and its related delivery, support or safety handling within the limits below. You should only provide material you have the right to use.

We do not use a face to identify a person, perform facial recognition, build a biometric identity profile or extract biometric identity information. An ordinary image of a recognizable person can nevertheless reveal personal information. The absence of biometric identification does not remove the need to protect that image or obtain the person's permission to use it.

No user information is used to train AI models. This restriction covers creative material and also identifiers, technical records, purchase information, correspondence and reports. Completing a generation, investigating an error or responding to misuse does not authorize a separate training use.

Every creation has a maximum 48-hour lifetime for all its information in systems we control and with processors acting for us. The clock begins when input upload starts, or when a prompt is submitted for a request without an upload. It does not restart when an output is produced. The fixed-lifetime section explains the full scope, including associated records and copies.

03 One deadline for all information about a creation

All creation information must be removed within 48 hours from the start of the input upload. If a request has no upload, the starting event is submission of its prompt. Inputs, outputs, instructions, settings, task identifiers, state, timestamps, metadata, associations and every related copy share that original deadline. Completing a result, retrying within the request, copying a file or moving a record does not start a new period.

The commitment covers all systems under our control and all processors handling the information for us. It includes databases, task records, logs, support and reporting tools, attachments, thumbnails, caches and backups. Keeping a reference or association after removing a media file would still retain creation information and is included in the removal obligation.

Routine removal does not depend on a support request or completion of identity checks. A pending purchase issue, content report, security enquiry or legal case cannot be used to keep creation information past its deadline. Any independent record required afterwards must first have the creation content, details and associations removed.

Save an available result to your own device before its deadline if you want to keep it. We cannot reconstruct erased creative records for a later download. Copies that you export and independently share outside our systems remain under your or the recipient's control, and our deletion does not remove those copies.

Only genuinely independent information follows the purpose-based periods below. The length depends on the reason for retention, applicable obligations, an outstanding issue and your valid requests. It is not a general permission to retain all service information indefinitely. When the independent purpose no longer requires it, the record is deleted or properly de-identified.

Independent app-user and settings records are kept as necessary to administer use and access, and addressed when you request removal or they are no longer needed. They cannot preserve a creation reference or association past its deadline.
Independent purchase and financial records may remain for verification, delivery and entitlement reconciliation, refunds, disputes, tax or accounting. Deleting creative work does not automatically delete separate purchase history, and purchase history cannot retain creative details.
Independent support and moderation records may remain to handle an issue, explain a response or address a dispute after all creation information, attachments and associations have been removed by the original deadline.
Independent diagnostic and security records may remain as necessary for reliability, protection or an investigation. Logs and incident records are subject to the same removal of every item related to a creation.
Independent attribution records follow the necessary source-attribution arrangements and applicable privacy requests. Their separate criteria do not authorize collecting or retaining creative information through Adjust.
A necessary backup of independent non-creation records is restricted from ordinary use and handled through the relevant deletion process; removal must be reapplied if restoration would reintroduce deleted data. All creation information in backups is removed by the original creation deadline without a backup exception.

04 Photos of other people, banned content and how to report it

Only upload or instruct us to process material that you are entitled to use. If another person appears in a photo, obtain that person's consent and any additional authorization required for the proposed use. An image being publicly visible online does not grant permission to copy it, use a person's likeness or create a new depiction of them.

The restrictions below protect people whose information or likeness may be involved. They apply to inputs, instructions, generated material and the way a result is used. AI generation does not make a prohibited depiction acceptable or remove another person's rights. Review a result before sharing it; a generated appearance or scene should not be presented as evidence that an event happened.

Non-consensual intimate imagery (NCII), including AI-generated nude or sexual depictions made or shared without the depicted person's consent, is prohibited.
Child sexual abuse material and any sexualization of a minor are prohibited, including synthetic depictions and instructions intended to produce them.
Harassment, threats, degrading abuse, deceptive impersonation of a real person and fraud are prohibited.
Material or uses that infringe copyright, privacy, rights in a person's image or likeness, or other protected rights are prohibited.

To report an infringement or prohibited content, use the reporting option in the creation's detail page inside Takeloft, visit the Help & contact page, or email contact@takeloft.app. You can use the in-app reporting route without leaving the app. Explain the problem and give an available reference; do not forward the prohibited material itself or unnecessary details about the person affected.

We may remove content or limit access to a function when addressing misuse. Repeated violations, or a single serious violation such as non-consensual intimate imagery or sexual content involving a minor, may result in suspended use or removal of app-user records. The response depends on the nature and seriousness of the violation, and appropriate review and support remain available.

Reviewing a report, handling a rights complaint or recording a moderation decision does not extend the lifetime of a creation. Any independent case record kept after its deadline must exclude the creative material and every association with that creation. Necessary information about the case may remain only under the separate retention criteria in the creation-lifetime section.

05 Material and messages you give us

Your choices determine much of the information received directly. You may select an image, enter instructions, choose generation options, report a problem or write to support. Please avoid adding confidential documents, unrelated identifying details or sensitive information that the request does not need.

Creation information means all information belonging or relating to a particular creation, not just the finished image or video. The examples below are not an exhaustive list. An item remains creation information when copied into a different system, attached to an enquiry or linked from an otherwise independent record.

Creative inputs and results: prompts or instructions, selected input images or videos where supplied, and output images or videos.
Information associated with a creation: generation parameters and choices, task records and identifiers, task state, timestamps, metadata, links and associations, previews, thumbnails and other information that describes or points to the work.
Copies and records containing creative information: originals, duplicates, cached material, backups, logs, report attachments, support attachments and any other controlled or processor-held record containing or linking to that information.
Correspondence and requested help: your explanation, available app-user or purchase references, a report of content or an error, and the details needed to reply. Any creation information within those materials keeps its original creation deadline.

We receive an email address when you write to us, together with the message and any attachments you choose to send. A support address does not become a Takeloft login. A content report may include a reference and explanation provided through the creation's detail page in the app. Avoid forwarding prohibited imagery itself; describe the concern and provide an available reference instead.

The deletion page can prepare an email using optional information you type. That form operates in your browser, without submitting the fields to our website or saving them in persistent browser storage. Sending the prepared message through your chosen email service is a separate step, after which we receive the correspondence. The browser-and-device section explains the available mail options.

06 Records arising from devices, stores and service operation

Information also arises when a device contacts our services, when an app store confirms a transaction or when a permitted attribution signal identifies an installation source. These sources are distinct from a photograph or message you deliberately supply. They still require a stated purpose and appropriate protection.

Google Play manages its payment process and provides relevant transaction information to support verification and administration of a purchase. We do not need your store password, authentication code or complete payment-card details to investigate an app purchase. Describe a purchase problem using an available order reference and the relevant part of a receipt instead.

An app-user or installation record may be used for settings, access or purchased benefits. If that record contains a task reference, creative metadata or another association with a creation, that part is creation information and must be removed by the creation's deadline. An independent transaction history is not itself a surviving copy of a creation.

Device and app records may include app-user or installation references, settings and preferences, and information needed to administer access or purchased benefits without a registration account.
Transaction records may include order and transaction references, the item purchased, dates, verification responses, receipt information, delivery status, purchase and refund status, and the resulting entitlement or its adjustment.
Technical records may include IP address, browser or device characteristics, operating system and app versions, request times, relevant service interactions, diagnostic information and error or security logs.
Installation-source attribution may involve permitted device or advertising identifiers, referrer or channel information, IP and version details, and installation, first-open or session signals. The dedicated Adjust section describes the purpose and excluded information.

07 App records do not require a login

Takeloft does not ask you to create a login profile, register a password or sign in through a social service. You can use the available app functions without those registration steps. There is no social sign-in collection to infer from a reference to an app user or a deletion control.

The service can still hold information associated with an installation or use of the app. Identifiers, settings, purchases, technical interactions and correspondence may relate to a device or person even though they are not presented as a login account. We use relevant references to deliver the service and locate information when you request assistance.

A Google Play account belongs to Google's separate service. Making a purchase there does not establish a Takeloft login, and deleting Takeloft information does not close that account or instruct Google to erase independently held transaction records. Google provides its own information and controls for those matters.

You do not need to create an account, reinstall the app or complete an in-app deletion attempt before contacting us about your information. If an available reference has been lost, explain what you still know. We consider a proportionate way to locate the records and verify authority instead of asking you to guess identifiers or share another service's credentials.

08 Website interactions, email preparation and device choices

The website is informational. It does not run analytics or advertising cookies, process an AI creation, accept a payment or persist your gallery selections in browser storage. Its typography uses system fonts rather than an external font service. Normal browser caching of pages or images is distinct from a website tracking profile; network requests may still generate delivery and security records as described above.

The deletion form prepares text locally from your optional entries and required confirmation of authority. It attempts to open your email application and also displays alternatives: Gmail, Outlook.com, another mail-app attempt, copying the complete message and manually selecting the prepared text. The website does not send the message or save the fields. Review the message and send it yourself to initiate the email request.

If you select a webmail alternative, the prepared address, subject and message are passed to the selected email provider to open its composition interface. That provider handles the interaction under its own terms and privacy notice. Do not include passwords, authentication codes, full payment details, unnecessary identity documents or prohibited creative material in a prepared message.

The installed app and its SDK operate separately from website cookies. Changing a browser setting does not automatically disable Adjust in the app or erase a service record. Likewise, clearing a local app cache or uninstalling the app does not itself communicate a request to delete remotely held records.

For image selection, Android's system Photo Picker supplies the items you choose. Relevant device permission choices can be reviewed through the operating system, and refusing or changing access may affect the associated function. A permission change does not retrieve material already submitted or override its fixed automatic deletion deadline.

External links take you to independent services. Our responsibilities for a disclosure remain, but a direct visit to an app store, an attribution provider's information page or your email provider can involve that service's own collection and controls. You can ask us about a disclosure made for Takeloft without needing to use an unrelated external account.

09 Adjust and the origin of an installation

The Adjust integration is used only for installation-source attribution: identifying the referral, campaign or channel connected with an installation of Takeloft. Adjust is not a generation service, a review service for your work or a purchase-event analytics service for Takeloft.

Attribution involves technical information. Depending on availability, applicable permission and privacy choices, that information can include device or advertising identifiers, installation referrer and channel details, IP address, operating system and app or SDK version, and installation, first-open or session signals relevant to the source attribution. Describing this narrow purpose does not mean that Adjust receives no data.

We do not send Adjust your prompts, input images or videos, generated results, task metadata or other creation information. Support messages, content reports and their attachments are not sent to Adjust, and it is not used for purchase-event tracking or analysis of your creative activities.

Necessary attribution information and the resulting source information may be exchanged with acquisition channels connected through enabled integrations, subject to applicable consent and privacy choices. These are attribution exchanges, not permission to include excluded creative, support or purchasing information. Independent attribution records have their own necessary retention arrangements; they are not assigned the creation deadline as though they were creative files.

Device privacy controls and permitted advertising-identifier choices may affect this processing. They do not automatically erase previously collected records. For access, removal, an objection or an applicable advertising opt-out concerning the integration used for Takeloft, contact contact@takeloft.app. We address the processing for which we are responsible, including relevant requests to providers acting for us. Adjust's own privacy information describes its responsibilities and available choices.

10 The purposes for which information is used

We connect information to a purpose rather than treating the presence of a record as permission for unrelated use. The relevant amount and type of information depend on whether you are requesting a creation, asking about a purchase, reporting a problem or exercising a privacy right.

Service performance can also be understood through aggregated or properly de-identified information. Merely replacing a name with a reference, or hashing an identifier, does not necessarily make information anonymous. Material that remains linked or reasonably linkable to a person continues to receive the protection of this policy. Statistics and diagnostics cannot be used to preserve creation information beyond its deadline.

None of these purposes permits training an AI model with user information. A need to administer a purchase, prevent misuse or improve reliability does not change that restriction. Where a proposed use is materially different, any required notice, consent or other legal step must happen before that use rather than being assumed from an earlier interaction.

Fulfil the creative request: receive chosen material, apply the requested settings, run and manage the task, and make the result available within its lifetime.
Operate the service: maintain relevant app settings and access, associate actions with the appropriate service record, and communicate information about availability or an outstanding request.
Administer purchases: verify a store transaction, provide the purchased benefit, investigate missing delivery and reconcile refunds, reversals or disputed transactions.
Answer and review: handle questions, content reports, technical incidents, privacy choices and deletion requests, including appropriate verification and follow-up communications.
Identify installation sources: use the limited Adjust integration to understand the referral, campaign or channel from which an installation came, without analyzing creative work or purchase events.
Protect lawful operation: diagnose failures, address security threats, misuse and fraud, manage legitimate claims, and meet applicable accounting, tax or other obligations.

12 Recipients and the limits on disclosure

We limit disclosure to information relevant to the stated purpose. A provider's role, a legal obligation or your instruction determines why information is supplied; receiving one kind of information does not authorize unrestricted access to the rest of your records.

Providers acting for us must handle information for the authorized work with appropriate protection. Our deletion commitment follows creation information held by those processors. An app store or another independent recipient may have separate obligations for information it holds in its own capacity, which should not be confused with a copy retained on our behalf.

We do not sell personal information for money. Some laws also treat certain non-monetary disclosures or advertising-related exchanges as a sale or sharing. The regional sections address those definitions and related choices without assuming that every attribution integration is outside their scope.

Operational providers: services supporting infrastructure, hosting, delivery, communication, support or security may receive relevant information for that work. Adjust receives the limited attribution information described above. These roles are separate from an external AI generation provider, which we do not use.
Google Play and purchase administration: relevant transaction, delivery, entitlement, refund or verification information may be exchanged to administer an actual purchase or resolve a store-related issue.
Professional advisers: lawyers, accountants, auditors, insurers or similar advisers may receive necessary records for advice, compliance, a claim or legitimate administration, subject to appropriate confidentiality obligations.
Lawful and protective disclosures: relevant information may be provided in response to a valid legal requirement, or where law permits it to protect people, investigate misuse or establish, exercise or defend rights. This does not create a retention exception for creation information.
Business changes: a proposed or completed financing, merger, acquisition, reorganization or transfer of assets may involve relevant records. Confidentiality, required notice and other applicable safeguards continue to apply; a change of operator does not erase existing privacy obligations.
Your chosen recipients: we may act on an authorized instruction to supply information to your representative. A copy you export and independently share is then handled by you or that recipient separately from the service's controlled copies.

13 Processing across borders

FM DISTRIBUTORS ( PRIVATE ) LIMITED is based in Pakistan. Using the service or communicating with us may involve handling outside the country in which you live, including where operational providers carry out their work.

Different locations can have different legal protections. Where a transfer is subject to data protection requirements, we apply the required safeguards or an available lawful transfer basis. Depending on the applicable law and circumstances, those may involve recognized adequacy arrangements, contractual safeguards or another permitted mechanism. The safeguards must address the transfer and its actual circumstances.

The purpose limits, access restrictions, no-training commitment and fixed creation deadline continue to apply to processing for us across borders. An internal transfer or a processor working from another location cannot restart the creation clock or turn a controlled copy into an exempt independent record.

You may ask contact@takeloft.app for information about safeguards relevant to your information and how to exercise an applicable transfer-related right. We provide the information required by law, taking account of legitimate confidentiality and security needs. Contacting us does not waive any right to approach an authority available under the law that applies to you.

14 Safeguards and security concerns

We use technical, administrative and organizational measures appropriate to the information and the risks of handling it. These include controls over access, relevant protection for storage and transmission, and procedures for managing service and security issues. Access should be related to a person's authorized task rather than available simply because a record exists.

A processor's involvement does not remove our responsibility to require appropriate protection for work carried out on our behalf. Security and support handling must also respect the creation lifetime. Making an investigation copy, saving a diagnostic attachment or placing material in a backup does not authorize longer retention of creative information.

No storage method, connection or security program can promise absolute protection from every possible incident. If an incident affects personal information, we assess it, take appropriate action and provide the notifications required by applicable law. This statement does not reduce our legal obligations or make you responsible for failures within our control.

If you suspect unauthorized use or disclosure connected with Takeloft, write to contact@takeloft.app. Describe the event and give a relevant reference if available. Do not send passwords, store authentication codes or an additional copy of sensitive imagery merely to report the concern. Keep your device and access to your chosen email and store services appropriately protected.

15 Your rights and how to exercise them

The rights available depend on the law applying to the information and activity, including any relevant territorial scope, thresholds and exceptions. We describe the principal rights here so that you can identify a request without needing a Takeloft login. The California and Virginia sections add information for those laws where applicable.

Contact contact@takeloft.app with the right you want to exercise and enough context to find the relevant information. An available app-user, purchase or correspondence reference can help. We seek verification proportionate to the request and the risk of disclosing or removing another person's information. An authorized representative may act where permitted, with suitable evidence of authority and any required verification.

Where a legitimate-interests basis applies, you may have a right to object for reasons related to your circumstances. An applicable objection to direct marketing does not require the same personal explanation. Exercising a privacy right does not itself authorize unrelated marketing contact or require you to agree to a different processing purpose.

We handle requests within the period required by applicable law. If a lawful limitation, extension or charge applies, we explain it and the available next step. We do not unlawfully discriminate against you for exercising a protected right. You may complain to the competent regulator available under applicable law; contacting us first can help resolve a problem but does not remove a right to contact that authority directly.

Access and information: ask whether information concerning you is processed, request a copy and receive the required explanation of collection, use, disclosure and retention.
Correction: ask for inaccurate information to be corrected or incomplete information to be completed for its relevant purpose.
Erasure or restriction: request deletion or limits on processing where the applicable conditions are met. Exceptions for necessary independent records do not extend the creation deadline.
Portability: where applicable, receive information you supplied in a usable format or ask for a technically feasible transfer to another provider.
Consent and objection: withdraw a consent-based choice without affecting prior lawful processing, or object to relevant processing under the applicable law.
Advertising and profiling choices: request an applicable opt-out of sale, advertising-related sharing, targeted advertising or qualifying significant-effect profiling.

16 Deletion requests and the records they cover

In the app, open Personal Settings, find the data-deletion option and follow the instructions and confirmation shown there. We do not require a separate login to start this process. Save any available creations you want to keep before requesting removal or reaching their automatic deadline.

You can also write directly to contact@takeloft.app, including when Takeloft is not installed, will not open or its deletion control cannot be used. The Delete your data page offers an email-preparation form and fallback options. These routes work independently; an earlier in-app attempt is not required. Provide a reference if available, but do not invent a missing identifier or disclose a store password.

Removal covers the relevant app-user record, associated personal information and all remaining creation information in our systems and with processors acting for us. We take appropriate steps with those processors. We may need proportionate verification to protect another person's records, but that verification does not stop the separate routine deletion of creations.

Support handles an application for removal as soon as it is seen, with completion expected within 30 days. An exceptional case may take longer; we explain an extension where lawful, and follow any shorter period required by law. This manual-request timetable never extends the 48-hour limit for all creation information from its original starting event.

Some independent transaction, tax, dispute, security, support or attribution records may need to remain for a defined lawful purpose. We explain relevant retention and remove creation material, task information, metadata and associations by the original creation deadline. A retained purchase record is not permission to keep a user's creative history.

A data-deletion request does not automatically apply for a refund or close your Google account. Purchase concerns can be raised separately or identified in the same correspondence. Copies you have exported or independently shared remain outside our controlled removal process; deletion of records we hold cannot erase another person's independent copy.

17 California rights where the law applies

California privacy rights depend on the law's scope, definitions, thresholds and exceptions. Where the California Consumer Privacy Act applies to our handling, this section supplements the categories, sources, uses, recipients and retention criteria elsewhere in the policy.

Relevant categories may include identifiers such as app references and support email addresses; commercial records such as purchase information; internet or app interactions and technical information; and images, videos, prompts and correspondence you supply. Creative material may reveal other categories depending on its content. The purposes and recipient sections describe how those categories are used and disclosed.

We do not exchange personal information for money. California also regulates other qualifying sales and sharing for cross-context behavioral advertising. To the extent an attribution exchange with an enabled acquisition channel falls within those definitions, the applicable opt-out is available through our privacy contact or a recognized preference signal.

Send a request or authorized-agent enquiry to contact@takeloft.app. We apply appropriate verification where required and explain any applicable exception. You do not need to resend a sensitive image merely to ask about it. An agent may need to establish authorization and meet the required verification procedure; the process must not require an unnecessary Takeloft login.

Request information about collection, use and disclosure and access to the personal information covered by the applicable right.
Request correction of inaccurate information and deletion, subject to the law's relevant exceptions and our separate fixed creation-removal commitment.
Opt out of a covered sale or sharing, and limit qualifying uses or disclosures of sensitive personal information where that right applies.
Use an authorized agent under the applicable rules and exercise rights without unlawful discrimination.

18 Virginia requests and appeals where applicable

For an eligible resident whose information is within the Virginia Consumer Data Protection Act's scope, the rights below apply subject to the statute's conditions and exceptions. The categories, purposes and recipients explained elsewhere in this policy describe the processing to which those rights relate.

Confirm whether personal data is being processed and obtain access to it.
Correct inaccurate data, request deletion and receive an applicable portable copy in a usable form.
Opt out of covered targeted advertising, a sale of personal data or profiling used for decisions with legal or similarly significant effects.
Appeal the handling of a privacy request and exercise protected rights without unlawful discrimination.

You can submit a request to contact@takeloft.app. Identify the action requested and provide an available reference that helps us locate the information. We authenticate a request as required without asking you to create a login profile. A parent or other authorized person may act where the law provides that authority.

If you disagree with a decision on your request, reply to the response or write to the same address identifying it as a privacy appeal. Explain what you believe should be reviewed. We consider the appeal within the applicable legal period and explain the decision and any available route to the competent authority. Raising an appeal does not remove other rights available to you.

Applicable response rules, permissible extensions and limited exceptions govern how the request is handled. We explain a restriction or refusal and do not impose an unlawful disadvantage because a right was exercised. The ordinary 48-hour removal of creation information continues independently while a request or appeal is being considered.

19 Browser signals and other opt-out choices

A browser's legacy Do-Not-Track setting does not have one uniform implementation across services. We do not interpret it as a general instruction to delete all app records, withdraw every consent or switch off every function of an installed SDK. It should not be confused with a legally recognized opt-out signal.

Where applicable law requires recognition of an opt-out preference signal, such as Global Privacy Control for a covered activity, we give a valid signal the effect required by that law. Its reach depends on the browser, device and processing context. A signal sent while browsing the website does not necessarily identify a separate app installation or a record held under another identifier.

You may send an applicable sale, sharing or targeted-advertising opt-out directly to contact@takeloft.app. Explain which service or available device reference it concerns so we can apply it appropriately. Where necessary we ask for limited clarification; a new registration account is not required.

The website does not use advertising or analytics cookies. That does not turn a device-level choice into deletion of an independent attribution record. Relevant choices for permitted attribution exchanges are addressed with the Adjust handling, and a valid request can include both an opt-out and a request to remove information where the law provides those rights.

20 Age requirements and particularly sensitive material

Use of Takeloft must meet the applicable age, capacity and permission requirements. The age rating shown in a store listing describes the store's rating and is not a substitute for legal requirements that apply to a particular user or processing activity.

A parent or guardian who believes a child's information has been provided inappropriately can contact us to explain the concern. We consider the information needed to investigate and take appropriate action, including removal where required. A valid representative may exercise rights for a child where the relevant law permits that role. Do not send unrelated identity documents or prohibited imagery to establish the concern.

An image, prompt or message can reveal health, beliefs, sexuality, private family circumstances or other sensitive information even when the form does not expressly ask for it. Avoid such information unless necessary and lawful for your request. Never supply sexualized material involving a minor. The content restrictions apply to synthetic and real depictions alike.

We do not build biometric identity information from faces, and we do not train AI with information concerning a child or anyone else. When sensitive material is part of a creation, all of its related records and copies remain subject to the original automatic deletion deadline, including information placed in a report or support message.

21 Policy updates and getting in touch

The date shown with this policy identifies its current version. We may update the policy when Takeloft's features, processing arrangements or applicable requirements change. A material change receives the additional notice required in the circumstances. Editing a webpage cannot replace consent, a required disclosure or another legal step for a new processing activity.

A revision must reflect the service's actual handling rather than silently introduce a broader use of information. Where a change affects existing information or an earlier interaction, we address the applicable notice and rights associated with that change. A later version is not permission to disregard the deadline already attached to a creation.

For information requests, objections, deletion, an appeal, a security concern or help understanding this policy, contact contact@takeloft.app. Written enquiries may also be addressed to FM DISTRIBUTORS ( PRIVATE ) LIMITED, h 4 street 42 muhammadi muhallah wassan pura, Lahore - 54000, Pakistan. The Help & contact and Delete your data pages explain the support and removal routes in more detail.

Describe the issue and provide an app-user, purchase or earlier correspondence reference if available. Avoid passwords, authentication codes, full payment details, unrelated identity documents and prohibited material. If a reference is missing, tell us what information remains so the next step can be proportionate to locating and protecting the records concerned.