CityCrush Privacy Policy

Last updated: September 16, 2026

This policy takes its starting point from the opposite end of the usual one. Instead of opening with what we do, it opens with the decisions that sit in your hands. The whole document runs in a you-then-us order, and each of its nine sections is headed by the same phrase — you are entitled to know. You are entitled to know what is gathered, where it goes, whether it ever leaves this door, whether you can pull it back, and who answers if something goes wrong. Our part is to fill in, beneath each heading, whatever has to be filled in. CityCrush is published by Cryze love, with FSHN FWRD LLC acting as the legal entity. The arrangement below takes effect the moment CityCrush lands on your phone.

§1 — Before anything else, a word about age

One matter belongs at the very front rather than in a footnote: CityCrush serves adults only. This app is not intended for minors, and visitors, registrants and users under the age of 18 all fall outside its scope. The line admits no exception and does not bend to whatever an account happens to declare — date of birth is a required field at registration, and an application below the age of 18 fails validation.

That provision sits first because it settles almost everything that follows. With minors outside the population we serve, the situation of "providing a social service to children" cannot arise, and we do not knowingly collect children's personal information. If you intend to read only one section, let it be this one.

§2 — You are entitled to know which four categories we gather

Collection follows a single measure: enough, and no more. There are four categories, each with its own source and its own purpose, taken one at a time below.

Category one — account information, placed in our hands by you

While you register, sign in and complete your profile, the following is recorded:

• Your email address, which serves as the account's sole sign-in credential;
• Nickname and avatar;
• Gender and date of birth, the latter used to verify that you are an adult;
• Your home city, used for same-city matching and distance estimation;
• Your self-description, interest tags, and anything further you choose to add or edit later.

Lose any one of these and an account may still come into being, but same-city recommendations and profile display will plainly miss the mark, and other members will struggle to recognise you.

Category two — device information, reported automatically by the system

So that the app holds up across chipsets and memory sizes, and so that a crash can be traced to its cause without delay, the following is reported automatically:

• CPU architecture and core count;
• Total device memory and currently available storage;
• The inventory of sensors — accelerometer, gyroscope, ambient light and the like — together with their availability;
• IP address and network type (Wi-Fi or cellular);
• Mobile carrier name and the country code of the SIM card;
• System time zone and language settings;
• The channel-package identifier corresponding to the app's install source.

Category three — usage behaviour, the trail your actions leave

Every swipe across a city card may leave a record behind. Those records are used both to reconstruct what went wrong and to decide where the next release should spend its effort:

• Which way a card was swiped (left, right, or timed out and skipped), and how many seconds each card was held;
• How often voice speed-dating was started, its connection rate, and the average length of a single call;
• The path nodes actually passed between registration and a completed profile;
• Notification click-through and the deep-link source a session arrived from;
• The type distribution of report tickets and how each was finally resolved;
• The city-level location recorded at sign-in.

Category four — payment information, of which only a receipt comes back

When membership benefits or virtual gifts are bought, charging, settlement and reconciliation are carried out independently through the official Google Play Billing channel. What reaches our systems is confined to the essential receipt — order number, transaction status, item purchased and amount. Card numbers, payment passwords and payment verification codes neither pass through our servers nor could be stored there.

§3 — You are entitled to know what each item is used for

Information is not tipped into a pool from which anyone may draw at will. Five purposes stand in one-to-one correspondence with the four categories above:

1. Running the features — registration and sign-in, profile display, same-city matching, city-card delivery and voice speed-dating depend on this one entirely;
2. Improving the service — where users drop off and which build stutters can be seen only through behavioural records and fault logs, and release planning is set on what they show;
3. Guarding security — bulk device registration, automated inflation, account theft and fraud are detected and blocked here, which is how community order is held;
4. Carrying customer support — the enquiries, appeals and reports you send are borne by this heading, with ticket routing and outcome feedback travelling the same line;
5. Meeting legal duties — obligations set by applicable law and by regulators are discharged under this head, and lawful investigations are assisted on the same footing.

Should information ever be wanted for a purpose beyond those five, consent will be sought from you separately beforehand — not announced afterwards as an afterthought.

§4 — You are entitled to know whether information leaves this door

Selling, renting out or otherwise trading your personal information is not our practice — it has not been, and it will not be added to the list of options.

