Cutting
Download Features Privacy Terms

Cutting Privacy

Last updated: July 19, 2026

Contents

  • Key privacy facts
  • 1. What Cutting is
  • 2. Information we collect
  • 3. Moments photos
  • 4. What we do not collect
  • 5. How we use information
  • 6. Legal basis
  • 7. Sharing
  • 8. Third parties
  • 9. Data location
  • 10. Local device data
  • 11. Retention
  • 12. Safety and moderation
  • 13. Your choices
  • 14. Security
  • 15. Children
  • 16. Your rights
  • 17. Changes
  • 18. Contact

Key privacy facts

This summary gives a plain-language overview of how Cutting handles information. It is not a substitute for the full notice below.

Anonymous sign-in
Cutting uses Firebase Anonymous Authentication. We do not ask for your email, phone number, or password to use the app. See section 2.
Display name
You choose a display name during onboarding. That name is shown to other members of your private groups when you start or join a break. See section 2.
Cloud storage
Groups, memberships, active breaks, In/Out responses, invite codes, device push tokens, and Moments photo metadata are stored in Google Firebase so the service can work across devices in your group. Moment image files are stored briefly in private Cloudflare R2 object storage. See section 2 and section 3.
Moments photos (optional)
If you choose to share a Moment, the App uses the camera to capture one square photo for that break. Photos are visible only to members of that private group, are short-lived on our servers, and can be reported, removed, recalled, or hidden. Cutting is not a public photo network. See section 3 and section 12.
Push notifications
If you allow notifications on your device, we use Firebase Cloud Messaging to alert you when a break starts, a host is leaving, or a break is cancelled. You can control this through your device settings. See section 5.
No ads or analytics SDKs
The Cutting app does not include Firebase Analytics, Crashlytics, or other third-party advertising or analytics SDKs. See section 8.

1. What Cutting is

Cutting is a mobile productivity / lifestyle app for coordinating immediate, real-world group breaks within small private groups. It is a real-time coordination tool — not a chat app, messaging product, public social network, dating app, or event planner.

Optional Moments let people who joined a break share one ephemeral photo with that same private group. Moments are not a public feed, profile gallery, or messaging feature.

This Privacy Policy describes how Redoxsoft ("we," "us," or "our") handles information when you use the Cutting mobile application and related services (collectively, the "App"). By using the App you also agree to our Terms & Conditions, which include community standards and the Moments moderation workflow.

2. Information we collect

When you use Cutting, we collect and store the following information as needed to operate the App:

Account identifiers

  • A Firebase Authentication user ID (UID) created when you sign in anonymously
  • A display name you provide during onboarding (shown as "Your name" in the app)
  • Profile timestamps (createdAt, updatedAt)

Device and notifications

  • Firebase Cloud Messaging (FCM) device token
  • Device platform (for example, Android or iOS)
  • Optional app version and push preference flags, when available

Groups and membership

  • Group names you create or join
  • Group membership, including your display name within each group
  • Invite codes and invite metadata used to join groups

Breaks ("rituals") and responses

  • Break type, label, and icon
  • Host user ID and host display name
  • Free-text location label you or the host enter (for example, "Usual Place")
  • Your In or Out response to a break
  • Timestamps related to break start, active duration, cooldown, cancel, and expiry

Moments (only if you upload)

  • Photo image file (compressed square WebP) and related metadata — see section 3
  • Report metadata if a participant reports a photo — see section 12

Permissions

  • Camera: requested only when you choose to capture a Moment. We do not access your photo library to create Moments; capture happens in-app.
  • Notifications: requested during onboarding so we can alert you about breaks in your groups.

3. Moments photos

Moments are optional, short-lived photos associated with a specific break in a private group. They exist to help people who are already coordinating a break share a lightweight visual — not to build a social feed.

What is stored

  • Image bytes (640×640 WebP, size-limited) in private Cloudflare R2 storage
  • Metadata in Firestore under the break, including uploader user ID, display name at upload time, status (for example pending, active, recalled, or removed), content type, dimensions, timestamps, and expiry
  • Short-lived signed upload/download URLs minted by our Cloud Function so image buckets are not publicly browsable

Who can see a Moment

  • Members of the same private group for that break
  • Not the public internet, not other groups, and not a searchable gallery

