Nu
Legal

Privacy Policy

This policy explains what data NUppel may process, why it is used, which providers may receive limited access, and what choices may be available to you.

Last updated: October 28, 2026

What we collect

Account, project, content, analytics, lead, appointment, and support-related data may be processed.

Why we use it

We use data for accounts, publishing, AI features, security, billing, support, and product improvement.

Who we share it with

Limited sharing may involve Supabase, Stripe, Vercel, OpenAI, Google AI, Google OAuth, Pexels, and domain services.

Your controls

You may have rights to access, correct, delete, object to, port, or manage certain communications.

scope

1. Introduction and scope

This privacy policy is a general explanation of how NUppel handles personal data across its website and product surfaces.

It applies to nuppel.com, account creation and sign-in flows, the AI website builder, editor, studio, blog tools, appointments, leads, analytics, hosting, and custom domain features.

Some features or integrations may also have supplemental checkout notices, disclosures, or contract terms that work alongside this policy.

who-it-applies-to

2. Who this policy applies to

NUppel works with more than one kind of user, and this policy is written to reflect that.

  • Individuals and businesses that create NUppel accounts
  • Authorized users acting on behalf of teams or companies
  • Visitors to NUppel marketing or product pages
  • End visitors who submit forms, messages, bookings, or appointments through sites built with NUppel

roles

3. Our role and responsibility framework

In some contexts NUppel acts directly for its own platform operations, while in others it provides infrastructure for customer websites.

For account, subscription, security, analytics, and support operations, NUppel may act as a controller, operator, or similar decision-maker.

When customers collect form, lead, booking, or appointment information through websites built on NUppel, NUppel may in some situations act more like a service provider or processor-like infrastructure layer.

Important

Site owners may also need to provide their own privacy notice and legal disclosures to their visitors.

data-we-collect

4. What data we collect

The categories of data we process depend on the features used and the type of interaction involved.

  • Account and identity data such as name, email, sign-in provider records, and profile data
  • Business and project data such as industry, site settings, language choices, publish state, and domain mappings
  • Billing and subscription metadata such as plan, status, invoices, and payment events
  • Content and media such as site copy, blogs, images, logos, favicons, and created assets
  • AI usage data such as prompts, generated drafts, and related product signals
  • Lead, form, and appointment data such as contact submissions, booking details, and internal notes
  • Analytics and device metadata such as IP, browser, device, country or city level signals, and performance events
  • Support and communication records such as emails, help requests, and bug reports

sources

5. Where we get data from

Data can come from multiple sources and is not collected in exactly the same way in every scenario.

  • Directly from you during signup, settings changes, payments, forms, and support requests
  • Automatically from logs, analytics events, error reports, and device or session signals
  • From connected third parties such as Google OAuth, payment providers, domain tools, or integrations
  • From customer-built websites when end visitors submit leads, forms, bookings, or appointments

purposes

6. Why we use data

We use personal data as reasonably needed to operate, secure, support, and improve the service.

  • Creating accounts, authenticating users, and managing sessions
  • Running the AI website builder, editor, studio, blog tools, leads, and appointments features
  • iublishing websites, hosting content, and supporting custom domain flows
  • Managing subscriptions, invoices, payments, and plan administration
  • iroviding support, troubleshooting, and service communications
  • Detecting abuse, fraud, unauthorized access, and security issues
  • Improving performance, reliability, and product quality
  • Meeting legal obligations and keeping necessary business records

ai-processing

7. AI, prompts, and automated processing

When you use AI features, prompts and related project context may be processed by model providers.

NUppel may send prompts and selected context to AI providers in order to generate website copy, blog drafts, creative suggestions, or similar outputs.

We recommend that you avoid placing unnecessary sensitive or special-category data into AI prompts.

Help assistant (Nu): what you write to the assistant is sent to OpenAI to produce the answer; if OpenAI is unavailable it may go to Anthropic or Google as a backup. ID, IBAN, card and passport numbers are hidden before sending. NUppel does not keep the conversation text; only technical records such as time, model, token count and cost are kept.

OpenAI is asked not to store request content as application data. OpenAI may keep logs for up to 30 days for abuse monitoring, and the cache of repeated fixed text may last up to 24 hours.

Our AI providers (OpenAI, Anthropic, Google) are in the United States, so what you write to AI features is transferred outside your country.

AI notice

Processing with OpenAI, Google AI, or similar providers may vary based on the active infrastructure and the rules of those services.

cookies-and-analytics

8. Cookies, analytics, and similar technologies

We may rely on storage, session, and analytics technologies to keep the product working and measure performance.

  • Necessary session cookies or similar storage to keep product state working
  • Analytics signals used for usage, performance, and debugging
  • Public site analytics metadata including IP-derived country or city, device type, and traffic events
  • Some preference controls that may be managed through browser or device settings

sharing

9. Who we share data with

Rather than framing this as data sale, we rely on a limited set of service providers and integrations to deliver the service.

  • Supabase for authentication, databases, storage, and backend infrastructure
  • Stripe for payment processing, subscription events, and invoicing records
  • Vercel for hosting, deployment, and domain infrastructure
  • OpenAI, Anthropic, and Google AI for AI-supported generation, the help assistant, and related flows (United States)
  • Google OAuth for social sign-in and identity-linked account flows
  • Pexels for certain media-search or stock-style content workflows
  • Meta (Instagram) and TikTok, only when you connect these accounts in Studio, to publish the posts you choose
  • Domain, DNS, and registrar providers for purchase, verification, or connection flows

