Privacy Policy

Last updated: October 28, 2026

1. Who is responsible and what this policy covers

DollHills (also displayed as Doll Hills) is operated by Vakazov Dmitrii, an individual at Conesa 4020, Ciudad de Buenos Aires, Argentina. He is responsible for the personal data described here. Contact: support@dollhills.com.

This policy covers the DollHills mobile applications, the APIs and services that support them, and the related service pages. It explains the information used for accounts, social features, messaging, support and security. Third-party websites and sign-in services also provide their own privacy notices.

2. Information we process

Account and profile information: email address, username, display name, profile photo and bio, optional profile fields, language, time zone and settings. If you use an email/password account, we process your password to authenticate you and store a password hash. We also process session, email-verification, password-reset and two-factor security information where those features are used.

Newer app versions ask you to accept the Terms and Community Guidelines and confirm that you are at least 18. We record the document versions and the time of confirmation with your account. This is a self-declaration; through this step we do not collect your date of birth or identity documents.

If you choose Google or Apple sign-in, we receive an account identifier and the name/email information made available by that provider under your choices, including an Apple relay address where used. We verify sign-in credentials; we do not receive your Google or Apple password.

Content and communications: posts, comments, stories, listings, photos, videos, text and voice messages, replies, mentions, reactions, group memberships, reports, appeals and support correspondence. Content can contain information about you or other people.

Account-linked activity: follows, likes, saved posts and records of posts you explicitly open, together with the identifiers and times needed to provide those features. This is distinct from counting every appearance of a post in the feed.

Technical and security information: IP address, request times and identifiers, relevant app/device and browser information, push-registration tokens, delivery and read status, errors and security/moderation events. Some information is stored locally to keep you signed in, apply settings, cache media and manage voice-message drafts.

Newer app versions include an account-creation integration with Google reCAPTCHA Enterprise (Google Cloud Fraud Defense). The integration is currently disabled. When enabled, the native SDK can process IP addresses, SDK and app/package details, the action being checked, device identifiers and integrity signals, app interactions and information about some installed apps, as described in Google’s platform-specific notices. These SDK data categories are distinct from the verification token and action sent by our backend.

3. Why we use information

We use this information to create and authenticate accounts; provide profiles, feeds, communities, listings and messaging; deliver the content and notifications you request; provide translation when requested; respond to support and privacy requests; and investigate spam, abuse, security incidents and reports.

Saved posts and activity history provide your personal collections and activity views. Feed ordering uses your own posts and accounts you follow before other available posts, in chronological sections. These records are not used for advertising profiling.

We use email addresses for account verification, account recovery, security and service communications. Verification and action limits may be used to protect the service. Moderation can include human review, action logs and reversible hiding of content while a decision is reviewed.

We process the account and communications information necessary to perform our agreement with you and provide the features you request, including proportionate authentication and security measures needed to operate those features. We also process information where required by applicable law. Where processing requires your consent, we ask for it before that processing begins. You can withdraw consent by contacting support@dollhills.com. Device permission does not authorize unrelated uses.

We do not sell personal information or use voice recordings for speech recognition, biometric identification, advertising or model training. Optional profile fields and voice messages are not required to use the core service; missing essential account information can prevent account creation or access to the corresponding feature.

4. Visibility, messaging and voice recordings

Posts and profile content are visible according to the relevant audience and feature. Other users may see your social actions in that feature. Saved-post lists and your opened-post history are intended for your account, not a public activity feed.

Direct and group messages are stored on our server and are not end-to-end encrypted. Access depends on conversation membership, available history and blocking rules. Authorized staff may process the information needed for support, security, handling reports and legal obligations.

Voice messages are optional. Recording starts when you choose it and grant microphone permission. You can listen to or cancel a draft before sending. A recording is limited to five minutes and stops when the app goes into the background. Sending uploads the recording for delivery and storage as part of the conversation.

Voice recordings are stored in non-public Cloudflare R2 storage. Recovery copies of service data are described in sections 6–8. Playback requires a permitted conversation-access check and uses a temporary HTTPS link. Expiry of that link does not delete the stored message. Leaving a chat, blocking access or deleting content cannot recall copies already saved by recipients.

Replies to stories can contain a reference to the story. A preview is shown only while the story remains available to the viewer and has not expired. An older reply may retain its textual context. Story expiry changes availability; it does not by itself establish erasure from storage and backups.

5. Device permissions and choices

Microphone access is used for voice-message recording when you initiate it. You can decline or revoke access in device settings and continue using features that do not need the microphone. We do not record continuously or in the background.

Photo/video selection and camera features use the content you choose to provide. Device permissions or the system media picker control access where applicable. Notifications can be controlled in the app and device settings. Notification previews may be visible on the device lock screen depending on your system settings.

You can update available profile/settings fields, choose whether to send media or voice messages, use content controls where offered, and contact us to exercise rights that are not available as a self-service feature. Removing the app from your device does not itself delete your server account.

If the account-creation reCAPTCHA check is enabled in a compatible app version, a separate notice and Agree/Cancel choice appears before SDK initialization. Declining does not start the SDK. The integration is intended for registration and the creation of a new account through Google or Apple, not ordinary sign-in to an existing account. It is not currently an active protection merely because an app version contains the integration.

6. Recipients and service providers

