Privacy policy

1. Information SLOG stores

SLOG stores your stable account ID, screen name, display name, password verifier, sign-in sessions and account status. Passwords are stored as salted password verifiers, rather than readable passwords.

Application records include profile choices, self-declared age band, selected appearance and image references, post text or excerpts, timestamps, file names and types, sizes, fingerprints, storage references, invitations, circle permissions, saved-memory references, replies, messages, Board posts, notifications and activity records. View and source-open counts support the creator dashboard; they are activity counts, not payment records.

Security controls use sign-in attempt records, including hashed account/IP identifiers. Hosting providers also process technical request information such as IP addresses, browser/device headers and request times for hosting, security and troubleshooting. Profile and background images uploaded through SLOG are stored as bounded display copies in SLOG’s hosting storage.

2. Device originals and connected storage

When you choose device storage, full conversation and attachment originals are kept in this browser’s local storage database. Clearing browser data can remove them. A copy on one device or website origin is not automatically available on another.

When you select Google Drive, SLOG uploads that selected original to the connected account and records the reference, file metadata and fingerprint. It does not create a permanent second copy of that Drive original in SLOG’s file storage. File bytes pass through SLOG’s servers during transfer and authorized playback. This is not end-to-end encryption.

External storage links and embedded media remain subject to the storage provider’s permissions and availability. SLOG cannot restore an original that no longer exists at its location.

3. Google Drive data and permissions

SLOG requests the Google Drive drive.file permission: access to specific files created or used with SLOG. It does not request permission to read or manage every file in your Drive.

To identify and reconnect the correct storage account, SLOG reads its Google Drive account identifier and email address. After you approve Google’s consent screen, SLOG receives access and offline refresh tokens. These are encrypted in the server database with an application encryption key held in runtime secret storage. They are not sent to SLOG’s browser interface.

The tokens are used to create originals you select for Drive storage and retrieve registered originals for viewers who pass SLOG’s access checks. Offline access lets an authorized viewer open a connected original while the owner’s phone is offline. SLOG uses this Google data to provide the storage and sharing features you request, not for advertising, sale of data or training generalized AI models.

SLOG’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Human access to Google data is limited to permitted purposes such as support with your consent, security investigations and legal obligations.

4. Sharing and who can access records

Post and original access follows your audience selection, active circle permissions, applicable invitation/history windows, content-rating settings and any explicit sharing references. Only-me content is not made public by connecting Drive. A viewer does not need their own Drive connection to view content shared with them; they need SLOG access to that content.

Private replies and circle chat are limited to their intended participants in the application. Board posts are visible to active SLOG members. Profile display images and direct profile pages follow the applicable account/circle access rules.

The site owner’s Admin can inspect account and registered-original metadata and administer accounts, site settings and sharing operations. Authorized hosting operators may access stored records for support, security and maintenance. Hosting infrastructure processes data on the app’s behalf. Other members receive the content you share with them, not your provider tokens.

Authorized viewers can still capture screens or retain information they have already seen. Watermarks and download controls cannot guarantee that a recipient will not copy content.

5. External services and cookies

Google handles its own sign-in and consent pages. The optional media picker sends your search terms directly to GIPHY for GIFs and stickers and loads popular meme templates from Imgflip. Those services receive search or preview requests, including technical connection information; your private SLOG post text and provider grants are not included in those searches. Linked images, videos, news sites and embeds can contact their providers when displayed or opened. Those providers may receive technical request information and apply their own cookies, sign-in requirements and privacy policies.

SLOG uses secure sign-in and password-unlocked Admin session cookies, short-lived connection-flow cookies, and browser storage for device originals and app preferences. These support the features you use. SLOG does not use Google Drive data for advertising.

6. Your controls, retention and deletion requests

You can change supported profile and sharing settings, stop sharing an original, sign out and export sharing records through SLOG’s controls. Stopping sharing changes SLOG access; it does not delete the original from your device or provider. An export of sharing records does not include every original file or provider token.

To disconnect Drive, unlock Admin and choose Disconnect beside that account. This clears the active stored grant and blocks future SLOG delivery through it, while keeping your Drive files. You can revoke the app’s access independently through your Google Account’s third-party connections settings. Delete provider originals in the storage account if you want to remove those files.

Account and reference records remain while needed to operate SLOG and preserve existing references, security and recovery records. There is currently no automatic account-deletion or fixed backup-expiry schedule. Recovery backups may contain earlier encrypted records; disconnecting clears the live grant, rather than every historical backup. Revoking access at Google stops provider authorization independently of those backups.

Contact the site operator to request access, correction or deletion, or help finding and removing your data. Requests are handled by the operator; some records or copies already held by other recipients may remain. The operator will explain the scope and any retention limits for your request.

7. Contact and policy updates

SLOG is operated by the site owner. For privacy questions, support or a data request, email mccoy228@gmail.com. Send only the information needed to identify your account and request; do not email your password, verification codes or provider tokens.

Changes to these practices will be reflected here with an updated date. If the app proposes a new use of Google data beyond the uses disclosed when you consented, it will seek the required new consent before that use.