NX6 OS Privacy Policy

1. Introduction

Welcome to NX6 OS ("NX6 OS," "we," "us," or "our"), operated by AVC Partner Solutions LLC. This Privacy Policy explains how we collect, use, disclose, and safeguard information when you use our marketing command center.

NX6 OS is a social media management and marketing-automation platform. It lets businesses and marketing agencies connect their own social and business accounts — including Facebook Pages, Instagram Business/Creator accounts, LinkedIn, YouTube, Google Business Profile, Google Analytics, Google Search Console, and Google Merchant Center — to schedule and publish content, respond to engagement, and view performance analytics from one place. NX6 OS also provides AI-assisted content generation.

1.1 Who This Policy Applies To, and Who Is Responsible for What

NX6 OS is a multi-tenant, white-label platform. It can be resold by a marketing agency to its own clients under the agency's branding, so the page you are reading may be presented under a name other than NX6 OS. Two kinds of people use the platform, and the responsibility for personal data differs for each:

• The agency (our direct customer). The agency signs up, pays, connects accounts, and invites its clients and their store-level staff. The agency decides what personal data enters the platform and why.
• The agency's clients and their stores/locations. They are given scoped access by the agency. Their data lives inside the agency's tenant.

Under GDPR/UK GDPR terminology, the agency is the controller of the personal data it and its clients put into the platform, and NX6 OS is the processor acting on the agency's instructions. We are an independent controller only for the limited data we need to run our own business — account registration, billing, support correspondence, and security logs. Section 8 sets this out in full, together with how to get a Data Processing Addendum.

If you are a client or store user and want your data corrected or deleted, contact your agency first — they control it. You can always contact us directly at privacy@avcpp.com, and we will work with the agency to action your request.

2. Information We Collect

2.1 Information You Provide

• Account Information: Email address, display name, and company/agency name. You sign in with Google or with a one-time email link, so NX6 OS holds no password for you.
• Profile Data: Business type, brand details, marketing goals, preferences
• Client and Store Records: The business names, addresses, phone numbers, service areas, and staff email addresses an agency enters or imports for its clients and their locations
• Payment Information: Billing address and payment method, collected and processed by Stripe. We store a Stripe customer/subscription identifier and invoice metadata; we never receive or store full card numbers
• Content Data: Posts, captions, prompts, images, videos, and related metadata you create or upload
• Customer Contact Details for Review Requests: The names and email addresses of a business's own customers and, where the business chooses to add them, the staff member who served the customer and the service the customer received. The agency or business enters or uploads these so NX6 OS can email the customer a request for a review. Each request email carries a link to stop further requests
• Photos Sent In by a Business: Photos and short clips that a business or its staff send to its photo library, including through a phone upload link
• Communication Data: Support tickets, feedback, and correspondence with our team

2.2 Automatically Collected Information

• Usage Data: Pages visited, features used, time spent, click patterns
• Device Information: Browser type, operating system, device identifiers, IP address
• Log Data: API requests, error logs, performance metrics, timestamps
• Error Reports and Optional Diagnostics: See Section 9 — error reports are always sent; session recordings and page-speed measurements are sent only if you choose "Allow diagnostics"
• Cookies and Local Storage: Authentication tokens, session IDs, preferences (see Section 13)

2.3 Information From Connected Platforms

When you connect a third-party account, you authorize NX6 OS to access certain data from that platform through its official API, using industry-standard OAuth. We only access data for the specific accounts, Pages, channels, properties, and locations you explicitly choose to connect, and only within the scopes you approve on the provider's own consent screen. Sections 4 and 5 describe the Google and Meta data in detail.

2.4 Online Store Connections (Shopify and BigCommerce)

If an agency connects a Shopify or BigCommerce store to a location, NX6 OS reads that store's product catalog: product names, descriptions, prices, images, SKUs and stock levels, and, from Shopify, the store's own locations. To show sales by product, NX6 OS also reads recent orders from Shopify. Only the products, quantities and prices on each order are used: they are added up into totals per product while the report is built, and no order, order number or customer detail (name, email, address or phone) is stored. Shopify treats access to orders as protected customer data. NX6 OS does not request Shopify's read_customers permission, and it reads no customer fields from orders. A BigCommerce store is connected with a read-only catalog key the merchant creates, and NX6 OS does not read its orders. The connection's credentials are stored encrypted. Disconnecting the store deletes them, and closing the workspace also deletes the product records copied from it.

3. How We Use Your Information

• Deliver the service: schedule and publish content, show analytics, manage reviews and engagement
• Generate AI content based on your prompts and the material you select
• Operate, secure, and improve NX6 OS, and develop new features
• Provide support and send transactional and (opt-out) marketing communications
• Bill you, enforce plan quotas, and prevent abuse
• Comply with legal obligations, and investigate fraud, abuse, or security incidents

We do not sell personal information, and we do not use your data or your connected-account data for advertising targeting or to build cross-site profiles.

3.1 Our Legal Bases

Where the GDPR or UK GDPR applies to the data we control ourselves (Section 8.1), we rely on these legal bases:

Legal basis	What we rely on it for
Contract	Creating and running your account, signing you in, providing the features you use, billing you, and answering your support requests. Without this data we cannot provide the Service.
Legitimate interests	Keeping the Service secure and preventing abuse: App Check, rate limits, security and audit logs, and the record that stops one person claiming the free AI allowance more than once. Finding and fixing faults through error reports (Section 9). Telling account holders about our own service by email, with an opt-out in every message. Our interest is a service that works, stays secure and is not abused, and we use only the data that needs.
Consent	Session recordings and page-speed measurements, which run only after you choose "Allow diagnostics" (Section 9), and anything else we ask your permission for in the product. You can withdraw consent at any time; that does not affect what was done before.
Legal obligation	Keeping payment and invoice records for 7 years, and answering lawful requests from authorities (Section 6.5).

Your right to object. You can object at any time to processing we base on legitimate interests, including error reports. Write to privacy@avcpp.com. We will then stop, unless we have compelling legitimate grounds that override your interests, rights and freedoms, or need the data to establish, exercise or defend legal claims, and we will tell you which applies.

For the data an agency puts into the platform, the agency is the controller and decides the legal basis (Section 8.1).

4. Google User Data and Limited Use

4.1 The Google Scopes We Request and Why

We request the scopes below when you sign in with Google or when you connect the relevant Google service. Google's consent screen is the authoritative record of what you granted, and you may decline any scope — declining disables only the feature that needs it. The Google Drive scope is never part of sign-in; it is requested separately, on demand, and only when you pick a file from Drive.

Google service & scope	Google classification	What we access	Why NX6 OS needs it
Sign-in — openid, email, profile	Not sensitive	Your Google account ID, email address, name, and profile picture	Create and authenticate your NX6 OS account
Google Business Profile — business.manage	Not sensitive	The locations you manage, their business information, posts, reviews, review replies, and media	Publish local posts, read and reply to reviews, and report on local performance for the locations you connect
YouTube — youtube.upload	Sensitive	Write access to upload videos to your channel	Upload and schedule the videos you create in NX6 OS
YouTube — youtube.force-ssl	Sensitive	Your channel identity, video metadata, and comments on your videos	Required to complete uploads, set video metadata, and read/reply to comments in the unified inbox
YouTube Analytics — yt-analytics.readonly	Not sensitive	Aggregated performance metrics for your channel and videos	Display your YouTube analytics inside NX6 OS
Google Analytics — analytics.readonly	Sensitive	Your list of GA4 properties and read-only report data	Show website traffic and conversion reporting next to your social results
Google Search Console — webmasters.readonly	Not sensitive	Your verified sites and read-only search analytics (queries, clicks, impressions, positions)	Show search performance and keyword reporting
Google Merchant Center — content	Sensitive	Your Merchant Center account, product feed, and product-status data	Diagnose product-feed problems and surface product data for commerce features
Google Calendar — calendar.events	Sensitive	Events on your primary Google Calendar	Show them beside scheduled posts, and create, edit or delete events you ask for
Google Drive — drive.file (separate, on-demand grant)	Not sensitive	Only the individual files you pick in the Google Picker	Import a specific photo from your Drive into a post

4.2 Our Limited Use Commitments

For all data we obtain from Google APIs, including data obtained under the sensitive scopes above:

• We use it only to provide and improve the user-facing features described in this policy and visible in the product.
• We do not transfer it to others except (a) as necessary to provide or improve those features, (b) for security purposes such as investigating abuse, (c) to comply with applicable law, or (d) as part of a merger or acquisition after obtaining your explicit consent. Section 7 lists every sub-processor that can receive it.
• We do not use it for advertising, ad targeting, ad measurement, or to build or enrich advertising or marketing profiles, and we do not sell it.
• We do not use it to develop, improve, or train generalized artificial-intelligence or machine-learning models.
• We do not allow humans to read it, except (a) with your explicit consent for specific messages or records, (b) where necessary for security purposes such as investigating abuse, (c) to comply with applicable law, or (d) where the data has been aggregated and anonymized.

4.3 AI Features and Google User Data

Some NX6 OS features send data obtained from a connected Google service to an AI model to produce the output you asked for — for example, drafting a reply to a Google review, turning a review into a social post, or writing a caption for a photo you selected from Drive. This happens only when you invoke that feature, only with the specific content the feature needs, and only to return the result to you. That content is not used to train generalized AI or machine-learning models. The AI providers we use are listed in Section 7.

4.4 YouTube API Services

NX6 OS uses the YouTube API Services to publish videos to the channels you connect, show your channel's videos and analytics, and read and reply to comments on your videos in the Unified Inbox. By using NX6 OS's YouTube features you agree to be bound by the YouTube Terms of Service. Google's own handling of your information is described in the Google Privacy Policy (http://www.google.com/policies/privacy).

What we access, store and share.

• Channel identity (channel ID, name and thumbnail) — stored with your connection so we can show which channel a post goes to. We re-read it from YouTube at least every 30 days; if it cannot be re-read for 30 days (for example because you revoked access), it is deleted.
• Videos you publish through NX6 OS — we keep the title, description and settings you entered. The video ID and link YouTube returns are kept for 30 days so you can open the video from your post history; after that, or as soon as you disconnect the channel, they are deleted and the post stays in your history as published.
• Analytics — channel and video analytics (views, watch time, subscribers) are read live from YouTube each time you open them and are not stored. For videos NX6 OS created and published for you, we store the view, like and comment counts YouTube reports, re-read daily for up to 90 days after publishing; they are deleted 30 days after the last re-read. We never calculate new or derived metrics from YouTube data, and YouTube data is never sent to an AI model.
• Comments — read live from YouTube each time you open the Unified Inbox. We do not store comment text; a reply you write is sent to YouTube and not kept by us.

YouTube data is used only to provide these features to you and your team inside your NX6 OS workspace. We do not sell it, use it for advertising, or share it with third parties other than the service providers listed in Section 7 that host it on our behalf. NX6 OS does not place advertising cookies on its pages.

4.5 Revoking Google Access and Deleting Google Data

You can revoke NX6 OS's access to your Google account at any time at the Google security settings page, https://security.google.com/settings/security/permissions (it opens myaccount.google.com/permissions). You can also disconnect a Google service, or a YouTube account, from Account → Connections (left sidebar) inside NX6 OS, which deletes the stored tokens and the data we hold for that connection. See our Data Deletion Instructions for full account deletion.

YouTube data deletion timelines. When you disconnect a YouTube channel in NX6 OS, or ask us to delete your YouTube data, the channel details and video links we hold for it are deleted within 7 days (a daily clean-up job removes them at its next run). When you revoke access from the Google security settings page instead, we detect the revoked authorization and delete the YouTube data related to you within 30 days. To ask for deletion by email, write to privacy@avcpp.com.

5. Meta Platform Data (Facebook & Instagram)

5.1 Data We Access

For each Facebook Page or Instagram Business/Creator account you connect, NX6 OS may access:

• Page & account identity: Page/account name, ID, profile and category metadata, and the list of Pages you manage (so you can choose which to connect)
• Published content: Posts, photos, videos, and captions on the connected Page/account, and the posts NX6 OS publishes on your behalf
• Engagement & insights: Reactions, likes, comments, shares, reach, impressions, and other performance metrics, used to show you analytics
• Comments, and who wrote them: Comments on your Page posts, each with the name and profile picture of the person who wrote it, shown in the Inbox so you can see engagement in one place. They are read from Facebook each time you open the Inbox; NX6 OS does not store them. NX6 OS does not send replies to Facebook or Instagram comments today.
• Ad accounts: The ad accounts shared with the connected login (name, ID and currency) and their reporting figures. If you use Boost, the paused campaign, ad set, creative and ad it creates; their IDs and the budget you chose are kept in your workspace’s audit log
• Access tokens: The OAuth access tokens that authorize the above, stored encrypted (see Section 10)

5.2 How We Use Meta Platform Data & the Permissions We Request

Permission	Why NX6 OS uses it
public_profile	Identify the Facebook account that connected, by name and account ID
pages_show_list	List the Facebook Pages you manage so you can pick which to connect
pages_read_engagement / pages_read_user_content	Read your Page's posts and engagement to display analytics and your content history
pages_manage_posts	Publish and schedule posts to your Page on your behalf
read_insights	Show Page-level performance insights
ads_read	Show reach and spend reporting for the Meta ad accounts shared with the connected login (read-only)
ads_management	Create a paused ad from a post you have already published, in the ad account you choose (“Boost”). Everything it creates is paused: NX6 OS never starts, changes or stops spending, and the ad runs only if you activate it yourself in Meta Ads Manager
business_management	Access Pages and Instagram accounts managed within your Business Manager
instagram_basic	Identify your connected Instagram Business/Creator account and read its media
instagram_content_publish	Publish and schedule posts to your Instagram account on your behalf
instagram_manage_insights	Show your Instagram performance analytics

AI drafts. The engagement figures of the posts NX6 OS published for you are also used to rank which of your own topics did best. When you ask NX6 OS to draft content, that ranking — the names of your topics and of the platforms, never the figures and never anyone's personal information — is included in the request to the AI provider listed in Section 7. NX6 OS does not use Meta Platform Data to train AI or machine-learning models.

5.3 What We Do Not Do

• We do not sell, rent, or license your Meta Platform Data.
• We do not use it for advertising targeting or to build cross-site profiles.
• We do not access data for Pages or accounts you have not explicitly connected.
• We do not share it with third parties except the sub-processors in Section 7 needed to operate the service.

5.4 Revoking Access & Deleting Meta Data

You can disconnect Facebook and Instagram at any time from Account → Connections (left sidebar) in NX6 OS. Disconnect removes every Facebook login you connected, together with the Pages and Instagram accounts it carried, and deletes the stored tokens immediately. Engagement figures already recorded on posts you published stay part of your own content history until you close the workspace or ask us to remove them. To delete all data, see our Data Deletion Instructions.

You can also revoke access directly on Facebook at Settings & Privacy → Business Integrations, where the app is listed as NX6 OS+. When you revoke access there without disconnecting in NX6 OS, NX6 OS finds out the next time a post is sent with that login: Facebook refuses it, and the login is shown as needing a reconnect. Thirty days later a daily clean-up job asks Facebook once more. If Facebook still refuses the login, its record — your Facebook name and picture link, the list of Pages and Instagram accounts, and the tokens, which no longer work — is deleted; if Facebook accepts it again, the login is kept. The job covers members of a workspace. To have a login removed sooner, or if you no longer belong to a workspace, disconnect in NX6 OS, delete your account, or write to privacy@avcpp.com.

