Privacy is part
of the picture.

About this notice

This notice describes the current Peeplo development preview and the account service and the community and collaboration features being tested for it. Feature availability can differ between development builds and the hosted preview. Peeplo support can be reached at support@youragentmemory.com. This page does not describe AgentMemory’s separate product or database. Peeplo is operated by Dhruv Joshi, based in India, and is intended for people aged 18 and over. Final release disclosures and retention procedures are being completed before public launch.

What Peeplo stores

• Account information: your email, a password hash, username, display name and email-verification state.
• Public profile: your headline, bio, location you choose to provide, interests and optional external avatar URL.
• Account security: session identifiers, device labels, last-use/expiry timestamps, hashed access and refresh credentials, verification/recovery records and policy consent.
• Community information, when enabled: posts, media links, comments, reactions, bookmarks, follows, blocks, muted accounts, polls and reports.
• Work information, when enabled: freelancer profiles, jobs, applications, message requests and messages, team memberships, projects, tasks, milestones, calendar items and versioned agreements and acceptances.
• Connected services, when enabled: provider identity, channel name, provider-reported subscriber count, ownership evidence and encrypted authorization tokens. Optional push delivery uses an encrypted device token and notification preferences.
• Membership and badges: plan and access period, owner-granted or Apple-verified entitlement records when available, optional profile/post links, and recorded Peeplo authenticity review decisions. Premium membership does not verify identity or social-platform ownership.
• Operational information: limited security, rate-limit, error and administration records needed to run and protect the service. Passwords and active session credentials must not be included in production application logs.

Why this information is used

We use this information to create your account, authenticate you, show your profile to other signed-in members, provide member search, deliver account-security emails, enable the community and work features you use, confirm connected creator ownership, deliver notifications you enable, enforce access rules and respond to support requests. Private account information is not offered through the commercial API. Public creator information is shared only after a separate opt-in described below.

What other members can see

Your username, display name and the profile details you choose to provide are visible to other signed-in members. Your email, password hash, account-security credentials and session records are not part of the public profile. Signing up does not confer creator verification. Published posts and jobs are visible to members who have access. Applications, message contents, team work and agreements are restricted to their authorized participants. Authorized moderators can inspect reported content to investigate abuse; messages are not end-to-end encrypted. Reporters’ identities are not shared with the reported member.

Hosting and external providers

The development service uses the existing Hostinger account with Peeplo’s data isolated from AgentMemory. Authorized hosting and email services process information necessary to run the service. External avatars and approved media links load directly from their providers; those providers receive image requests from your device and may apply their own policies. Peeplo accepts managed photos up to 5 MB and short videos up to 50 MB, 180 seconds and 1080p. Image normalization removes original metadata. Technical checks, safety screening where configured and content review precede public availability. Covers follow the same privacy and moderation rules.

Places, camera and nearby privacy

World and community media open after sign-in and email verification. City Stories are optional public city tags and creator-supplied dates, visible worldwide. Captured Here requires a fresh in-app camera session; approximate capture locations are stored on a 1 km grid and nearby viewers use a fresh, session-bound two-minute location unlock. Viewer checks are retained until expired-record cleanup (scheduled every minute); no background tracking is used. Location is device-reported, can be spoofed and is not independent presence or provenance proof. A viewer who sees media can still copy it. Nearby-only media is excluded from commercial data APIs and persistent replay caching. Capture time can be shared by day or minute; choose day for less detail. Private posts are owner-only in this preview; follower approvals are not yet available. Name and avatar remain discoverable. Private accounts may browse other public posts. Switching to private withdraws globe contributions, and returning to public does not restore them. AI-generated demo photos and simulated locations are labelled in local previews and are not real user posts.

Optional city activity API

Commercial city activity counts require both a separate profile consent and per-post City Story consent. No Captured Here content, media URLs, usernames, viewer histories or GPS are returned. New posts wait at least 48 hours, dates end at least two UTC dates ago, groups require five distinct contributors and counts are rounded down to groups of five. These measures reduce disclosure risk but do not guarantee anonymity against all external data. Withdraw consent in Edit profile to stop new responses including your contributions; recipients may retain earlier aggregates. Creator directory access has separate optional consent and may return personal data even when public. API clients must honour withdrawal/deletion requests, avoid sensitive profiling and comply with applicable data protection and intellectual property obligations. Regional availability and legal review are required before launch.

Campaigns, YouTube and optional notifications