When uploads are allowed

  • Only while the break's short "meeting" window is open (about 30 minutes from break start)
  • Only if you are the host or your response is In
  • One photo per person per break

Local copies

After a successful download, the App may keep a cached copy of a Moment on your device alongside local recent-break history (about 14 days). Leaving a group clears that group's local Moment files on your device.

4. What we do not collect

Cutting does not collect:

  • Email addresses, phone numbers, or passwords for sign-in
  • GPS coordinates or precise device location — the App does not request location permissions; locations are text you type
  • Contacts or address book data
  • Payment or billing information (the App is currently free)
  • A permanent public photo profile, albums, or photo library browsing — Moments are optional, per-break, and ephemeral
  • Chat messages, comments, likes, or reactions (the App has no chat)

5. How we use information

We use the information described above to:

  • Create and maintain your anonymous account
  • Let you create, join, and switch between private groups
  • Start breaks, show who is In or Out, and display break details to group members
  • Deliver Moments photos to eligible group members for a short period
  • Process safety actions such as report, remove, recall, and local hide, and review report metadata when needed
  • Send push and local notifications about breaks in your groups
  • Remember recent location text and break history for faster reuse on your device
  • Operate, secure, and improve the App

6. Legal basis

Where applicable data protection laws require a legal basis, we rely on the performance of our contract with you (providing the App) and our legitimate interest in operating a secure, functional coordination service for private groups — including preventing abuse of Moments. Push notifications and camera access are used only if you grant permission on your device. Uploading a Moment is optional and constitutes your request to process that photo for the purposes described here.

7. Sharing

We do not sell your personal information. Information is shared as follows:

With other group members

Members of a group you belong to can see your display name, your In/Out responses, break details (including location text and host name), and any Moments you upload for breaks in that group (while those Moments remain available).

With service providers

We use Google Firebase (Authentication, Firestore, Cloud Messaging, and Cloud Functions) and Cloudflare R2 (private object storage for Moment images) to host and deliver the App. These providers process data on our behalf as infrastructure providers.

When you report content

If you report a Moment, we store report metadata (reporter ID, reported uploader ID, reason, and related timestamps) so we can review and act. Report records do not store image bytes or public image URLs.

Legal requirements

We may disclose information if required by law, legal process, or to protect the rights, safety, or property of Redoxsoft, our users, or others.

8. Third parties

The App uses the following infrastructure providers:

  • Firebase Authentication (anonymous sign-in)
  • Cloud Firestore (groups, memberships, breaks, responses, Moments metadata, device tokens, report metadata)
  • Firebase Cloud Messaging (push notifications)
  • Firebase Cloud Functions (notification delivery and Moments upload preparation)
  • Cloudflare R2 (private storage for Moment image blobs)

Google's handling of data is described in the Google Privacy Policy. Cloudflare's handling of data is described in the Cloudflare Privacy Policy.

The Cutting app does not integrate Firebase Analytics, Crashlytics, or other third-party advertising or analytics SDKs. We do not share Moments or account data with advertising networks or third-party AI services.

9. Data location

Cutting's Firestore database is hosted in asia-south1 (Mumbai). Firebase Cloud Functions used for notifications and Moments upload preparation run in asia-east2 (Hong Kong). Moment image objects are stored in Cloudflare R2 according to our configured bucket region. Data may be processed in other locations as part of these providers' global infrastructure.

10. Local device data

In addition to cloud storage, the App stores some data locally on your device (SharedPreferences / Hive), including:

  • Your selected group and cached group memberships
  • Recent break history for quick reuse
  • Location text history and place catalog entries
  • Custom break types you define
  • Cached Moment image files and paths for recent breaks
  • Local hide list for members whose Moments you chose to hide on this device
  • Cached user ID and display name for notification actions

Local data remains on your device unless the App syncs related information to our backends as described above, or you clear app data / uninstall.

11. Retention

Breaks and responses

  • Break documents include a ttlAt timestamp (approximately 24 hours from creation). The App's live sync window is shorter (about 2 hours).

