Privacy Policy | here.now

What we collect

We collect the minimum information needed to operate the service:

Email address - used for authentication, essential account/service messages, and occasional product announcements (which you can unsubscribe from).
Google profile information - if you sign in with Google, we receive your name, email address, and profile picture from Google. We keep only the email address and the profile picture URL (see "Google sign-in data" below).
IP address - stored temporarily for anonymous publishes to enforce rate limits. Cleared when a publish is claimed or expires.
Uploaded files - the content you upload to Sites and Drives is stored and served according to the access settings described below.
Workspace membership data - if you join a workspace, we record your membership, role, and how and when you joined.
Generated Site metadata - bounded excerpts from published files may be processed by a third-party AI model to generate owner-facing display names, display descriptions, search metadata, and related Site metadata. Workspace admins can turn this off for their workspace (see below).
Support chat - if you use the in-dashboard support assistant, your messages are processed by a third-party AI model to generate answers, along with limited account context (your account email, your plan, your Sites' names and access settings, and your workspace names and roles). We retain support chat transcripts to improve the product and our documentation.
Editor - if you use the Editor, the in-dashboard editor with an embedded agent, the messages you send, images you attach, and the contents of the Site you are editing are processed by a third-party AI model provider (OpenRouter and the upstream model you pick) to carry out your requests. We store your Editor conversation, draft, and the agent's notes about the Site so you can continue across sessions, and we record usage and error telemetry about Editor sessions, including a short excerpt of each message, to keep the product working. We do not use your content to train AI models.
Site request metadata - used to provide first-party analytics to site owners, including request path, referrer domain, coarse country, status class, content type, known crawler classification, and daily privacy-preserving visitor hashes.

What we do not collect

We do not use cookies for tracking or advertising.
We do not sell or share your information with third parties for marketing purposes.

How we use your data

Email addresses are used for authentication, account access, essential service/onboarding messages, and occasional product announcements with an unsubscribe link. We do not share your email with third parties for marketing.
IP addresses are used solely for rate limiting anonymous sites and are not retained after the site is claimed or expires.
Uploaded files are stored and served at their assigned URL according to their access settings.
When AI metadata generation is enabled, bounded published-file excerpts are sent to a third-party AI model solely to generate Site metadata for dashboard, search, profile, API, and related product surfaces. We do not use your content to train AI models. Workspace admins can disable this for all of their workspace's Sites in workspace settings; manually set titles and descriptions are unaffected and never involve an AI model.
Support chat messages and the limited account context described above are sent to a third-party AI model solely to answer your question. We do not use your messages to train AI models. Transcripts are retained for product improvement and are visible to the here.now team. The chat only processes data when you use it.
Editor messages, attached images, and the files of the Site being edited are sent to a third-party AI model provider solely to carry out your requests in that conversation. We do not use them to train AI models. The conversation, the draft, and the agent's notes are stored so the Editor can resume across sessions; usage and error telemetry about Editor sessions (including a short excerpt of each message) is visible to the here.now team.
If a workspace has auto-join enabled for an email domain, we match your verified email domain against those rules to offer you the option to join. Joining is always your action; we never add you to a workspace automatically.
Site request metadata is used for owner-facing analytics, abuse prevention, reliability, and debugging. Raw IP addresses are not exposed to site owners.

Google sign-in data

You can sign in to here.now with a Google account instead of a magic-link email. When you do, we request only Google's basic sign-in scopes (your email address and basic profile). We do not request access to Gmail, Drive, Calendar, Contacts, or any other Google service data.

What we access. Google sends us a signed identity token containing your email address, whether Google has verified it, your name, and your profile picture URL.
What we store. We store your email address (to identify or create your here.now account) and your profile picture URL (to show your avatar in the dashboard and to members of workspaces you belong to). We do not store your name or any other Google profile field. The picture URL is refreshed each time you sign in with Google.
How we use it. Google sign-in data is used only to authenticate you, to associate you with your existing here.now account by email, and to display your avatar. We do not use it for advertising, and we do not use it to train AI models.
Sharing. We do not sell Google user data and do not share it with third parties, except for the infrastructure providers that host our database on our behalf. Your avatar is visible to the members of workspaces you join, as described under "Workspace membership data".
Retention and deletion. Google sign-in data is retained for as long as your here.now account exists. You can ask us to remove your stored profile picture, or to delete your account and all data associated with it, by emailing hello@here.now. You can also revoke here.now's access at any time from your Google Account permissions page.

here.now's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Workspace membership data

Workspaces are shared accounts, so some of your information is visible to the people you share them with:

Workspace members and admins can see your email address, your role, and when you joined.
Workspace admins can invite people by email address; we send invite emails on the workspace's behalf.
Sites you publish into a workspace are visible to the workspace according to their access settings, and remain with the workspace if you leave. Leaving a workspace removes your membership-based access (any Site whose guest allowlist separately lists your email keeps admitting you as a guest until you are removed from it) but does not delete content you published for it.

Third-party services

We use third-party services for infrastructure, hosting, and email delivery. These services process data on our behalf and are governed by their own privacy policies.

Domain registration. If you buy a domain through here.now, we act as a reseller of name.com, an ICANN-accredited registrar operated by Identity Digital Inc. We provide name.com with the domain name and payment from our own account, and list here.now as the registrant contact on your behalf. Where a top-level domain or ICANN policy requires an end-user contact, we provide your account email address. name.com processes registration data as an independent controller under its privacy policy, and registration data is escrowed with the registry as ICANN requires. Payment card details are handled by Stripe and never stored by here.now. See the Domain Services Terms.

Data retention

Anonymous sites and their associated data are automatically deleted after 24 hours if unclaimed.
Claimed and authenticated sites are retained until you delete them.
If you delete your sites, all associated files are permanently removed from storage.
Deleting a workspace permanently deletes all of its Sites and their files. Removing a member revokes their membership-based access (per-Site guest allowlist entries admit them until removed separately) but does not delete content they published for the workspace.
Raw analytics events and daily visitor hash rows are retained for a short debugging window. Long-term analytics are stored as aggregated daily rollups.

Who can see your content

Visibility depends on the access settings you choose:

Public Sites - served to anyone who requests the URL. Personal site URLs are randomly generated and non-guessable; workspace label URLs (like deck.acme.here.now) are readable and should be treated as guessable.
Password-protected Sites - served to anyone who enters the password. Passwords are stored hashed; no one, including us, can read a password back.
Members-only workspace Sites - the default for workspace publishes. Served only to signed-in, active members of the owning workspace. Access ends promptly when a member is removed.
Restricted Sites - served only to viewers who verify an email address on your allowlist (on workspace-owned Sites, workspace members are also admitted).
Drives - private to your account and to accounts you explicitly share them with. Drive contents are never served at a public URL.

Public sites may be indexed by search engines. If you want to prevent indexing, you can include a robots.txt file or add <meta name="robots" content="noindex"> to your HTML. Gated sites are not served to crawlers.

Changes

We may update this policy. Changes will be reflected by updating the date at the top of this page.

Contact

Questions about privacy? Email us at hello@here.now.

here.now is operated by Beanstalk AI, Inc., a Delaware corporation, which is the data controller for the account and usage information described in this policy. You can also write to us at Beanstalk AI, Inc., 2261 Market Street STE 64851, San Francisco, CA 94114, United States.