Privacy Policy

Bereshit is a browser that provides content filtering and protection features.

To evaluate image safety, the app may send the URL of an image detected on a web page to the service’s servers. The app does not directly upload the image file itself; the server retrieves the image from the URL for safety analysis.

Safety-check results may be stored on the server keyed by a content hash of the image and are not linked to a personal user account.

Local browsing history, visited page URLs, search queries, keyword filtering, and domain filtering are handled and stored on the device only and are not sent to Bereshit servers for filtering. Please note that image URLs may be transmitted as part of the safety analysis.

The system may also process operational information required to provide the service, including:

• Job identifiers
• Installation identifiers
• App version
• Model or decision version
• Safety-check results
• Timestamps
• Technical information required for security, abuse prevention and troubleshooting

Client IP addresses may be processed for rate limiting, service security, and abuse prevention.

IP addresses are not maintained as a dedicated user-profile or database field.

Standard request metadata, including IP addresses, may appear in server access logs for operations, security, and troubleshooting purposes.

Bereshit does not collect as part of its normal service operation:

• Your full name
• Home address
• Phone number
• Contacts
• Precise location
• Camera or microphone data
• Card numbers or card security codes. App-store payments are processed by the store; see Accounts for the purchase and subscription information we receive from it.
• Advertising identifiers
• Information for targeted advertising
• Full web-page content
• Website passwords or login credentials
• Cookies or form data for server-side processing

Information is used for:

• Evaluating image safety
• Operating the filtering system
• Returning filtering results to the app
• Protecting the service
• Preventing abuse
• Diagnosing technical issues
• Improving stability and performance
• Handling support and deletion requests
• Complying with legal requirements when applicable

We may use external infrastructure providers, including hosting, server, database, network and GPU-processing providers.

We also use an external monitoring provider (Grafana Cloud) to receive aggregate operational metrics only. That metric stream does not include website URLs, image URLs, or installation identifiers.

These providers process information only as required to provide the technical infrastructure used by Bereshit.

We do not sell personal information and we do not share information with advertisers.

The current production version of the app does not use an advertising SDK, an analytics SDK, or a crash-reporting SDK.

We do not track user activity for targeted advertising and we do not share information with advertising networks.

Information is retained only for as long as reasonably required to operate the service, protect it, maintain system integrity, prevent abuse, investigate technical issues, process support and deletion requests and comply with applicable legal requirements.

An image URL is required only for the time needed to process that image's safety check.

When the check reaches a final state, the raw URL is automatically replaced with a non-retrievable redacted value in the same write that records the result.

Older records created before this mechanism was enabled are covered by the previous retention policy and are automatically deleted or redacted under it within at most 7 days.

Other records may be retained as reasonably required for security, operations, support and legal compliance.

We are working to reduce retention periods and remove raw information when it is no longer required.

The app does not require an account and does not create one automatically. Where accounts are available they are optional; see Accounts.

On first launch, the app automatically creates a random installation identifier. This identifier is not derived from a phone number, device serial number, or permanent hardware identifier.

On first launch, the server issues an access credential to the app. The raw credential value is stored in the app using secure storage, and the server stores only a cryptographic digest for authentication.

The information stored on the server does not enable direct personal identification of the user and is required only to operate the service and authenticate the installation.

The app uses a pseudonymous installation identifier only for service access, installation state, and security. It is not an advertising identifier.

Image URLs sent for checking are not stored together with an installation identifier after processing completes.

Bereshit can be used without an account. Where accounts are available, creating and using an account is optional.

When a user creates an account, we may process:

• Email address and verification status
• A password only to create or check a one-way hash; only the hash is stored
• A Google or Apple account identifier and email address if those sign-in methods are used
• Sign-in sessions as one-way digests linked to the app installation
• Account email and security events and support actions
• If a subscription is purchased through an app store, store-provided purchase and subscription information such as the product, plan, state, dates, free-trial status, recurring price where included, store purchase identifiers (the Google purchase token only as a one-way digest; Apple transaction identifiers as supplied), and a random purchase-binding identifier

The app store processes payment. Bereshit does not receive a card number or card security code.

Account information is used for sign-in, syncing a plan across devices, store verification, fraud and abuse prevention, and legal and accounting obligations. It is not used for advertising and we do not sell it.

Once account email features are available, account emails will be transactional only, such as verification, password reset, and account deletion, and will be sent through Postmark, the transactional email provider acting on our behalf.

Sign-in sessions and single-use email links are retained for 90 days after they end. Account email and security event records are retained for 90 days. App-store notification records are retained for 180 days. Web access logs are retained for 14 days. Application logs roll over at a fixed size. Other account data is retained while the account exists, subject to the deletion rules below.

Where accounts are available, an account can be deleted in the app through Settings → Account and plan → Delete account. The page at https://account.bereshitbrowser.cloud/delete explains how to delete an account. A user may also write to support@bereshitbrowser.com from the account email address; support acts only after confirming through that same address that the request is from the user.

When an account is deleted, the email address, password hash, sign-in provider link, sessions, device links, and account email and security event records are deleted immediately. Devices keep working without an account. Deleting the account does not cancel an app-store subscription.

After deletion, the random account identifier is retained with its creation and deletion times. If no retained record refers to it, it is deleted 30 days after account deletion.

If purchase, subscription, or support-action records exist, a minimal pseudonymous billing and audit record is retained without an email address, name, password, sign-in link, or device link. That record is retained until at least 7 years after account deletion and 7 years of inactivity across all related billing, subscription, and support records. We then retain only a one-way fingerprint of each store purchase identifier together with the purchase date for 3 additional years; after that period, those records are also deleted.

Operational logs do not contain full image URLs and do not contain access keys.

Aggregate operational metrics may be processed by infrastructure providers.

Certain information is stored locally on the device, including app settings, local browsing history, tabs, bookmarks, filtering preferences and operational data.

This local information is not automatically sent to Bereshit servers unless it is specifically required to provide a feature.

Android cloud backup is disabled in the current app version being prepared for distribution, reducing the automatic backup of local browser data to cloud backup services.

We use reasonable technical and organizational measures to protect information, including:

• Encrypted communication
• Access authentication
• Environment separation
• Permission restrictions
• Keeping secrets outside source code
• Security testing
• Minimizing sensitive information in logs
• Protections against unsafe URLs and abuse

No system can be completely secure, and we cannot guarantee absolute protection in every situation.

You may request deletion of information associated with an installation of the Bereshit app.

Requests are reviewed and processed manually.

Opening the request page or sending an email does not immediately delete information.

When an installation can be reasonably identified, we may revoke its associated access and delete or anonymize information that can be linked to it.

Limited non-identifying, aggregated or security-related records may be retained when required for security, abuse prevention or legal compliance.

We aim to respond to and process requests within 30 days.

The service is intended for users aged 13 and over.

We do not knowingly request personal information from children under 13.

If we become aware that personal information was collected from a child under 13 without appropriate authorization, we will take reasonable steps to delete it.

Depending on the applicable law, you may have rights concerning your information, including rights to request access, correction, deletion, restriction or objection.

Requests may be sent to:

support@bereshitbrowser.com

We may update this policy when the service, infrastructure, legal requirements or information-handling practices change.

The latest update date will appear at the top of this page.

Material changes may also be displayed on the website or in the app.

For questions about this Privacy Policy or how information is handled, contact:

• Oshri Ben Yizhak
• Jerusalem, Israel

support@bereshitbrowser.com