Privacy policy

[NAWOR] Labs Privacy Policy

Effective date: August 28, 2026
Last updated: August 28, 2026

[NAWOR] Labs (“[NAWOR] Labs,” “NAWOR,” “we,” “us,” or “our”) is a brand operated by ****(hidden to protect personal non-Second Life Information, this information will be disclosed in the need of any legal proceedings). It provides Second Life productivity products and connected web services, including the **[NAWOR] Labs Blogger HUD**, its Addons, the Store Integration Device, private scan workspaces, publishing integrations, and Unique [NAWOR] Links (collectively, the “Services”). The ****** the operator and data controller for the Services.

This Privacy Policy explains what information the Services collect, why we use it, when it may be shared, how long it may be retained, and the choices available to you.

The Services are operated from Texas, United States, and are offered to eligible Second Life users worldwide.

1. Scope

This policy applies to information processed through:

– NAWOR Labs websites and subdomains, including scan, connection, demonstration, redirect, and administrative services;
– NAWOR Labs Second Life HUDs and Addons, and their connected workspaces;
– private scan-result and Scan a Friend workspaces;
– Tumblr, Blogger/Blogspot, and WordPress publishing connections;
– customer access, merchant registration, feedback, support, entitlement, and Credit functions; and
– TMSL permanent links used to direct readers to a participating merchant’s current Second Life destination.

This policy does not govern independent services operated by Linden Research, Inc., Automattic/WordPress, Tumblr, Google/Blogger, Vercel, Supabase, Cloudflare, CasperTech/CasperVend, or another third party. Their own terms and privacy policies apply to their services.

2. Information we collect

2.1 Second Life identity and product-access information

We may collect your Second Life owner UUID, legacy name, display name, product or Addon entitlement, access status, activation source, purchase reference, Credit balance, and related support notes. The owner UUID is used as the durable identity for HUD access; an object or device UUID is not treated as the customer’s identity.

2.2 Scan and workspace content

When you run a scan, the Services may process information made available to the HUD or intentionally supplied by you, including:

– public inventory or attachment names exposed through Second Life;
– detected attachment points and proposed item categories;
– brand, product, variant, color, and item-detail text;
– approved merchant links and unresolved plain-text items;
– BOM Layer notecard entries you intentionally transfer through the supported device;
– Premiere Pose Stand pose names you choose to include;
– blog tags, Social Media Studio hashtags, social profile details, and formatting preferences;
– category corrections, confirmations, and other debugger feedback; and
– Scan a Friend content submitted through that feature.

The Services are designed to use expiring, opaque scan tokens rather than searchable public scan archives. Anyone who receives a valid, unexpired scan link may be able to open it, so you should treat the link as private.

2.3 Business information supplied through The Management SL

The NAWOR Blogger HUD receives maintained business information from The Management SL through its API. This can include official brand names, alternate names, store and event destinations, tags, social profiles, and product-naming examples used to interpret scan details. Store and event registration, review, and destination updates are managed through TMSL.

TMSL supplies permanent business and event links used in supported NAWOR credits. Approved destination updates are maintained through TMSL; its own terms and privacy policy govern its registration and link services.

2.4 Publishing connection information

If you connect Tumblr, Blogger/Blogspot, or WordPress, we may store:

– the provider and connected blog or site identifier;
– authorization tokens or equivalent credentials issued by that provider;
– connection status and configuration preferences; and
– draft-publishing requests, results, and diagnostic information.

NAWOR Labs does not ask for or receive your Tumblr, Google, or WordPress password. You authenticate on the provider’s own authorization page. Authorization tokens are sensitive and are used only to operate the connection you requested.

2.5 Purchases, subscriptions, Credits, and entitlements

We may keep records needed to deliver and support products, including purchased Addons, activation status, Credits, subscription or renewal status, transaction references, refund or revocation status, and the platform through which a purchase was made. Payment providers and Second Life commerce services may process additional payment data under their own policies. NAWOR Labs should not receive full payment-card credentials from those providers.

2.6 Communications and feedback

If you contact us, submit HUD feedback, request support, or communicate with a NAWOR administrator, we may collect the contents of the message, your Second Life identity or contact information, timestamps, status, and internal resolution notes.

2.7 Technical information

Our hosting, security, and infrastructure providers may automatically receive standard technical information such as IP address, browser or device type, requested URL, timestamps, error data, and security or server logs. We use this information to deliver, protect, diagnose, and maintain the Services.

Unique [NAWOR] Link analytics may record the internal Second Life account identifier associated with the originating HUD or published feature, the participating store, referring page, browser information, and a privacy-conscious unique-visitor indicator. NAWOR does not use the visitor’s IP address as the link-attribution identifier, although infrastructure providers may process IP addresses in ordinary network and security logs.

