Privacy policy

nith LLC, a limited liability company registered in Wisconsin, United States ("nith," "we," "us," or "our"), operates the EasyAsPie platform. Our mailing address is To be confirmed: registered address. For privacy questions and requests, contact hello@nith.app.

This policy explains how we handle personal information when you visit our own websites, create or use an EasyAsPie account, communicate with us, or use an enabled nith service such as our dashboard, AI assistance, community, or Bug Center. Feature-specific descriptions apply when the feature is available and used.

Our customers use nith to operate their own websites and businesses. A customer generally determines why it collects information through its site, lead forms, booking, shop, client records, and contracts. We process that information for the customer under its instructions and our agreement. The customer's own privacy notice explains its use of that information. A customer's agency may also administer its site and information. This policy does not replace the customer's notice or authorize a customer to collect information it is not otherwise entitled to collect.

We separately determine the purposes of processing information needed to operate our own business, including account administration, our billing, platform security, support, and our marketing. Our role depends on the particular activity; information does not become ours to use for unrelated purposes merely because it passes through nith.

We receive information directly from you, from a customer or agency that invites or adds you, from your browser or device, and from the service providers and integrations involved in the features you use.

Please provide only information needed for your request. General enquiry forms and AI tools are not designated channels for medical records, payment card details, passwords, or other restricted information. A warning or screening feature cannot prevent all sensitive information from being submitted.

We use information to:

• Create and administer accounts, verify contact details, manage access, and support collaboration.
• Host, display, organize, and deliver content and the customer features described above.
• Process our subscriptions and charges, keep financial records, reconcile usage and credits, and assist with payment issues.
• Send operational messages, such as verification and password-reset emails, invitations, lead alerts, order and contract notices, billing notices, and service communications.
• Provide requested AI features and perform configured safety or abuse screening.
• Investigate problems, respond to support requests, maintain security, limit misuse, and enforce our agreements.
• Understand use of our own public pages and improve the service. For customer-site analytics, the allocation of responsibilities is explained in the customer's notice and our agreement.
• Send optional marketing communications through the channels for which the applicable permission or other legal basis exists.
• Meet legal obligations, respond to valid legal process, and establish, exercise, or defend legal claims.

Jot and other model-assisted features use OpenAI. Depending on the task, a request can include your message, conversation context, page or document text, business profile, selected records, design instructions, media descriptions or URLs, or an image supplied for an image task. A site-generation request that uses image URL metadata does not necessarily send the image's pixels; image editing and other image-aware features can process image content.

Where configured, nith also uses TypeSafe AI's Jev through the Vercel AI Gateway for bounded evaluations such as intent routing, reviewing proposed changes or designs, setup advice, selecting stock imagery, and screening form text. The gateway and model provider receive the material included in that evaluation. The data involved depends on the feature; it is not limited to requests typed into the Jot chat box.

In particular, when health-information screening is enabled, text and long-text form answers may be sent to an AI provider before the enquiry is stored or forwarded. Separate email, phone, and other non-text fields are excluded from that screening payload, but personal or sensitive information entered within the prose can still be sent. A detected submission may be refused with an invitation to edit it or contact the business directly. The screening may be unavailable or inaccurate, and does not make the form suitable for health information.

We retain relevant conversations, output, task records, and usage information in nith to support the service. Provider processing is also subject to the arrangements and settings applicable to that provider. To be confirmed: ai provider retention and training disclosure. This policy does not promise that selecting a non-storage API option eliminates every provider log or copy.

Automated screening and access controls can reject submissions or limit activity. If you believe a decision has prevented a legitimate request, contact the relevant business or hello@nith.app. To be confirmed: automated decision rights disclosure if required.

Studio collaboration and guest review. When you join a shared Studio session, other authorized participants can see your display name, profile photo, selected block, text selection, pointer and the part of the page you are viewing. Draft changes, including unpublished content, are shared with participants in the relevant page or custom header/footer session through our collaboration service hosted on Railway. Cursor, selection and viewport information is transient session information and is not retained as page content or sent to an AI provider by the collaboration feature. Drafts and shared edit history are retained with the page or design, subject to deletion and backup practices.

