Effective date: September 8, 2026

Last updated: October 25, 2026

This Privacy Policy explains how Sideby ("Sideby," "we," "us," or "our") handles information when you use the Sideby mobile app. Sideby is operated by Darío Martínez Bajo, an individual based in Spain. A postal address is available on request. For privacy questions or requests, contact dariomartinezbajo@gmail.com.

Sideby is designed to be local-first. Your record collection, room design, and cover photos are stored on your device and are not uploaded to Sideby servers.

Information we handle

Collection and room data

Sideby stores the following information locally on your device:

Sideby does not provide its own user accounts or cloud synchronization. You may optionally connect a Discogs account, as described below. A name entered during onboarding remains on your device; we do not receive it. We do not collect your email address, contacts, precise location, or a cloud copy of your collection.

Camera and cover photos

If you grant camera permission, Sideby uses the camera to photograph a record cover. The image is processed and stored locally in the app's private storage. Sideby does not upload your camera photos to us, PostHog, RevenueCat, Discogs, or an image-recognition service.

If you choose a cover photo from your photo library, Sideby receives only the photo you select. When you share a picture of your wall, the image is created on your device and leaves it only through the destination you pick in the iOS share sheet; saving it to Photos uses add-only access.

You can deny camera permission, but features that require scanning a cover will not work. Sideby does not record or use audio. The current Android camera configuration may nevertheless cause Android to list microphone permission alongside camera permission.

Analytics and technical data

When Sideby is built with PostHog analytics configured, Sideby uses PostHog to collect a limited set of events about how the app is used, such as whether onboarding was completed, the camera was opened, a photo was captured or retaken, a record was placed, the room was customized, the wall was shared, or a Discogs account was connected and its collection imported.

These events may include limited properties such as the onboarding step, photo attempt number, type of customization, whether a record was the first one added, a broad range for the number of records in the collection or in a Discogs import, the reason a Discogs connection or import failed, and basic app, operating-system, and device information supplied by the analytics software.

Sideby configures PostHog to disable session replay, automatic app-lifecycle events, IP-based geolocation, and remote feature flags. We do not send PostHog your photos, record titles, artists, release identifiers, exact collection size, name, email address, or precise location. PostHog uses an automatically generated identifier to distinguish app installations or devices; Sideby does not connect that identifier to your identity.

Purchases and subscriptions

Sideby uses RevenueCat to manage purchase offerings, subscriptions, lifetime purchases, entitlements, and purchase restoration. RevenueCat receives an automatically generated anonymous customer identifier and information needed to verify and manage your purchase status.

Payments are processed by Apple through the App Store. Sideby and RevenueCat do not receive your full payment-card details from Apple.

Remote cover images

Some record cover images included in the current app are loaded from Discogs' image delivery service. When your device requests one of these images, Discogs or its delivery provider receives the address of the specific cover image requested and may receive information normally sent with an internet request, such as your IP address and basic request or device information. Sideby does not upload your camera photos or send a separate copy of your collection or onboarding name to Discogs.

Record information from Discogs

When you search for a record, Sideby looks it up in the Discogs database through Sideby's catalogue service, and the record details and cover images you see come from Discogs. Wherever Sideby shows those search results or that record, it says "Data provided by Discogs" and links to the matching page on discogs.com.

Connecting your Discogs account

Connecting a Discogs account is optional. You sign in on Discogs' own page, shown in a secure system browser sheet; Sideby never sees your Discogs password. Discogs then issues an access token for Sideby, which is stored in the iOS Keychain on your device and never moves to another device.

To read your collection, the app sends the access token and the address of each Discogs request to Sideby's catalogue service, which signs the request with Sideby's Discogs application key and returns it. The service does not store your token, your Discogs username, or your collection, and it does not log request contents. Your device then downloads your collection directly from Discogs, and the imported records are saved on your device like any other record. Discogs receives your requests under its own privacy policy.

Signing out of Discogs in Sideby removes the access token from your device; records you already imported stay in your collection. You can also revoke Sideby's access from your Discogs account settings.

This application uses Discogs' API but is not affiliated with, sponsored or endorsed by Discogs. 'Discogs' is a trademark of Zink Media, LLC.

How we use information

We use information only to:

We do not sell your personal data. We do not use your information for third-party advertising, cross-app tracking, or profiling for advertising purposes.

Legal bases

Where the General Data Protection Regulation (GDPR) applies, we rely on:

You may withdraw consent through your device settings. You may also object to processing based on legitimate interests by contacting us.

Service providers

We share information only with providers needed to operate Sideby:

These providers process information under their own privacy policies and may process it outside your country.

International transfers

PostHog analytics are sent to its European Union endpoint. RevenueCat, Apple, Discogs, and their providers may process information in the United States or other countries. Where the GDPR requires safeguards for a transfer outside the European Economic Area, we rely on applicable transfer mechanisms, such as adequacy decisions or the European Commission's Standard Contractual Clauses.

Storage and retention

Your collection, room, preferences, onboarding name, and cover photos remain in Sideby's private storage on your device. Sideby's local data is removed when you delete the app, subject to normal device backups and operating-system behavior. A Discogs access token, if you connect an account, is kept in the iOS Keychain until you sign out. Widget images are stored locally in Sideby's shared iOS app-group container so the widget can display them. The operating system may also temporarily retain camera files or cached remote images under its normal storage and cache-management behavior.

PostHog retains limited analytics data, and RevenueCat retains purchase and entitlement records, for as long as reasonably necessary to provide their respective services, meet legal obligations, resolve disputes, and enforce agreements. Apple may retain transaction records under its own legal and accounting obligations. You may contact us to request deletion of data under our control. Some purchase records may need to be retained by Apple, RevenueCat, or us where required by law or necessary to preserve transaction records.

Your choices and rights

You can:

If you are in the EU or EEA, you also have the right to lodge a complaint with your local data-protection authority. In Spain, this is the Agencia Española de Protección de Datos (AEPD) at www.aepd.es.

Because Sideby does not provide its own accounts or cloud synchronization, we generally cannot retrieve or delete local app data on your behalf. That data remains under your control on your device.

Security

Sideby's local data is kept within the app's private storage and iOS app-group storage used by the widget, and a Discogs access token is kept in the iOS Keychain. Connections to Sideby's catalogue service, Discogs, PostHog, RevenueCat, Apple, and remote image services use encrypted HTTPS connections. No method of storage or transmission is completely secure, but we use reasonable technical and organizational measures appropriate to the information we handle.

Children's privacy

Sideby is not directed to children under 14. We do not knowingly collect personal data from children under 14. If you believe a child has provided personal data to Sideby or one of its services, contact us and we will take appropriate steps to delete it.

Changes to this policy

We may update this Privacy Policy when Sideby's features, providers, or legal obligations change. We will publish the updated policy and revise the date at the top. If a change materially affects how we handle personal data, we will provide additional notice where required.

Contact

For questions, concerns, or privacy requests, email dariomartinezbajo@gmail.com.