To keep its features operational, CityCrush integrates third-party SDKs / services, among them Adjust (install attribution and campaign performance analysis), Mixpanel (user behaviour analytics), OneSignal (push messaging delivery), AppLovin (advertising delivery and monetisation) and Sentry (crash and exception monitoring). Advertising, analytics and push messaging — all three of these processing categories — are carried out through those third-party SDKs / services. Each provider processes data only within the limits its own function requires, and is bound by its own privacy policy.

Outside the situations listed below, your information will not be handed to any party by us:

1. You have given separate consent, or explicit authorisation, for that particular sharing;
2. Where necessary functions such as payment, push messaging and analytics have to be delivered, information within the minimum necessary scope is passed to an entrusted partner, which must accept confidentiality duties of equal weight;
3. A judicial body, a regulator or applicable law imposes a mandatory disclosure requirement;
4. Sharing is genuinely required to protect members' physical safety, platform security or a substantial public interest;
5. In a merger, acquisition, reorganisation or transfer of assets, information moves with the business concerned, and the recipient must keep applying standards of protection no lower than those set out here.

§5 — You are entitled to access, correction, erasure, withdrawal and a copy

Control over your information stays with you throughout. Five rights may be exercised at any time, through the in-app settings entry or the support mailbox:

1. Access — your account profile and the processing records connected to it can be called up and checked whenever you wish;
2. Correction — where a record is wrong or incomplete, you may require us to correct, supplement or update it;
3. Erasure — you may require your personal information to be wiped; to leave altogether, start from the in-app deletion entry, or submit a request on the CityCrush Account Deletion page;
4. Withdrawal of consent — consent given for a specific processing activity may be pulled back at any time, and pulling it back does not reach into processing already completed;
5. Obtaining a copy — a copy of your personal information will be issued in a structured format at your request.

Beyond those five, questions, objections and complaints about how personal information is handled are equally welcome. Once identity verification is done, a reply will follow within a reasonable period.

§6 — You are entitled to hold us answerable for security and retention

Security is divided into four interlocking checkpoints, so that no single one is left carrying the whole burden:

• In transit — TLS/SSL encryption is applied end to end, leaving little room for information to be intercepted en route or quietly rewritten;
• At rest — sensitive fields are held under AES-256 encryption, with keys kept in separate custody rather than stored alongside the business data;
• When read — permissions are split by role (RBAC), and the data any staff member can reach is compressed to the minimum set their own work demands;
• On audit — every read produces a log entry, logs are sampled on a periodic schedule, and anomalous access raises an alert at once.

Three further arrangements sit behind those four checkpoints: security assessments and penetration tests are conducted at least once each per year; personal information protection training is delivered to all staff on a recurring basis; and a dedicated contingency plan is held for data security incidents, so that when one is triggered, containment, damage control and reporting can be completed within a short span.

Retention obeys one rule only: no longer than the period necessary to achieve the service purpose. Once that period runs out, or once continued retention is no longer required by law, the data concerned is deleted, anonymised or de-identified. Where the law prescribes a longer term for a particular category, that category is held for the statutory period and is likewise purged or anonymised when it ends.

§7 — You are entitled to be told plainly: this app is not for minors

Saying it a second time is no indulgence: this app is not intended for minors, 18 is the only door in, and we do not knowingly collect children's personal information. In the event that a minor's personal information does reach our systems anyway — through an age entered in error, a registration obtained by deception, or something we did not foresee — the information is deleted once the position is confirmed, and the account in question is barred from any further use of the app.

The complete arrangements for protecting minors appear in the CityCrush Child Safety Standards, open to members, parents, guardians and regulators alike.

§8 — You are entitled to know when this policy is revised

When product features are adjusted, when the service model shifts, or when laws, regulations and regulatory expectations take a new turn, this policy is revised accordingly. The new version is published in the in-app notice area and on the official website, and the date at the top is refreshed at the same time.

Where a revision touches rights that matter to you, we will say so before it takes effect — through a pop-up, an in-app notification or another means prominent enough to be noticed; where genuinely necessary, your consent will be sought once more.

§9 — How to reach us

Questions, comments or complaints concerning this policy, the way personal information is processed, or the exercise of your rights may be raised through the channels below: