esharemo logoStart

Data & Trust

Your event archive stays with the host.

A plain-language guide to what esharemo stores, what goes to Google Drive, and what happens when an event changes.

Host reviewing an organized event media archive
The original event files are delivered to the host-connected Drive.

Two places, two purposes.

esharemo keeps the records needed to run the collection. The host's Google Drive holds the original media.

esharemo keeps

The records needed to run the event, connect the host, and keep uploads traceable.

  • Event and guest records

    Event names, dates, access modes, guest records, and invitation details help the host manage who can upload.

  • Upload records

    File names, types, sizes, upload status, failure details, Drive references, and activity records help uploads remain traceable.

  • Connection records

    Host sign-in details and the Google Drive connection state support host access and reconnect flows.

  • Transfer data

    Temporary upload and resumable-session data may be processed while a file is being delivered.

Google Drive holds

The original collection and the folders that make it easier for the host to find later.

  • Original media

    Uploaded photos and videos are delivered to the host's connected Google Drive.

  • Organized folders

    esharemo creates an app folder, event folders, and guest folders to keep the archive readable.

  • Host control

    The Drive account belongs to the host, who controls its sharing, storage, and files.

Google access stays tied to the workflow.

The connection exists to move and organize event media in the Drive account the host chose.

  • The permission

    Hosts connect Google Drive through Google sign-in. esharemo requests the drive.file permission for app-related folder and file operations.

  • The workflow

    That connection lets esharemo create folders, deliver uploads, verify files, and support host review.

  • The connection record

    OAuth credentials are protected in esharemo's stored connection record so the host can continue using the Drive connection.

  • When access changes

    If access expires or is revoked, storage-dependent actions pause until the host reconnects.

  • The boundary

    Google account and Drive data is used for sign-in and event storage, not for advertising or unrelated profiling.

Host reviewing organized media in a Drive folder
esharemo organizes the path. The host keeps the archive.

Privacy works through clear roles.

Everyone involved should know where the media goes and what an event access link means.

Hosts

Tell guests that media goes to the host's Drive, obtain required consent, control invite links or QR access, and manage the archive afterward.

Guests

Use the link or QR path provided for the event and upload only content you have the right and consent to share.

esharemo

esharemo does not provide a public gallery or casually browse user media. Access may be required for support, debugging, security, abuse investigation, or legal compliance.

Retention and deletion have separate boundaries.

Service records and Drive files follow different ownership and deletion paths.

Service records

The records that run the service

Account, event, guest, upload, and activity data may remain while needed for the workspace, upload history, support, security, or legal reasons.

Drive files

The archive the host controls

Original files stay in the host's Drive until the host manages or deletes them. Removing an esharemo record does not automatically erase files already stored there.

Requests

Deletion has more than one layer

Account, event, guest, or media removal requests may need host cooperation. Backup and security-log removal can take longer, and some records may need to remain.

This page is a practical summary. Read the Privacy Policy for the complete details.

Ready to collect

Give guests one clear way to share.

Set up the event, share the path, and keep the media where the host can find it afterward.

Start an event