Privacy policy

Updated October 31, 2026

This page covers Folio by Zip1 at www.zip1.ai and the Folio app for iPhone, which shows this same site. Folio is run by Folio by Zip1 (“we”). Questions go to hossain6944@gmail.com.

In short

  • You can search without an account. Optional account registration asks for a name, email address, and password; signed-in accounts can save topic history across devices when account storage is configured.
  • Zip1 uses Vercel Web Analytics for aggregate visits to public pages, without third-party analytics cookies or custom account identifiers. Search questions, account views and private draft URLs are excluded; public article IDs and URL fragments are removed. Vercel may process timestamps, referrers, approximate location, browser and device information, with visitor-session identifiers discarded after 24 hours. Do Not Track and Global Privacy Control requests disable this analytics script. Counts cover only eligible public visits and cannot recover earlier traffic. See the Vercel Web Analytics privacy details. AdSense loading remains disabled.
  • When you search, your search text goes to Folio’s server. The server passes it to the sources you have on to get results. Searches can be saved in your browser; if you sign in and account syncing is available, saved topic and conversation data can also be stored on Folio’s server.
  • The website can request an AI answer for a search. Search text and relevant result information may be sent to a configured AI provider; using the model selector is not an opt-in privacy switch.
  • Source preferences and recent searches can be kept in your browser. Account-based topic history can also sync to our server when you sign in and syncing is enabled.
  • AdSense is currently disabled, so this site does not load its advertising script.

What you type and where it goes

A search sends what you typed (up to 180 characters) to Folio’s server, along with which sources are on and which page of results you want. If a search address includes a place (the “near” part of the address), that place is sent too. The server then asks these services for results:

  • Microsoft Bing: web results, related “Deep dive” searches, and image results when Images is on.
  • Wikipedia (Wikimedia Foundation): articles, the summary card, and coordinates for place names, when Wikipedia is on.
  • Grokipedia (xAI): pages and summaries, when Grokipedia is on.
  • AI model providers: A search may be processed by a configured AI provider to generate an answer or perform a translation. Depending on availability and your model choice, the service can use xAI, OpenAI, Anthropic, or another configured provider or gateway. The provider may receive your question and relevant source titles, excerpts, and URLs. A request may be retried with a different configured provider if the initial attempt fails. Providers process data under their own terms and privacy policies.
  • Datamuse: short definitions for words in your search.
  • Open-Meteo geocoding: place lookups for the location references.

As you type, once there are at least two characters, Folio’s server sends the text so far to Wikipedia and Grokipedia for suggestions. When you open a result preview, the server sends that result’s title and address to Wikipedia or Grokipedia to get a longer extract. Folio’s server makes all of these requests itself. They carry the server’s own identification, not your IP address, cookies, or device details. Each service handles the requests it receives under its own policy. Trending topics come from Google Trends and Grokipedia, and Folio’s server fetches them without sending anything about you.

Your search is also part of the page address (for example /?q=…), so it appears in your browser history and in the address you share if you copy the link. The public search endpoint at /api/search works the same way. The query is in the address, and results come from the same services. The website can request an AI answer for a search. The public search endpoint returns source results and does not generate an AI answer, including when ai=1 is supplied. If the site language is not English, Folio asks an AI provider to translate the query into that language (sent to that language’s Wikipedia) and into English (sent to Grokipedia, and to Bing with the site language set when the query is not in Latin script). Grokipedia titles and snippets, and the text of a preview you open, are also sent to an AI provider to be translated into the site language. The AI answer is written in the site language. Until you pick a language, Folio reads your browser’s preferred languages (the Accept-Language header it sends with every request) to choose one.

Using Zip1 in ChatGPT

When you use the Zip1 plugin in ChatGPT, ChatGPT sends the search query or article URL needed for the selected tool to Zip1. Zip1 sends queries to its public search sources and retrieves requested public pages, then returns results or article extracts to ChatGPT. ChatGPT processes these requests and results under OpenAI’s terms and privacy policy. The plugin tools do not access your private Zip1 topics, saved conversation history, or account information. The search, image, preview, and comparison tools retrieve public sources without calling an AI answer model. When you explicitly request the plugin’s ChatGPT answer tool, Zip1 sends your question, any recent conversation messages supplied with that request, and retrieved source context through our AI Gateway to an OpenAI model. This uses Zip1’s Gateway account; it does not use your personal ChatGPT subscription.

Separately, selecting ChatGPT in Zip1’s model menu sends your question and relevant source context through our AI Gateway to an OpenAI model. That mode may retry with another OpenAI model through the same Gateway. It uses Zip1’s API configuration, rather than your personal ChatGPT login or subscription.

