Nearby Access
← Back to main
Nearby Access for iPhone & Mac

Privacy Policy

Updated November 8, 2026

Applies to Nearby Access on iPhone and Mac, and the iPhone sharing extension accessed using the iOS Share Sheet.

Nearby Access lets you prepare a display of files, photos, videos, links, contact cards, and calendar events for people nearby. It works without an account. This policy explains information stored on your device, information exchanged directly with other nearby devices, and information handled when you contact us or visit this website.

Information stored on your device

Nearby Access stores the items and lists you add, your display name, a local app profile identifier, password-protection settings, blocked profiles, visitor-review preferences, transfer history, and notification settings and history on your device. Where Preview settings is available, the app also stores your automatic-preview preference and when its occasional settings reminder was last shown. On iPhone, the app and its sharing extension use an app group to share relevant local settings, acceptance records, restrictions, and transfer records when sharing using the iOS Share Sheet. Received previews, thumbnails, and files being prepared for export may also be stored temporarily on your device.

Before use, versions with the acceptance screen ask you to confirm that you are 18 or older and agree to the terms. We store your adult declaration, terms version, and acceptance time locally. The main app and its sharing extension reuse the same current confirmation; sharing using the iOS Share Sheet does not require a second confirmation when it is already valid. We do not ask for a birth date, age range, identity document, or selfie. Title filtering stores a local violation count and the time of the last violation, but does not store the rejected title or file contents in that record. Restrictions and the separate voluntary pause are local flags. Acceptance and safety records remain after local library deletion. They are not included in nearby discovery or sent automatically to the developer.

The app has no account service, cloud storage service, developer-operated transfer server, advertising SDK, or analytics SDK. Nearby Access does not upload your library, profile information, relative distance, or transfer history to a developer-operated server and does not track you across other companies' apps or websites. Your device's backup settings may include local app data.

Information exchanged with nearby devices

Nearby discovery and communication use Apple's MultipeerConnectivity framework and encrypted nearby sessions. Your chosen profile name and app profile identifier can be exchanged during discovery, connection setup, access requests, and viewer-presence updates. A private display prevents sharing your display items; it does not hide the profile name you send when you request or view another person's display.

Discovery also communicates availability and the status of sharing using the iOS Share Sheet. The underlying transport's device name can include your device's name and part of its local profile identifier, even if you chose a different name in the app. Discovery information precedes display approval and should not be treated as confidential. Item lists and file metadata are exchanged through a connected, authorized display session, rather than being included in the discovery advertisement.

When you make your display visible, eligible nearby visitors can receive metadata for the items you choose to share, such as item names, types, sizes, list names, and protection status. Thumbnails can arrive separately, and opening or downloading an item transfers its content directly between the devices. When sharing using the iOS Share Sheet, selected items are available while Nearby Access's sharing screen remains open. Recipients may keep, copy, or share content they receive; turning a display off does not recall copies already received.

Review display visitors lets you approve, decline, or block a profile requesting access. In newer versions it is on by default, is enabled once when upgrading to that safeguard, and is restored after local-data deletion; you may change the main-app preference. The sharing extension requires approval for each new visitor connection in versions with that safeguard. Older versions can have different defaults. The displayed name is not a verified identity. Enabling visitor review during an existing viewing session revokes previous item access and requires a new request. Turning your display private or leaving the app suspends display sharing. Approval allows access to available unlocked items without a separate approval for every file. Metadata already seen or copies already received cannot be remotely erased.

Password-protected files require the correct password before their contents are sent. Protected links may show a title and lock status, but their web address is withheld until the password is verified. Protected lists withhold their contents until unlocked. Item names, protected-list names, and lock status are not secret. Passwords entered by recipients are sent to the sender for verification over the encrypted nearby session.

Item passwords control access through Nearby Access; they do not separately encrypt each stored library file. Selected files may retain information already embedded in the original, such as photo location and camera metadata, document authors, contact details, or calendar participants. The app does not automatically remove this information. Review the files you choose to share.

Viewers, distance, and blocking

Display owners can see active viewers by their Nearby Access profile name, and approximate relative distance when supported and available. Nearby Interaction can begin during nearby connection setup before item access is granted. It exchanges ranging information with the nearby device; the app does not request GPS coordinates or geographic location. Device compatibility, permission, and radio conditions affect whether distance is available.

Blocking stores the other profile's identifier on your device and prevents that profile from accessing your display. Names and identifiers are not verified identities. Blocking does not erase copies already received, unpublish content from another display, or guarantee recognition of the same person under a different identifier.

Permissions and other apps

Opening a shared web link sends you to the browser or linked service, which applies its own privacy practices. Files saved or shared through Photos, Files, or another app are handled by that destination and its settings.

Retention, deletion, and your choices

Library items and lists remain until you remove them or delete local app data. Transfer and notification histories keep a limited set of recent records. Unsaved previews are temporary: the preview cache is cleared when the app starts and older previews can be removed sooner to make space. Other temporary export copies are subject to operating-system temporary-storage cleanup.

On iPhone, Profile → Local data → Delete all local data turns your display private, removes the local library and lists, clears blocked profiles and transfer/notification histories, resets preferences, clears items staged for sharing using the iOS Share Sheet, and resets your custom display name to the iPhone's device name. In versions with the newer controls, visitor review and automatic previews reset to on, and the preview-reminder timestamp is removed. The app profile identifier and safety records are retained. Temporary copies may remain until restart or operating-system cleanup. Files already saved to Photos, Files, another app, another person's device, or device backups are not deleted by this action.

On Mac, Settings → Local data provides deletion of the local library, lists, blocks, transfer and notification histories, and preferences. It turns the display private and keeps the local profile identifier and safety records. Copies already exported or retained by another device are not recalled. Temporary files still in use by a sharing service can remain until that service finishes.

Turn your display off to stop sharing, remove individual items from your display, block profiles, or change permissions in your device’s system settings. We do not hold a server-side copy of your app library that we could inspect or delete for you.

Adult declarations, terms records, title-warning counts, local restriction flags, and the app profile identifier remain after library deletion. A restriction stops discovery and sharing, including sharing using the iOS Share Sheet; local library deletion remains available. In versions with separate pause and restriction controls, a voluntary pause can be ended by reviewing and accepting the terms. Confirmed under-18 restrictions and repeated-title restrictions cannot be lifted through that acceptance screen. Older versions may offer different restriction controls; none of these actions verifies age.

Title filtering and reports

Versions with title filtering check titles for a small set of prohibited explicit words. The first two rejected attempts show warnings; a third restricts use on that device. This title check does not inspect file contents and is not a complete content-classification system. Separate preview controls and limited on-device checks are described below.

Help us improve app safety. Tell us which control or screen was involved, what the app did, and what would have helped. For example, tell us if a preview appeared when you expected it to stay hidden. Leave out names, descriptions of the content, and attachments. You can remove names from an in-app draft before sending it. Email app safety feedback.

Where available, Safety & reports and a nearby display's menu can prepare an email to nearbyaccess@gmail.com. The draft can include the displayed profile name, selected category, and text you enter. It does not automatically include profile identifiers, device identifiers, distance, file bytes, images, or passwords. Where available, the optional removal-request category also asks for information identifying where the image appeared, your electronic signature/name, contact email, and a good-faith nonconsent statement. A copy-text option provides an alternative to opening an email app. Drafts are held in memory while the screen is open; copying text places it on the system clipboard. The app does not save a new report history. Older local report records, if present, are cleared by library deletion.

You review and send the message in your email app. Until you choose to send it, Nearby Access has not submitted a report to us. If you send it, your email provider processes the message and we receive your sending address, email header information, and message text. Nearby Access attaches no files. Emails with attachments will not be accepted or opened. You can block a profile separately without sending a report.

Reports help us review safety concerns and product issues. Preparing or sending a report does not automatically erase or unpublish anything from another person's display. The current app has no developer-operated remote restriction or content-removal service. A displayed profile name alone does not reliably identify a person or installation. We cannot recall files already exported to another app or device.