Our use of Meta Platform Data complies with the Meta Platform Terms and Developer Policies.

6. How We Share Information

6.1 Connected Platforms

When you publish or schedule content, NX6 OS sends that content to the platform you selected (for example Facebook, Instagram, LinkedIn, YouTube, Google Business Profile, Pinterest) through its official API, on your instruction. The Canva connection works in the opposite direction: when you connect your own Canva account, NX6 OS fetches the design and media you choose to import, through Canva's official API, on your instruction.

6.2 Within Your Agency's Tenant

Data you enter is visible to other users of the same tenant according to the role and client/store scope the agency assigned them. Agencies decide who can see which client's data; we enforce that boundary server-side.

6.3 Destinations You Configure

Some features send workspace data to a place the agency chooses. Nothing is sent until an owner or admin (for website widgets, also a manager) sets the destination up, and it stops when they remove it:

• Slack and Microsoft Teams notifications. Notification content, such as review text, client and store names, and approval details, is posted to the webhook URL the agency enters.
• Outbound webhooks. Signed event messages about the agency's own workspace are sent to the URLs the agency registers.
• REST API. Anyone holding an API key the agency created can read that workspace's stores, clients, scheduled posts and approvals, limited to the key's scopes. The API does not change data.
• SCIM. The agency's identity provider can read, invite, update and remove the workspace's members, using a token the owner created.
• Website widgets. When a widget is turned on for a location and its code is placed on the business's website, anyone who visits that website sees the location's photos, Google posts, FAQ answers and newest five-star Google reviews. A review is shown with the reviewer's first name and last initial and the words of the review, shortened. NX6 OS keeps a copy of those reviews to serve the widget and does not show a copy older than 30 days. The business-details block for the same website publishes the business's own name, address, phone, opening hours, service areas and FAQ answers, and no reviews. Turning a widget off stops it; a copy already cached by the website's visitors or our content network can show for up to ten minutes.

These destinations are not our sub-processors. The agency chooses them and is the controller for each transfer; the receiving service's own terms and privacy policy apply to the data once it arrives.

6.4 Sub-processors

We share data with the vendors listed in Section 7, strictly to operate the service.

6.5 Legal Requirements

We may disclose information if required by law or to respond to court orders, subpoenas, or law-enforcement requests; to protect our rights or property; or in an emergency involving safety.

6.6 Business Transfers

In a merger, acquisition, or sale of assets, your information may be transferred to the acquiring entity, subject to this Privacy Policy. Data obtained from Google APIs will be transferred only after obtaining your explicit consent, as required by the Limited Use requirements.

7. Sub-processors

These are the third parties that process personal data on our behalf. The list is current as of the "Last Updated" date at the top of this page. We will update this list, and notify agency account owners by email, before adding a new sub-processor that handles customer data.

Sub-processor	Purpose	Data it can receive	Processing location
Google Cloud / Firebase (Google LLC) — notice	Hosting, authentication, database, file storage, serverless functions, secret management, logging. Also abuse protection (reCAPTCHA through Firebase App Check) on every visit, Google sign-in (Google Identity Services), and page-speed measurement (Firebase Performance Monitoring) only if you choose "Allow diagnostics" (Sections 9 and 13)	All platform data, including account data, content, and connected-platform data. reCAPTCHA also receives your IP address and browser and device signals	United States (us-central1)
Google — Gemini and Veo AI APIs — privacy	AI text, image, and video generation	The prompts, images, and source content you submit to an AI feature	Gemini: provided by Google LLC (United States), no region guarantee (Section 14). Veo: United States (us-central1)
Luma AI — privacy	Video generation (fallback provider)	The prompts and reference images you submit to a video feature	United States
Sentry — privacy	Error monitoring (always). Session replay and performance tracing only if you choose "Allow diagnostics" (see Section 9)	Error reports with page URLs, browser and device details, and your user ID only (no email address or name). If you allow diagnostics: session recordings with all text masked, and page-speed measurements	United States
Stripe — privacy	Subscription billing, checkout, and payment processing	Billing name, email, address, payment method, and transaction history. Stripe — not NX6 OS — holds your card details	United States
Resend — privacy	Transactional email delivery (invitations, approval requests, alerts, notifications)	Recipient email address and name, and the contents of the message	United States
Outstand	Pinterest publishing only	The post text and media you schedule to Pinterest, and your Pinterest account identifiers. Your Pinterest credentials are held by Outstand, not by us	United States
Canva — privacy	Importing designs from a connected personal Canva account	Your Canva account identity, and the design and exported media you choose to import. Your Canva credentials are held by Canva, not by us	United States