We disclose content to the people you choose to communicate with and to the audiences of the features you use. We also use providers and authorized technical operators to deliver and protect the service.

Hetzner Online GmbH provides the database, API and media-delivery proxy infrastructure in Nuremberg, Germany. Google provides optional Google sign-in, and Firebase Cloud Messaging supports push delivery. Apple supports Apple sign-in and notification delivery on Apple devices. These services can process installation identifiers, registration tokens, delivery metadata and notification text/previews.

Cloudflare R2 Object Storage stores uploaded photos, videos and voice recordings used by the service, as well as encrypted recovery backups of the database and shared service data. These backups can contain account and authentication records, profiles, content, private-message records, social and moderation data, and stored media. Previously used media storage in Germany is retained as separate recovery copies.

Sentry is used for backend error diagnostics. Diagnostic reports can include exception details, request identifiers, request paths and an account identifier (user ID) in some reports, including registration-email delivery failures. Account and security emails use the service mail infrastructure and recipient mail systems. Support correspondence is received through our support mailbox and may be forwarded by an authorized support contact to the operator for handling. Both handle this correspondence from Argentina. Google provides the Gmail service used for this correspondence. Requested text translation uses self-hosted LibreTranslate.

Providers receive the information needed for their role. Some services also process information under their own notices. We may disclose limited information when legally required or needed to investigate security incidents and protect rights, subject to applicable law.

7. Countries of processing

The application database, API and media-delivery proxy are hosted by Hetzner in Nuremberg, Germany. Active storage for uploaded photos, videos and voice recordings is provided by Cloudflare R2, which also holds encrypted recovery backups. Former media storage is retained in Germany for recovery. R2 uses an Eastern Europe (EEUR) location setting; this does not establish an exact country or a guaranteed European Union jurisdiction restriction. We do not represent all copies as stored only in Germany or only in the European Union. The operator administers the service from Argentina. Support correspondence is handled by the operator and an authorized support contact from Argentina, using Gmail for email delivery and correspondence. The locations of Google’s email processing are separate from those human access locations. Google, Apple and Sentry may process relevant information in countries outside the main hosting location.

Applicable requirements for international processing and transfers depend on the countries and parties involved. Contact support@dollhills.com for information about the arrangements applicable to your data.

8. Retention and account deletion

We retain account information and content to provide your account and the features you request. Saved items and account-linked activity are retained for those features. Deleting or hiding an item in the app, or a story becoming unavailable, does not by itself erase every stored copy.

You can request deletion through the account-deletion option in app settings, at https://dollhills.com/account-deletion/, or by emailing support@dollhills.com with your account email address or username. You do not need to install the app, sign in or create another account to send a request. Requests are handled manually; this website does not perform immediate automatic account erasure. Proportionate ownership verification may be needed.

A deletion request can cover account identifiers and sign-in information, profile and settings, social activity, posts, comments, stories and messages, uploaded photos, videos and voice recordings, and associated derivatives. Completing deletion requires deletion or irreversible anonymization of the in-scope personal information and ending account access and sessions. Suspending, hiding or freezing an account alone is not completed deletion.

Associated records in backups, operational logs, moderation records and service-provider systems also need separate consideration. We do not represent removal from an active account as immediate erasure of every backup or provider-held record. If particular information needs to be retained for a specific lawful reason, you can request an explanation of its categories, reason and retention period or criteria. Copies independently saved by other users are outside our control.

Active media storage, retained former storage and local and offsite recovery backups require separate handling when data is deleted. Routine recovery backups are made weekly, and a previously verified copy is replaced only after a new copy is verified. A failed backup can extend the age of the last good copy. Older release, rollback and other recovery copies may be retained separately from routine backups. Logs are managed using rotation and storage limits. These mechanisms do not establish a single maximum retention period for every copy. There is no single guaranteed erasure period covering every account record and backup.

The manual process does not remove your legal rights or applicable deadlines. For rights governed by Argentine law, the AAIP describes ten calendar days for access and five working days for correction, updating or erasure after receipt of a request, subject to applicable legal conditions. Ownership checks must not create unjustified delay. Contact support@dollhills.com for the actual status of a request, confirmation of its outcome and information about any data that remains.

9. Security and your rights

We use access controls and protected network connections to reduce unauthorized access. Recovery backups are encrypted before upload to cloud storage; authorized operators with the recovery key can decrypt them. Cloudflare also applies provider-managed encryption to R2 storage. These measures are distinct from end-to-end message encryption: messages remain server-stored as described above. Infrastructure and application security depend on ongoing administration; no system can guarantee absolute security.

Depending on the law applicable to you, you may request access, correction, updating, deletion, restriction, objection or a copy/portability of relevant data, and withdraw consent where processing relies on consent. Send requests to support@dollhills.com. We may seek proportionate information to verify ownership; do not send your password or one-time login codes.

You may complain to the competent data-protection authority. In Argentina this is the Agencia de Acceso a la Información Pública (AAIP): https://www.argentina.gob.ar/aaip/datospersonales/derechos. Contacting us does not remove your right to contact an authority.

10. Age and policy updates

DollHills is intended for people aged 18 or older. People under 18 must not create an account or use the service. If you believe an underage person has supplied personal information, contact support@dollhills.com so the operator can investigate and take appropriate action.

We update this notice when relevant features or processing practices change. The published version shows its last-updated date, and material changes are communicated as required by applicable law.