Peeplo uses its own reviewed sponsored campaigns, not Google AdMob. Campaign records include advertiser, creative, destination, budget, approvals, estimated qualified impressions, clicks and spend. Signed-in ad events are limited per viewer and day and do not expose viewer identities to advertisers. There is no sensitive audience targeting or third-party advertising SDK. City banners use the city being explored, not viewer GPS. Members may boost their own eligible public original posts through the desktop campaign studio; nearby-only captures and private posts are excluded. Campaigns have clear action buttons, total and optional daily budgets, review, pause/resume and aggregate results. Qualified views are first-party estimates, not independent audits. Live purchases and delivery remain gated. The iOS promotion studio currently supports drafts and campaign management; paid in-app boost purchasing is not yet enabled. External media providers still receive direct device requests. YouTube videos use the official player only after you choose to load it; YouTube may receive network/device information and show its own player advertising. See Google privacy and YouTube terms. Sign-in providers, creator connections, push and campaign delivery stay disabled until configured and validated. Optional announcements and inactivity reminders require separate consent and push permission. An hourly-coarsened last signed-in activity time supports reminders after seven inactive days, no more than once per 30 days, with quiet hours respected. Android delivery is future scope. Public-page analytics remains optional: daily rotating keyed network hashes, allowlisted paths, referring hostnames and device categories, retained up to 90 days. No raw IP, query strings, full referrers or account-page analytics are stored in that table. DNT, GPC and recognized bots are excluded.

Optional public creator directory

The commercial creator API and search-engine-accessible creator pages are optional and off by default. A published, verified creator with fresh independent evidence may explicitly allow username, display name, Peeplo profile URL, verified platform, audience count and check time, plus optional public service pricing. These fields may still identify a person. Private email, credentials, messages, device details and private account records are excluded. Turning a choice off immediately stops new results; external recipients and search engines may retain previously received information. Eligible premium profiles that opt in may appear in labeled premium search placements. The API stores key hashes and usage/cost records, not recipient keys in plaintext or copies of account-wide creator datasets.

Payments and service credits

Desktop purchases use Aurpay when enabled. We store your Peeplo order ID, provider order ID, requested amount/currency/network, verified payment status, access period or service-credit entry. Aurpay processes payment and network information under its own policies. Redirects never establish payment. App Store verification stores transaction identifiers, product and access periods; optional Peeplo-only sales-report rows contain country and currency totals without individual customer identities. Service-credit balances, API charges and reserved/spent campaign budgets are recorded to provide usage accounting. Passwords, merchant keys and provider authorization credentials are excluded from public profiles and exports.

Safety screening, music and stickers

Uploaded media may be checked for prohibited material. Automatic classifier screening is currently not connected; uncertain or unavailable results require staff review. If Google Cloud Vision screening is enabled, image bytes and sampled video frames are sent to that processor for safety classification. Video sampling can miss brief content. No classifier automatically bans accounts, and people may appeal moderation decisions. Peeplo original instrumental loops may accompany posts on Peeplo; commercial recordings require appropriate permission. Sticker points are separate from memberships and service credits, are not a cash balance, and currently have no enabled purchase or withdrawal service. Publishing allowances vary by plan and renew monthly; a limit message explains when publishing can resume.

Retention and deletion

Account information remains while your account is active. You can request an export or permanently delete your account in Settings. Deletion removes active account, profile, consent and session records. Security/audit records may be anonymized where needed. Hosting backups and operational retention require a documented, time-limited policy before public launch; this preview must not be treated as a finalized production retention commitment.

Your choices

You can edit your profile, remove your avatar URL, change interests, revoke sessions, reset or change your password, confirm a new email address, export your information or delete your account. Where enabled, you can disconnect YouTube, disable push, mute or block accounts, remove your posts and manage collaboration invitations. See account deletion for the exact steps. Contact support about access, correction or deletion requests you cannot complete in the app; ownership verification is required.

How information is protected

The hosted API requires HTTPS. Passwords use Argon2id hashing; server access/refresh credentials are stored as hashes. The native app stores session credentials in the iOS Keychain. Private configuration and storage belong outside public web folders. These controls reduce risk but do not establish that the unfinished service is ready for production.

Questions or changes

Email support@youragentmemory.com with “Peeplo privacy” in the subject. Do not send sensitive credentials. This notice will be revised as Peeplo’s features and hosting configuration change. Material changes should be communicated before they take effect.