Preview controls and on-device checks

In Profile → Preview settings on iPhone, or Settings → Preview settings on Mac, Show previews is on by default and automatically loads thumbnails on a nearby display after access is granted. Turn it off to stop automatic thumbnails; you can still tap or open an individual item. The preference is saved locally. An occasional in-app reminder points to this setting, with its last-shown time stored on the device rather than sent to the developer.

Where Apple's Sensitive Content Analysis is available and enabled by system policy, supported incoming images and videos are checked on the device for possible nudity. Flagged content remains concealed until you choose to view it. If an attempted check fails, you choose whether to reveal that item. When system policy disables analysis, the app follows your preview preference without treating that as a successful content check. Turning previews on does not dismiss a sensitive-content warning. Your reveal choice is held in memory for that item during the display visit and is cleared when that visit or access ends. A newly detected warning can require a new choice. Opening your own library files is separate from these incoming-preview controls.

This is a limited warning, not a determination of consent, legality, age, copyright, or all harmful content. Analysis can be unavailable, fail, or miss content. No preview image or analysis result is sent to the developer for this check.

If an intimate image was shared without consent

Contact local law enforcement to report suspected illegal sharing, threats, or harassment. If you are in immediate danger, call your local emergency number. If the image also appears on a website or online service, ask that service to take it down. In the U.S., the FTC explains how to request removal and report an online platform.

Send a formal removal request

If you are the person depicted or their authorized representative, you can email a removal request without an account. Include the following information.

Do not send the image, screenshots, or other attachments. You do not need to describe what the image shows.

We can review your request. Files transfer directly between nearby devices, and Nearby Access cannot remotely remove an item from another person’s display or erase copies already received.

Support, website, and Apple services

If you email nearbyaccess@gmail.com, we receive the email address and information you choose to send so we can respond. We use support and report messages to investigate the described concern, respond, and address product issues; they are not used for advertising or marketing. Emails with attachments will not be accepted or opened. Email is not an emergency service. You may ask us to delete correspondence by contacting that address, subject to any necessary legal retention.

This website uses first-party traffic measurement to count page views, approximate daily browser visitors, broad referral sources, and App Store link clicks. It uses a random browser identifier in local storage that resets each day in Los Angeles time, and a same-day referral category in session storage. It does not use advertising cookies or track visitors across other websites. Our analytics database does not store IP addresses, full browser details, complete referrer URLs, or URL query strings. Short-lived day-scoped identifiers and event IDs are deleted after up to three calendar days when new events arrive; daily aggregate totals are retained. Global Privacy Control and Do Not Track signals are respected. Clearing browser storage removes the local identifier. Its hosting provider may process technical request information, including IP address and browser details, to deliver and protect the site. Apple's App Store, TestFlight, device diagnostics, backups, Photos, and Files operate under Apple's policies and the settings you choose. Nearby Access does not include its own remote crash-reporting service.

Age eligibility and known under-18 use

Nearby Access is intended for adults aged 18 and older and is not intended for children or teenagers. The initial confirmation is self-reported and does not verify identity or prevent every misrepresentation.

Where the separate controls are available, Profile → Safety & reports offers Restrict access for under-18 use to record confirmed under-18 use and stop discovery and sharing. Reaccepting terms does not lift that restriction. A separate Pause access action is reversible by reviewing and accepting the terms. Neither action verifies identity or age. The local library can still be deleted while restricted.

If you believe a child is using the app, contact nearbyaccess@gmail.com with a text description. Only include information needed to describe the concern. Emails with attachments will not be accepted or opened. We will assess information actually held by us, minimize further collection, and address deletion requirements where applicable. We have no account system or remote restriction service; a parent or device holder must apply the local restriction on the relevant device.

Policy changes

Changes to this policy will be posted with an updated date. Changes to app data practices will also be reflected in the App Store privacy information when required.

Contact

Nearby Access developer: Jose Quintero
Privacy and support contact: nearbyaccess@gmail.com