Google Cloud, Sentry, Stripe, Resend, and the AI providers may in turn use their own infrastructure sub-processors, as described in their respective policies.

8. Controller, Processor, and Data Processing Terms

8.1 Roles

• The agency is the controller for the personal data it and its clients place in the platform: client and store records, staff contact details, content, connected-account data, the customer contact details it supplies for review requests, and the photos sent in to its photo library. The agency decides what to collect, from whom, and why.
• NX6 OS is the processor for that data. We process it only on the agency's documented instructions — which, in practice, are the actions the agency and its users take in the product — plus what is required to keep the service secure and to comply with law.
• Where an agency resells NX6 OS to a client under its own brand, and the client is the one who determines the purposes of the processing, the agency acts as processor for that client and NX6 OS acts as a sub-processor. The agency is responsible for having a lawful basis and appropriate terms in place with its client.
• NX6 OS is an independent controller only for our direct relationship with the account holder: registration details, billing records, support correspondence, and security and audit logs.

8.2 What We Commit To as a Processor

• Process personal data only on the controller's instructions, and tell the controller if we believe an instruction breaks the law.
• Keep the people who handle personal data bound by confidentiality.
• Apply the security measures in Section 10.
• Use only the sub-processors listed in Section 7, under written terms no less protective than these, and give notice before adding a new one.
• Help the controller respond to data-subject requests and, where applicable, to data protection impact assessments and regulator enquiries.
• Notify the controller without undue delay after becoming aware of a personal data breach affecting their data.
• Delete or return personal data on termination, subject to the retention rules in Section 11 and any legal retention obligation.
• Make available the information reasonably needed to demonstrate compliance with these obligations.

8.3 Getting a Data Processing Addendum

Agencies that need a signed Data Processing Addendum — including the EU and UK Standard Contractual Clauses for transfers out of the EEA, UK, or Switzerland — can request one from legal@avcpp.com. We do not currently publish a self-serve DPA; we will send you one to sign. Until a DPA is signed, this Section 8 states the terms on which we process controller data.

9. Analytics, Error Monitoring, and Session Replay

We use Sentry to find and fix crashes. Error reports are always sent to Sentry. They include the page URL, browser and device details, a stack trace, and — when you are signed in — your user ID only, never an email address or name. We remove any email address or name before a report leaves your browser. Error reports contain no screen recording. We send them on the basis of our legitimate interest in finding and fixing faults, and you can object as Section 3.1 explains.

Session recordings and page-speed measurements are optional. They are sent only after you choose "Allow diagnostics" in the privacy banner. Until you choose, and if you choose "Essential only", neither runs. Specifically:

• Session recordings (Sentry Session Replay) reconstruct what happened in the browser during a session: page structure, navigation, clicks, scrolls, and network timings, played back like a video. Roughly 10% of sessions are recorded at random, and a session is recorded whenever an error occurs. A recording is never made on the shared approval, report, review, and photo-upload pages that anyone can open without an account.
• In production, all text is masked and all media is blocked before a recording leaves your browser, so the words you type and read, and the images on screen, are not transmitted. What is captured is the shape of the page and your interactions with it. Like error reports, recordings carry your user ID only, never an email address or name.
• Page-speed and performance measurements (load times, network timings, and the Core Web Vitals) are sent to Sentry and to Google (Firebase Performance Monitoring).
• These are not used for marketing, profiling, sales, or monitoring of individuals. They are used only to diagnose faults and slow pages.