Domain / third party

Some sharing happens because you initiate domain, payment, or integration steps that need third-party completion.

international-processing

10. International data transfers and hosting

Because NUppel depends on global SaaS infrastructure, data may be processed outside your country.

Depending on the hosting, deployment, and AI providers we use, personal data may be stored or processed on servers located in other regions.

We do not assume that every country provides the same legal framework and may rely on technical, administrative, or contractual safeguards where appropriate.

International processing

Cross-border processing patterns may change as providers or deployment regions evolve.

retention

11. Data retention

We do not apply one fixed schedule to all data; retention depends on business need, legal obligations, and technical reality.

  • Account data may be kept while the account remains active and for related management needs
  • Billing and transaction records may be retained for financial, operational, or legal recordkeeping
  • Support records, logs, and fraud signals may be retained for limited business and security purposes
  • Some backups, logs, or compliance records may remain for a period after a deletion request

security

12. Security

We do not promise absolute security, but we aim to use reasonable technical and organizational safeguards.

These may include access controls, encryption in transit, provider-level security measures, and role-based restrictions.

Payment card details are handled by Stripe or comparable payment providers rather than being stored in full by NUppel.

rights

13. Your rights and choices

Depending on applicable law, you may have certain rights over personal data related to you.

Not every right applies in every jurisdiction or every scenario; identity verification, security review, and legal exceptions may affect the response.

  • Request access to personal data
  • Ask for incorrect or incomplete information to be corrected
  • Request deletion of certain data
  • Object to or restrict certain processing in some scenarios
  • Request portability where applicable
  • Manage marketing preferences or opt out of certain communications

children

14. Children privacy

The service is not designed for children and we do not aim to knowingly collect personal data from them.

Depending on applicable law, the service may not be intended for users under 13 or under 16.

If we learn that data from a child has been collected inappropriately, we may review and take reasonable steps to restrict or remove it.

customer-sites

15. Customer websites and site-owner responsibility

Sites built on NUppel may create separate obligations for the site owner toward their own visitors.

If a customer enables forms, bookings, appointments, or lead capture on a NUppel-built site, that customer should assess what notices and legal text must be shown to their own visitors.

NUppel may provide the infrastructure for those flows, but that does not automatically make NUppel solely responsible for every statement or legal notice on the customer site.

Customer site responsibility

If your site collects forms, leads, or booking data, you may also need your own privacy notice and related legal disclosures.

social-connections

16. Instagram and TikTok connections

If you connect an Instagram professional account or a TikTok account in Studio, NUppel publishes the posts you choose on your behalf.

  • What we receive: the account ID, username, account type, and an access token that lets NUppel publish the posts you create or schedule. We do not read your direct messages, followers, or other account content.
  • Permissions: instagram_business_basic and instagram_business_content_publish for Instagram; user.info.basic, video.upload, and video.publish for TikTok.
  • Storage: access tokens are encrypted and kept only on our servers; they are never shown in the browser.
  • What we send: the images, caption, and hashtags of the posts you publish, delivered to Instagram (Meta) or TikTok at the time you choose.
  • You can disconnect at any time in Studio. Removing NUppel in your Instagram or TikTok settings also deletes the connection and its keys; Meta data deletion requests are completed immediately.
  • Published content is handled by Instagram and TikTok under their own terms and privacy policies.

support

17. Support conversations

When you write to us through the support chat, the contact form or e-mail, we keep the conversation to help you.

  • What we keep: your messages, your name and e-mail address, the dashboard page and project you were on when you wrote, your browser type, and your last few messages with the AI assistant.
  • We do not send your IP address to any third-party service.
  • Live support: when you open nuppel.com or your dashboard, our support team can see that you are on the site right now, the page you are on, how long you have been there, your IP address, your approximate location (city and country, from our hosting provider's request data — no third-party service), and your browser, device and language. If you are signed in, your name and e-mail address are shown too. Our team may write to you in the chat; when they do, the chat window opens. We use this only to help you.
  • Preview sites: the NUppel team may prepare a private preview site for a business or professional using only public professional information (name, profession, city, a short bio; given by them or read from the text of a profile screenshot). The site opens only with the private link sent to that person, is kept out of search engines, uses no photos of the person and its forms send nothing. The pages a visitor of that link opens, how long they stay and how far they scroll (no IP address, only the device type) are shown to our team. The person can close the preview at once with "I don't want a website"; closed or expired previews are deleted for good within 30 days and the raw visit records within 90 days.
  • Our support team may change your website to solve your problem; every change and note is logged with date and time and shown to you in the chat.
  • If you rate a conversation, the rating is used to improve our service.

changes

18. Changes to this policy

We may update this policy over time, and the latest version may become effective when published.

  • Material changes may also be communicated by email or in-product notice where appropriate.
  • The date shown near the top of the page reflects the latest revision.

contact

19. Contact and privacy requests

You can contact us in writing with privacy questions, data requests, or concerns about this policy.

Use the contact details below for access, correction, deletion, or general privacy requests.

Data controller: Birds Agent Co (United States).

Company legal name, postal address, or jurisdiction-specific details may be added once the final business structure is confirmed.

Privacy contact

Reach out here for privacy questions, data requests, or concerns about how NUppel processes personal data.