Moments

  • Upload / moderation window: about 30 minutes from break start (green indicator in the App)
  • Server retention: Moments metadata and R2 objects are intended to expire about 2 hours after break start (Firestore TTL and R2 lifecycle rules)
  • Local cache: downloaded Moments may remain on your device with recent-break history for about 14 days
  • Report metadata: kept longer than the image (on the order of about 30 days) so we can review safety reports after the photo itself is gone

Groups and profiles

Group, membership, and profile data may persist until removed through in-app actions (for example leaving a group) or a support request.

Important: Automated cleanup depends on configured TTL and object-lifecycle rules. TTL expiry is not a substitute for account deletion. To delete your anonymous account and associated data, use Settings → Profile → Delete account in the app, or follow data deletion. You can also contact us using the details in section 18.

12. Safety and moderation

Because Moments are user-generated photos visible to other members of a private group, we maintain safety controls that help people keep their break groups comfortable and respectful. Cutting remains a private-group coordination app — not a public social network — but photo sharing still needs clear standards, reporting, local blocking, and prompt review practices.

In-app controls

  • Report photo: removes the photo for the group and writes report metadata for our review
  • Remove photo: lets a participant hide another participant's photo for the group without filing a formal report
  • Recall photo: lets the uploader remove their own Moment
  • Hide member (local): hides that member's Moments on your device only

How we handle reports

  • Reported photos are removed from active display promptly via the in-app action
  • We review report metadata and may take further action, including removing content, restricting features, or terminating access, consistent with our Terms
  • We aim to review safety reports within 24 hours of receipt where practicable

Contact for safety concerns

Email info@redoxsoft.com with the subject line "Cutting safety report" and include the group name, approximate time of the break, and any details you can share. Do not email illegal images of minors; contact local authorities for emergencies.

13. Your choices

  • Notifications: You can allow or deny push notifications in your device settings at any time.
  • Camera: You can deny camera permission; Moments upload will be unavailable until you allow it.
  • Display name: You can update your display name during onboarding or in settings on return visits.
  • Leave a group: You can leave a group from Settings when you belong to more than one group. This removes your membership records for that group and clears that group's local recent/Moment cache on your device.
  • Moments: Uploading is optional. You may recall your own photo during the meeting window, and you may report, remove, or locally hide others' photos as described above.
  • Account deletion: Open Settings → Profile → Delete account to permanently delete your anonymous Auth user and associated server data (profile, memberships, Moments, device tokens). If the app is uninstalled, use data deletion (email support@redoxsoft.com with your User ID, last display name, and one group name).

14. Security

We use Firebase security rules, private R2 buckets with short-lived signed URLs, and industry-standard practices to protect data in transit and at rest. No method of transmission or storage is completely secure. You are responsible for keeping your device secure (for example, using a screen lock) and for sharing invite links only with people you trust.

15. Children

Cutting is not directed at children under 13, and we do not knowingly collect personal information from children under 13. You must be at least 13 (or the minimum digital-consent age in your country, if higher) to use the App. If you believe a child has provided information through the App, contact us and we will take reasonable steps to delete it.

Moments must not contain child sexual abuse material or any sexual content involving minors. We will remove such content and cooperate with authorities as required by law.

16. Your rights

Depending on where you live, you may have rights to access, correct, or delete personal information we hold about you, and to withdraw consent where processing is based on consent.

Because Cutting uses anonymous authentication, we may need your Firebase user ID (shown in Settings → Profile) to locate your data. You can delete your account and associated server data directly in the App via Settings → Profile → Delete account. If you cannot open the App, request deletion via data deletion by emailing support@redoxsoft.com with your User ID, last display name, and the name of one group you belonged to so we can verify the request.

For other privacy questions, email info@redoxsoft.com.

17. Changes

We may update this Privacy Policy from time to time. The updated version will be indicated by a revised "Last updated" date at the top of this page. We encourage you to review this notice periodically. Material changes affecting Moments or safety practices will be reflected here.

18. Contact

If you have questions about this Privacy Policy or safety concerns, contact us at:

Privacy / general: info@redoxsoft.com

Account deletion: support@redoxsoft.com (see data deletion; subject: "Cutting Account Deletion Request")

Support / safety: info@redoxsoft.com (subject: "Cutting support" or "Cutting safety report")

info@redoxsoft.com

Copyright © 2026 com.redoxsoft

Privacy Policy Terms & Conditions Data deletion