Google Analytics is planned for NAWOR websites. If enabled, it may process browser, device, referral, interaction, cookie, or similar analytics information according to NAWOR’s configuration and Google’s terms. NAWOR will provide any consent notice or choice required by applicable law before using non-essential analytics technologies.

3. How we use information

We use information to:

– authenticate customers and enforce product, Addon, subscription, and Credit access;
– create, retrieve, format, customize, and troubleshoot private scan workspaces;
– match scanned products to approved merchant records without inventing brands or destinations;
– create blog drafts or social-ready output at your direction;
– use permanent links supplied through TMSL for current store and event destinations;
– process merchant submissions, approvals, updates, and renewals;
– respond to feedback, support requests, disputes, and account-recovery needs;
– prevent misuse, secure the Services, enforce rate limits, and investigate failures;
– maintain records required for accounting, legal compliance, and service administration;
– improve scan classification and formatting through reviewed, auditable corrections;
– measure the use and effectiveness of participating-store links and eligible public blogger features;
– provide participating stores with launch-supported attribution and aggregated engagement information associated with their brand; and
– evaluate and improve the reliability, usefulness, and performance of the Services.

Debugger corrections may change the current scan immediately and may also be retained for administrator review and future classification improvement. We do not promise that an unreviewed correction will become a permanent global rule.

4. Legal bases for processing

Where a law requires a legal basis, we process information as necessary to perform a contract with you, take steps you request before entering a contract, pursue legitimate interests such as operating and securing the Services, comply with legal obligations, or act with your consent.

You may withdraw consent where processing depends on consent. Withdrawal does not affect processing that was lawful before withdrawal and may prevent the related optional feature from working.

5. How we disclose information

We may disclose information in the following circumstances:

– **Service providers.** Hosting, database, network, security, commerce, delivery, and technical providers may process information for us subject to their services and contractual terms. The current architecture uses Supabase, Vercel, and Cloudflare, and may use Second Life commerce or delivery services such as CasperVend.
– **Publishing providers.** When you request a connection or draft, we send the information needed to Tumblr, Google/Blogger, or WordPress. The chosen provider determines what formatting and metadata it accepts.
– **Second Life services.** Interactions with in-world products necessarily occur through Second Life and are also subject to Linden Research’s systems and policies.
– **Merchants and public link visitors.** A TMSL permanent link may expose only the intentionally public store destination or limited public listing information. It must not expose owner UUIDs, device identifiers, payment state, private notes, or scan contents.
– **Participating merchants.** When blogger attribution is active, an eligible participating store may receive the blogger’s approved public professional identity, qualifying public feature information, products associated with the store, and aggregated Unique [NAWOR] Link engagement. Stores do not receive the blogger’s Second Life UUID, private scans, unpublished drafts, OAuth credentials, email address, or Scan a Friend identity through this reporting.
– **Legal, safety, and enforcement needs.** We may disclose information when reasonably necessary to comply with law, protect rights or safety, investigate fraud or abuse, or enforce our agreements.
– **Business changes.** Information may be transferred as part of a merger, acquisition, financing, reorganization, or sale of assets, subject to applicable law and appropriate notice.

NAWOR Labs does not currently sell personal information or share it for cross-context behavioral advertising. If that practice changes, we will update this policy and provide any legally required choices before the change applies.

6. Data retention

We retain information only for as long as reasonably necessary for the purpose collected, including providing the Services, maintaining security and audit history, resolving disputes, and meeting legal or accounting obligations.

– Current scan workspaces and underlying raw scan data are retained for up to 30 days. A future separately entitled Scan Batching and History Cache Addon may offer a different customer-controlled history period, which will be disclosed before that feature is released.
– OAuth tokens are deleted when the customer disconnects the publishing connection, subject only to technically necessary provider revocation and security processing. Non-token connection or audit records may be retained where required for security, fraud prevention, or legal obligations.
– Expired merchant records are retained for 30 days while the Unique [NAWOR] Link may show a neutral availability notice. After that period, future scans revert to readable, unlinked brand text and no new store link is supplied unless the account is restored and verified.
– Support messages, feedback, resolution notes, entitlement records, transaction records, and records reasonably required for fraud prevention, accounting, legal claims, or proof of purchase may be retained indefinitely where necessary for those purposes.
– Reviewed classification corrections may be retained indefinitely as an auditable product rule or improvement example. Where practical, NAWOR minimizes or separates the originating customer’s identity from reusable rules.
– NAWOR-controlled security and application logs are retained for up to 180 days. Infrastructure providers may apply their own documented retention periods.
– Publishing-job content and diagnostic history follow the scan workspace’s 30-day retention period unless a shorter period is technically appropriate or longer retention is required to investigate fraud, security, or a support dispute.

When information is no longer needed, we delete it, anonymize it, or isolate it until deletion is technically practicable.

7. Security