You can change your choice at any time with "Privacy choices" in the footer of the website (also in Settings). Choosing "Essential only" stops new recordings and measurements. To have recordings already sent to us deleted, email privacy@avcpp.com.

10. Data Security

• Encryption in transit and at rest: TLS in transit; encryption at rest as provided by Google Cloud for Firestore, Cloud Storage, and backups
• Token encryption: Connected-platform OAuth tokens are encrypted with AES-256-GCM before storage, with keys held in Google Cloud Secret Manager
• Authentication: Firebase Authentication, with app-integrity verification via Firebase App Check
• Access control: Role-based access control enforced server-side, with per-client and per-store scoping so a user only reaches the clients they were granted
• Secrets management: API keys and credentials in Google Cloud Secret Manager, never in client-side code

No system is perfectly secure, and we do not claim otherwise. We hold no third-party security certification — we are not SOC 2, ISO 27001, or HIPAA certified, and NX6 OS is not intended for protected health information or other special-category data.

11. Data Retention and Backups

Data Type	Retention
Account information	Until account deletion is completed (a deletion request has a 30-day cancellation window before it is executed)
Connected-platform tokens	Deleted when you disconnect the account, or when your NX6 OS account is deleted. A Facebook login that Facebook has refused for 30 days is deleted by a daily clean-up job (Section 5.4)
Cached platform data (engagement figures on your published posts)	Kept with your content until the workspace is closed, or removed on request within 30 days
Cached YouTube API data	Refreshed or deleted within 30 days, and on disconnect
Generated & published content	Until you delete it, or until account deletion
Review-request records (a customer's name and email address, the staff member and service entered for them, and whether the request was sent, its review link was clicked, it bounced, or the customer asked for no more requests)	180 days from the request
Review-request repeat-send markers (kept as a salted hash, not the address)	30 days
Queued copies of emails we send, including review requests	30 days
"Stop" requests from a customer who unsubscribed from review requests (kept as a salted hash, so we can keep honoring the request)	Until the workspace is closed
Unsubscribes from the monthly client report and from the emails that ask a business what is new (a salted hash of the address, never the address, with when and how the person unsubscribed)	Until the person subscribes again, or the workspace is closed
Unsubscribe links in those emails (the kind of email, a salted hash of the recipient's address, and the sender name shown on the unsubscribe page)	400 days
"Stop sending these" requests from the emails that ask a business what is new	400 days
Photos and clips sent in to a photo library	Until the business deletes them, or until account deletion. A clip that no video used is deleted 30 days after it arrived
Usage and audit logs	Up to 6 months
Support requests sent from inside NX6 OS (your address, the subject and the message)	2 years after the last change to the request
Business Profile change history (which listing field changed, its old and new value, where the change came from, and the member who made it)	400 days
Free AI allowance record (a SHA-256 hash of the sign-up email address, never the address, with when each free allowance was given)	Each allowance counts for 2 years. The hashed record is kept after the account is deleted, so the same person cannot claim the free allowance again under a new account (legitimate interests, Section 3.1). We do not yet delete it by age
Error events, and session replays if you allowed diagnostics (Sentry)	Per Sentry's retention for our plan — currently up to 90 days
Payment and invoice records	7 years (tax and accounting requirement)

Backups. We take a daily export of the database to storage inside the same Google Cloud project, so we can recover from a failure. A record you delete can survive in an export taken before the deletion until that export is removed. Daily exports are deleted after 30 days (the cleanup runs weekly, so an export can exist for up to about 37 days), with a 90-day storage backstop. Deleted records also remain recoverable for 7 days through the database's point-in-time recovery, which we use only to recover from a failure. If you need confirmation that a specific record has been purged from backups, ask us at privacy@avcpp.com and we will action it. We do not offer a recovery-time guarantee.

12. Your Rights and Choices

• Access & Export: Request or download a copy of your personal data (Settings → Privacy & Data)
• Correction: Update inaccurate information
• Deletion: Delete your account and data — see Data Deletion Instructions
• Disconnect: Remove any connected platform from Account → Connections (left sidebar), or revoke Google access at myaccount.google.com/permissions
• Diagnostics choice: Turn session recordings and page-speed measurements on or off at any time with "Privacy choices" in the footer or in Settings (Section 9)
• Communication preferences: A customer who receives a review request can stop further requests from that business with the link in the email. Reminders about drafts waiting for approval can be switched off in Automations ("Email me about expiring drafts"), and the monthly client report and the emails that ask a business what is new each carry their own unsubscribe link; the agency that set up a report can also switch it off. Account, billing and AI-budget alerts go to a workspace's owner and admins while the workspace is open. You can opt out of any marketing email from us with the link in it, or by writing to privacy@avcpp.com

If your data was put into the platform by an agency, we will normally refer your request to that agency as the controller, and assist them in fulfilling it.

13. Cookies and Local Storage

We use essential cookies and browser local storage for authentication, session management, and security, plus functional storage for your preferences (such as the client you last had selected, and your "Privacy choices" answer). We do not use advertising cookies, we do not run third-party ad networks, and we do not sell personal information. Sentry sets no advertising identifiers. If you choose "Allow diagnostics", session recording keeps a session identifier in your browser's session storage for that visit. You can clear or block this storage in your browser, but doing so will sign you out and may break parts of the product.

Google services that run in your browser. reCAPTCHA by Google, through Firebase App Check, runs on every visit to protect the service from abuse. It stores an item named _grecaptcha in your browser and sends Google your IP address and browser and device signals, which Google handles under the Google Privacy Policy. Google Identity Services loads from Google when you sign in with Google.

14. Where Your Data Is Stored and International Transfers

NX6 OS runs on Google Cloud Platform in the United States (region us-central1), and AI video and music generation on Google's Vertex AI is set to the same region. AI text and image requests go to Google's Gemini API. Google LLC, a US company, provides it, but the API gives us no setting to fix where a request is processed, so we do not guarantee that Gemini requests are processed in the United States. The other sub-processors in Section 7 process data in the United States, as listed there. We do not currently offer EU, UK, or any other regional data residency, and we do not offer a self-hosted or on-premises deployment.

If you are in the EEA, UK, or Switzerland, your data will therefore be transferred to and processed in the United States, and Gemini requests wherever Google processes them. For those transfers we rely on the Standard Contractual Clauses, which we will execute as part of the Data Processing Addendum described in Section 8.3.

15. Children's Privacy

NX6 OS is not intended for users under 18. We do not knowingly collect information from children. If you believe a child has provided information, contact privacy@avcpp.com and we will delete it.

16. California (CCPA/CPRA) & European (GDPR) Rights

California residents may request the categories and specific pieces of data we collect, request correction or deletion, and opt out of the sale or sharing of personal information — we do not sell or share personal information as those terms are defined by the CCPA/CPRA — without discrimination for exercising those rights. EEA/UK residents have rights of access, rectification, erasure, restriction, portability, and objection, and may lodge a complaint with their supervisory authority. To exercise any right, contact privacy@avcpp.com or our privacy contact at dpo@avcpp.com. We have not appointed a statutory Data Protection Officer or an EU/UK Article 27 representative; the same address reaches the person responsible for privacy at our company.

17. Changes to This Policy

We may update this Privacy Policy. We will update the "Last Updated" date and, for material changes, notify you by email or in-app. Continued use after changes constitutes acceptance.

18. Contact Information

19. Additional Resources

• Terms of Service
• Data Deletion Instructions
• Security and Vulnerability Disclosure
• Google API Services User Data Policy
• YouTube Terms of Service
• Google Privacy Policy
• Google security settings — revoke app access
• Meta Platform Terms
• NX6 OS Application
• Customer Support