Last updated: October 27, 2026
LASFIT Messaging is operated by 5DLIGHT INC., United States, for authorized LASFIT staff handling enquiries on our company Facebook Pages and Instagram professional accounts. This notice supplements the LASFIT Privacy Policy for this messaging integration.
Information we process and why
Subject to your interactions with our accounts, the permissions granted and Meta API availability, the integration processes account, participant, conversation and message identifiers; display names or usernames; message text and timestamps; and available attachment metadata or shared-content references. It also processes proposed replies and the records needed to check the intended recipient and authorize a reply.
We use this information to answer enquiries, handle customer support and business cooperation, prepare replies and investigate technical problems. We do not sell this information or use it for unrelated advertising profiles. We access only the company assets authorized for this integration and the information available through Meta's official APIs.
AI assistance and service providers
When an authorized operator uses Codex, selected conversation content and context are transmitted to and processed by OpenAI services to assist with a reply. This workflow is not entirely local. Processing and service-held records are subject to the applicable account settings, service terms and privacy arrangements. A person must review the exact recipient and final text before a reply is authorized, and applicable Meta messaging limits still apply.
We restrict access to staff and service providers needed for these purposes. Processing may involve countries outside your country of residence. We do not represent that all data is stored only in the United States or that service-provider copies are deleted at the same time as a local file.
Storage and retention
The current macOS integration stores access credentials in the operating system credential store. It retrieves conversations on demand and does not create a separate full-inbox archive or automatically download attachments. Selected content can nevertheless appear in Codex task records, and a frozen reply draft can be stored locally for human confirmation.
Our operating policy is to remove local expired drafts and temporary approval records promptly, with a target of no later than 24 hours after completion or expiry. Operators are responsible for applying this policy and checking that cleanup has completed. Devices that are switched off or unavailable must be handled when they become accessible. Draft expiry prevents sending even before the text is removed.
We keep only the operational records needed for support and security, normally for no longer than 30 days. Records of an uncertain send result may be held for the shortest necessary reconciliation period to avoid duplicate delivery. We do not put message bodies or credentials in ordinary operational logs. Tasks containing message content should have deletion requested promptly after completion, and no later than 30 days, using the relevant service's supported controls. Archiving a task does not count as deletion. Provider retention, device backups and any legally required exceptions must be handled separately.
We stop using credentials when authorization is revoked or the integration is discontinued and target removal of our credential copy within 24 hours once the relevant device is accessible. We do not retain information simply because a maximum retention period has not yet elapsed.
Your requests
Contact Novia at novia@lasfit.com for access, correction, deletion or other privacy requests concerning LASFIT Messaging. We aim to acknowledge requests within three business days and begin handling them promptly after any necessary identity checks. We generally aim to complete deletion of copies we control within 30 calendar days of receiving a request; any shorter applicable legal or Meta deadline takes priority. If a justified exception or service-provider dependency applies, we will explain the relevant scope and next step.
See LASFIT Messaging Data Deletion Instructions. Please do not send passwords, access tokens, verification codes or unnecessary identity documents. Disconnecting the app stops authorized future access but is separate from deleting existing records. We cannot delete records that Meta or another conversation participant holds independently.
Lawful requests and changes
We review the identity and legal basis of requests from public authorities, seek clarification or challenge requests where appropriate, and limit any lawful disclosure to the necessary information. We document the handling decision and apply relevant retention obligations. We will update this notice when the integration or our data handling changes.