We use administrative, technical, and organizational safeguards appropriate to the nature of the Services. Current design controls include multifactor authentication for the private Control Center, row-level database security, least-privilege server functions, opaque expiring scan tokens, server-side handling of privileged credentials, and keeping service-role keys and OAuth secrets out of browser and LSL source.

No method of transmission or storage is completely secure. You are responsible for protecting private scan links, your Second Life account, connected-provider accounts, and any device or browser through which you use the Services.

8. Your choices and privacy rights

Depending on where you live, you may have the right to request access to, correction of, deletion of, or a portable copy of personal information; object to or restrict certain processing; withdraw consent; opt out of certain sales or advertising-related sharing; and appeal or complain to a regulator.

You may also:

– disconnect a publishing provider or revoke NAWOR’s access through that provider;
– avoid submitting optional BOM, pose, social-profile, merchant-tag, or feedback information;
– request correction of inaccurate account or merchant information through the approved support process; and
– stop using the Services, subject to records we must retain for legitimate or legal reasons.

Account deletion disables connected HUD access and removes active publishing authorization information. NAWOR may retain entitlement, transaction, enforcement, fraud-prevention, accounting, legal, and proof-of-purchase records indefinitely where reasonably necessary.

To protect customers, we may need to verify your identity, Second Life ownership, or authority over a merchant record before completing a request. We will not unlawfully discriminate against you for exercising a privacy right.

Submit privacy requests to **naworlabs_sl@gmail.com** or through **https://www.naworlabs.com/support**. Include enough information to identify the relevant NAWOR or Second Life account, but do not send passwords, OAuth secrets, or unnecessary sensitive information.

9. International processing

NAWOR Labs and its providers may process information in countries other than the one where you live. Where required, we will use an approved legal mechanism and safeguards for international transfers.

10. Younger users

The Services are not intended for anyone under 16. Users who are 16 or 17 may use the Services only when their Second Life account is eligible for the relevant in-world access and, where required by applicable law, with authorization from a parent or legal guardian. We do not knowingly provide the Services to anyone who does not satisfy Second Life’s applicable age and account requirements. If we learn that an ineligible younger person used the Services, we will take appropriate steps to disable access and delete information except where retention is legally required.

11. Third-party links and services

Scan output and TMSL permanent links may lead to Second Life destinations, merchant pages, social profiles, or other third-party services. We do not control those destinations and are not responsible for their privacy or security practices. Review their policies before providing information.

12. Changes to this policy

We may update this policy as the Services, providers, or law change. We will change the “Last updated” date and provide additional notice when required. Material changes will not be applied retroactively where prohibited by law.

13. Contact

**Data controller/operator:****

Brand: [NAWOR] Labs

Location: Texas, United States

Privacy contact: naworlabs_sl@gmail.com

Support: https://www.naworlabs.com/support

**Website:** https://www.naworlabs.com

**Legal center:** https://www.naworlabs.com/legal

-

© 2026 NAWORLabs™. All Rights Reserved.
Second Life® and Linden Lab® are trademarks of Linden Research, Inc. All rights reserved. No infringement is intended.
Naworlabs.com is not affiliated with or sponsored by Linden Research.

Facebook Pages connection and data deletion

Facebook supplement updated October 18, 2026.

NAWOR's Social Media Studio connects a Facebook Page you choose and publishes a photo and caption when you explicitly send a prepared package from Post Production. Connecting a Page does not publish a post. This integration publishes to Facebook Pages, rather than personal Facebook timelines. Instagram is a separate connection.

To provide this connection, NAWOR processes the list of Pages you authorize, their names and identifiers, your Page publishing access, authorization tokens, the selected Page, and publishing requests and results. NAWOR uses pages_show_list to offer Page selection, pages_read_engagement to access and verify the selected Page's information, and pages_manage_posts to publish your requested content. Tokens are encrypted on the server and are not sent to the browser. Your Facebook password is entered on Facebook, not provided to NAWOR.

Disconnect Facebook

Open the Facebook connection from your HUD or private workspace and choose Disconnect. NAWOR clears the saved Facebook connection identifiers and authorization tokens and invalidates pending connection links. You can also remove NAWOR's access in Facebook's Business integrations settings. Removing access on Facebook and requesting deletion from NAWOR are separate steps.

Request deletion of Facebook-related data

Email naworlabs_sl@gmail.com with the subject “Facebook data deletion request”. Include your Second Life account name or owner UUID and the name or ID of the connected Facebook Page, if known. Say whether you want the Facebook connection data removed or broader NAWOR account deletion. Do not send passwords, access tokens, or copies of identity documents with the initial request.

We may verify your control of the relevant account or Page before processing the request. We will respond with the outcome and explain any information retained for security, fraud prevention, transaction records, legal obligations, or disputes under this policy. Disconnecting does not itself erase previously published Facebook posts or all publishing history. Manage published posts directly on Facebook; request deletion of retained NAWOR data by email.