What stays in your browser

Folio uses browser storage for settings and features including:

  • which sources you turned on or off;
  • which AI model you picked, if you picked one;
  • which site language you picked, if you picked one;
  • which speaking voice you picked for that language, if you picked one;
  • recent searches, individually saved searches, and topic-based conversation history;
  • generated-image and other local feature state, where available;

These stay on your device. The site language is also stored in a cookie named folio_lang so pages and searches load in that language. That cookie is sent to Folio’s server. Other saved items can remain local to your browser. If you sign in, account topic history may sync to our server. The sidebar groups searches and follow-up conversations under their topics. Older saved and recent searches are moved into that history on this device; guest topics enter an account only after you confirm an import. Deleting a topic removes it from the active catalog and syncs the change when account saving is available. Local recovery copies can remain. Clearing this site’s browser data removes local copies, not server account records.

On Folio’s server

Following relationships are saved to your signed-in account. You can see who follows you and the members you follow. These lists show discoverable profile details or details already shared through an accepted connection; other profiles appear as private members. Default public profiles are public account links saved as follows on Zip1. You can unfollow them; your choices are stored with your profile. These choices do not change your follows on X or create mutual connections. Following does not grant access to shared images, saved topics, or private conversations. Shared images still require an accepted connection.

When account features are configured, Folio uses a database for sign-in information and saved account topics. Account topics may include searches, answers, and follow-up questions. Guest topic history is normally stored in browser storage. Some source responses may be cached briefly in server memory to reduce repeated requests. We do not claim that search text is absent from all application, hosting, or provider logs.

Folio is hosted on Vercel. Like any web host, Vercel receives each request’s IP address, browser details, time, and the address requested, which can include your search text. Request logs are kept by our hosting provider Vercel according to Vercel’s own retention policy. See the Vercel privacy policy.

What your browser loads from other services

Some parts of a Folio page load straight from other companies’ servers. Those companies see your IP address and browser details when they do:

  • Google Fonts serves Folio’s typefaces on every page.
  • Google’s favicon service serves the small site icons next to results. That request includes the result’s domain name.
  • Images in results come from Bing’s image servers, Wikimedia, Google (pictures on trending topics), and, when you open an image preview, the site that hosts that image.
  • YouTube (youtube-nocookie.com) loads only when you open the preview of a YouTube result.
  • A “Created with Grok” script from grok.com (xAI) loads on each page. It checks with xAI’s app-builder service whether to show a small “Created with Grok · Remix” banner that links to Grok.

Related policies: Google, Microsoft, Wikimedia, xAI, OpenAI, Anthropic.

Ads

AdSense loading is currently disabled across the site. If advertising is enabled in a future content placement, Google and other third-party advertising vendors may use cookies to serve ads based on your previous visits to this site or other websites. Google’s advertising cookies allow it and its partners to show personalized ads. Ad requests may share your IP address, browser details, and page URL with Google. You can manage personalized advertising through Google My Ad Center or opt out of participating third-party vendors through AdChoices. Read more about Google’s advertising practices.

Links you open

Results link to other sites, which have their own privacy practices. The arrow on a result opens the page without passing Folio’s address along. In the iPhone app, outside pages open in Apple’s in-app Safari view.

The iPhone app

The Folio app shows this website, so website account, AI, storage, and advertising practices described above also apply when using the app. The native wrapper may use operating-system features when you explicitly invoke them; consult the device permission prompts for access requests. The Share button hands a link to the iOS share sheet only when you tap it, and you choose where it goes.

What Folio does not do

  • Folio does not sell or rent information about you.
  • Account profiles and user-generated content may be stored when those features are used. Third-party ads and embedded services can have their own tracking practices.
  • Do not submit sensitive personal information in searches or public posts. If you create an account, the registration details you provide are processed for that purpose.

Results come from the open web. Folio does not add its own content filter, so be aware of this if a child is using it.

Your choices

  • Turn Wikipedia, Grokipedia, or Images off so a search skips them.
  • Assume searches entered into the AI search interface may be sent to an AI provider. Disabling individual search sources does not guarantee AI processing is disabled.
  • Delete topics from the history sidebar or your account, or clear this site’s browser data to remove local copies. For account-data requests, contact the address above.
  • Manage personalized ads through Google My Ad Center.
  • Avoid typing personal details into the search box, since searches are sent to the services above.

Changes

If Folio’s handling of data changes, this page and the effective date above will change with it. Questions or requests: hossain6944@gmail.com.

Zip1 Plus is coming soon. Search is free to use today.