Private beta
Privacy notice
Reentry is built around a local-first workspace. This notice explains what stays on your device, what may leave it when you choose an online feature, and how the Reentry website handles beta signups.
Who is responsible
Reentry is operated by Dennis Weishaar. Questions, privacy requests, and complaints can be sent to emaildweishaar@gmail.com.
Information stored on your device
Reentry stores the core workspace locally. This includes canvases, placements, notes, saved items, tags, search indexes, chat history, enrichment jobs, cached media, and generated previews. Authenticated browser sessions and connector cookies are also kept in the app’s local data directory when you choose to sign in to a supported site. You control this data through the app and your operating system.
Information sent to online services
Some features cannot run entirely offline. When you ask Reentry to generate text, create embeddings, transcribe media, enrich a source, search the web, or use an authenticated connector, the information needed for that request may be sent to the provider or website you configured. Depending on the feature, this can include prompts, selected workspace context, source text, transcripts, images, URLs, and ordinary browser requests. Providers may include Anthropic, OpenAI, models accessed through OpenRouter, source websites, and media or transcription services. Their own terms and privacy notices govern their processing.
Reentry does not silently upload the entire local workspace. Online processing is bounded to the feature being used, its selected context, and the provider configuration available to the app.
Website and beta signup information
The beta form sends your email address, whether you asked to hear about founding lifetime access, which signup form you used, and a derived idempotency value used to prevent duplicate submissions. Reentry uses this information to operate the beta, contact you about access and product updates, and—only when requested—share details of a founding offer.
The marketing site currently does not use analytics or advertising cookies. Hosting and delivery providers may still process IP addresses, device information, and standard request or security logs under their own policies. Signup information is forwarded to the configured email or beta-list provider.
Why this information is processed
Reentry processes beta signup information with your consent and to provide the updates you request. Security and basic service logs are processed where necessary to operate and protect the website. App data is processed to provide features you choose to use and, for optional online services, to carry out the request you initiated. You may withdraw consent to beta marketing at any time.
Sharing, sales, and international transfers
Reentry does not sell personal information and does not share it for third-party behavioral advertising. Information is shared only with service providers needed to operate the beta or with online providers and source platforms involved in a feature you use. Those services may process data outside your country or the European Economic Area. The safeguards available depend on the provider and your chosen configuration.
Retention and deletion
Local workspace data remains on your device until you delete it or remove the app data. Beta signup records are kept only while needed for beta access, requested launch communication, security, or legal obligations. External providers retain information according to their own policies. You can unsubscribe through any beta email or request deletion using the contact address above.
Your rights
Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or receive a copy of personal information connected to you. You may also withdraw consent and complain to your local data protection authority. Email Dennis Weishaar at the address above to exercise a right. Reentry may need enough information to verify and complete the request.
Security and changes
Reentry uses a local-first architecture and limits online requests to the services involved, but no storage or transmission method is completely secure. This notice may change as the beta, providers, and distribution model evolve. Material changes will be reflected here with a new update date.
Last updated: July 15, 2026