A temporary guest link allows anyone holding it to view the selected page's unpublished draft and live edits without an account. It does not grant editing or publishing access. Links expire and can be revoked; an existing connection can take up to 60 seconds to lose access. Guest-link records include the creator, page, timestamps and a hashed token. The full link may appear in browser history or infrastructure request logs. Review comments contain the comment, block reference, author or guest label and relevant account/link reference. They are visible to other reviewers of that page, including holders of an active guest link, and remain after a link expires. Page or site deletion removes the associated comment and guest-link records, subject to backups. There is no separate scheduled purge promised for expired links or comments.

Profile photos. An optional account photo is resized and stored as a WebP image after embedded metadata is removed. The uploaded original and crop settings are not retained. Your photo appears across nith and is accessible to anyone who has its image URL. Replacing or removing it deletes the previous stored photo; account deletion removes it, subject to existing backups. Browser or delivery caches may retain it for up to five minutes. Photos are not attached to Jot prompts by this feature.

Saved Jot context and suggestions. We retain bounded notes derived from conversation messages, conversation titles, reply durations and suggested follow-up prompts to help continue your work. Relevant earlier excerpts and page observations may accompany later requests to the existing AI provider. Generating follow-up suggestions can send the latest request and reply, page address and available tool names to that provider. Suggestions and their evidence are private to the applicable account and site; conversation records follow that conversation's private or shared access. These records are removed with the relevant conversation, account or site according to the feature, subject to backups. Local identity placeholders resolve your account name, role and permission labels in the interface; this mechanism does not send those profile fields to the model. Information you include in a message can still be processed as part of that message.

Only a conversation's owner can share it with authorized site teammates or revoke that sharing. Shared participants can read and continue the conversation using their own permissions. Revoking access does not remove copies already seen. Deleting a shared conversation removes the shared transcript for its participants, subject to backups. Conversations that use private account tools cannot be shared, and previously shared conversations cannot use those private tools.

Official community posts. A teammate authorized to post as nith team keeps their personal login and permissions. The forum records the actual posting account, personal forum identity, time and public post references for attribution and duplicate-send handling. Switching posting identity does not grant forum administrator powers. Public posts and replies remain visible under the forum's publication and moderation rules; operational attribution records are retained while the publishing integration is active.

Your organization, agency, or site team. Authorized members can access information according to their assigned permissions. A business or agency managing your workspace may control membership and access. EasyAsPie platform administrators can access customer workspaces for platform administration and support; staff impersonation is recorded.

Service providers. We use providers for hosting and delivery, databases, file storage, email, payments, phone verification, spam protection, and AI processing. The accompanying provider notice identifies the providers used for those purposes and distinguishes processors from recipients acting for their own purposes. Providers receive information relevant to the service they perform. Service providers.

Customer-selected recipients. A customer may send enquiry information to its chosen notification addresses or webhook destinations, connect payment or analytics services, or add scripts and embedded services. These recipients and their uses are determined by that customer's configuration and applicable agreements. Please consult the customer's notice.

Public audiences. Published pages and media, public community contributions, and an approved public version of a bug report may be visible to others. Bug reports begin private. The Bug Center allows a separate sanitized public version when the reporter permits publication; individual evidence files require separate staff review before public exposure. Security and privacy reports are excluded from publication through that workflow.

Legal and business recipients. We may disclose information where required by applicable law or valid legal process, or as reasonably necessary to protect legal rights and address fraud, abuse, or security incidents. If our business is involved in a merger, acquisition, financing, reorganization, or asset transfer, relevant information may be disclosed to the parties and advisers involved, subject to applicable law and appropriate confidentiality protections.

To be confirmed: sale sharing targeted advertising disclosure.

We use cookies and browser storage for sign-in, access to requested pages, interface preferences, and workspace functions. Some browser storage contains drafts, copied blocks, undo history, or upload metadata, rather than only appearance preferences. See our Cookie Policy for the inventory and controls: Cookie policy.

Our public pages and customer sites with analytics configured can load our self-hosted Umami service. Although the analytics integration is designed to operate without cookies, requests still involve technical information. Cookie-free operation does not by itself mean that no personal information is processed.

Customers may enable Google Analytics, Google Tag Manager, Meta Pixel, maps, outside forms, videos, chat tools, or other custom scripts. These can cause your browser to communicate directly with their operators. A video may load a third-party thumbnail before playback; provider code can load when playback begins. A customer's notice should identify its enabled services and the choices available to you.

To be confirmed: consent and opt out control description. To be confirmed: do not track and global privacy control disclosure.

We consider the purpose for which information was collected, the service and customer instructions involved, applicable legal requirements, unresolved disputes and security issues, and the technical steps needed to remove information from active systems and backups.

Customer content ordinarily remains available while the customer maintains it in the service. Archiving a record, hiding a site, cancelling a subscription, and deleting data are different actions. For example, archiving a lead keeps it for possible restoration; deleting that lead does not necessarily delete an associated booking or copies previously delivered by email or webhook. Financial, security, and legal records may remain when an account or site is removed, where an applicable retention purpose exists.

The following schedule describes our approved periods or criteria: To be confirmed: retention schedule url or text. Contact hello@nith.app about information you wish us to locate, return, correct, or delete. We will explain applicable exceptions and the effect on related services when responding to a verified request.

We use measures intended to protect information, including account authentication, permission checks, password hashing, session controls, and security logging. The measures appropriate to particular data and services can differ. No system or transmission method is completely secure.

Protect your credentials, review access granted to team members and connected tools, and avoid publishing information you intend to keep confidential. Making a page private or password-protected does not necessarily make a media URL used elsewhere private. Report a suspected security issue to To be confirmed: security contact.

nith is operated by a company registered in United States. Our providers may process information in other countries depending on the service, deployment, and support arrangements. The relevant countries and, where required, transfer safeguards are described at To be confirmed: transfer information url or text. Where applicable, you may contact hello@nith.app for information about safeguards or a copy subject to lawful redactions.

You can use available account controls to update supported profile information and manage sessions. To request access, correction, deletion, a copy of information, or another privacy action, contact hello@nith.app or use data deletion and privacy request instructions. We may request information reasonably needed to verify your identity and authority. An authorized agent may act for you where applicable law permits, subject to appropriate verification.

Depending on the law applicable to you and the processing, you may have rights to access, correct, delete, or obtain a portable copy of information; restrict or object to certain processing; withdraw consent; or opt out of specified sales, sharing, targeted advertising, or automated decisions. Applicable exceptions can limit a request. Withdrawal does not invalidate processing that was lawful before it. We respond within applicable legal time limits and do not unlawfully discriminate against you for exercising a protected right. Where required, a denial will explain how to appeal through To be confirmed: privacy appeal channel. You may also complain to the competent regulator where that right applies.

If the request concerns information held for a customer, such as a form answer, booking, order, or agency contract, contact that customer first. We can help identify the appropriate customer and assist it according to our agreement and applicable law. This does not prevent you from contacting us about our own processing.

Marketing emails, when offered, include an unsubscribe mechanism. Operational messages needed for your account, transactions, or security are separate from optional marketing.

The platform is intended for business use and is not directed to children under To be confirmed: minimum account age. If you believe a child has provided information in circumstances requiring parental authorization, contact hello@nith.app. A customer's site may serve a different audience; that customer is responsible for its collection practices and any required child-specific notice and permissions. A contractual age restriction alone does not establish that children cannot use a service.

To be confirmed: regional notices required for actual launch markets.

We may update this policy as our practices change. The published version will show its effective date. We will provide additional notice or obtain consent where applicable law requires it; continued use alone does not supply consent where affirmative permission is required.

nith LLC
To be confirmed: registered address
Privacy: hello@nith.app
Support: hello@nith.app