arh7
↖ ARH7 home

ARH7 · ASK / ROOM / HEART

Privacy Policy

What happens to your information when you explore ARH7 or use its three AI services, from collection to deletion.

Effective 2026.11.03

PrivacyTermsSupportDelete account & data

ARH7 connects Ask7, Room7 and Heart7. Check each store for app availability and supported features, or use the web services below.

What this policy covers

SLOX operates ARH7. arh7.kr provides service information and linked public results without storing a separate copy. This introduction site does not send questions to AI or create accounts. It remembers language in browser storage (arh7-language). This introduction site (arh7.kr) has no advertising SDK. Optional website statistics, cookies and storage are described separately below. Hosting may temporarily process access and error logs. The “Today’s best comments” strip on the home page loads and shows the list Ask7 has approved for publication; this site does not store it separately. Reports sent from the strip go directly from your browser to Ask7 (ask7.kr).

The integrated ARH7 app has no in-app purchases. Versions before 1.3.0(8) have no advertising SDK; from the forthcoming 1.3.0(8), some result screens may show Google AdMob ads, described in “Advertising (Google AdMob)” below. Standalone Ask7 and Room7 advertising notices are separate. Linked service policies provide further details.

Ask7 Privacy Policy ↗Room7 Privacy Policy ↗Heart7 Privacy Policy ↗

Information used by each service

  • Ask7: questions, AI results, summaries of previous questions for follow-ups, question language, device locale and real-user votes. An optional anonymous profile (gender, age group, occupation and broad area type) is stored on your device and sent with questions and votes. You can leave it blank; the teen age group also enables stricter safety checks. It also processes likes on each answer (result ID, answer ID, time and IP hash) and, if the asker agrees, “Today’s best” submissions and reports.
  • Room7: questions, audience comments, debate rounds and results, safety checks and reports. Ranked play uses your SLOX member ID and nickname, three submitted lines, processing results, progress, timing and scores. Email verifies login; signup details go to SLOX authentication, and the Room7 server never receives or stores passwords. A relationship-game role describes that game, not your gender. From ARH7 app 1.3.0(8), using “Watch an ad for one more round” also processes a ticket, date, IP hash, ad unit, transaction number, status and times to verify the reward (see “Advertising (Google AdMob)” below).
  • Heart7: nicknames, relationship, seven selected answers, AI results, creation time and hashes of random participation keys. It does not collect an account, real name, phone number, email, photo or location. Do not use contact details or real names as nicknames.
  • We use this information to provide results, sharing, anonymous statistics, error checks and abuse prevention. Service databases store irreversible salted IP hashes rather than original IP addresses; Ask7 may also process approximate country/region and Room7 a country code. Heart7 does not store original participation keys on its server.

AI processing and service providers

OpenAI (United States) handles AI generation and safety checks. Ask7 sends questions and context; Room7 sends questions, comments, previous rounds and generational consensus; Heart7 sends nicknames, relationship, selected answers and assessment text. Room7 and Heart7 may send an IP hash as a safety identifier, never the original IP address.

Supabase provides databases and Vercel provides web and API hosting. Necessary information is transmitted over the network when you use AI features. Where consent is requested, you can accept or cancel after reading the disclosure; declining prevents that AI feature from running. Reading this policy is not itself consent to a transfer.

OpenAI API training is off by default; abuse logs are generally kept up to 30 days, with exceptions.

OpenAI API data controls ↗

Connected questions and local storage

Up to 60 completed ordinary Ask7 questions, context, languages and result identifiers are saved on this device. Safety-restricted and sensitive results are excluded. Clear the question list or app/browser data to remove local history; this does not delete original server results.

Continuing in Room7 passes the selected question, context and reference Ask7 result; their AI calculations are separate. Choosing seven questions for Heart7 saves a question-and-choice snapshot with the answers on its server and sends it to OpenAI for safety checks and AI analysis. AI answers from Ask7 never become your own answers automatically. Heart7 questions, answers and results become eligible for deletion after 90 days. Link holders can see questions, and can see answers and results after both people answer.

My situation (optional)

Optional “My situation” (up to 240 UTF-16 characters) gives the AI background about the asker for responses and safety checks. It is sent with questions, follow-ups or debate lines to OpenAI and processed by the Vercel server. The app/browser keeps this input only in current session memory, not in URLs or persistent device storage. Questions and generated results using it are excluded from the service’s public result storage, question/safety-event log tables and shared-response cache; sharing, voting and question-list saving are disabled. Content-free usage-limit and abuse-prevention records may remain. Responses may mention the situation: do not enter names, contact details or sensitive information. OpenAI processing/retention and hosting access records remain subject to the providers’ policies and processor disclosures below; this does not mean providers process no personal data. Screenshots, copied text and voluntary report emails or other copies made outside the app are not deleted by this feature. Existing rules still apply to ordinary questions, sharing, profiles and advertising without this feature.

In the ARH7 app, explicitly choosing to continue a personalized question in Room7 passes the current question and situation in memory. It does not start a debate automatically or pass a personalized result reference link. The situation and personalized questions are excluded from Heart7 question collection and the on-device question list. Each generation character keeps its own identity; the situation does not turn AI responses into real people’s opinions or professional advice.

Optional app usage statistics — forthcoming iOS 1.2.1(7)

This section describes optional Google Firebase Analytics planned for ARH7 iOS 1.2.1(7). This update has not been released. It will be offered only in the new version after its public notice and store disclosures are reviewed, and will be off by default. This new SDK collection does not apply to iOS 1.2.0(6) or earlier apps. Android analytics requires a separate update and is not activated by this iOS notice. Optional website statistics on arh7.kr are separate. Refusing does not limit basic features.

After separate consent, the app sends launches, predefined screen IDs and feature-button activity. From ARH7 1.3.0(8), while ad placements are switched on, the Google SDK may also record automatic ad events such as ad impressions in these statistics (see “Advertising (Google AdMob)” below). Google’s SDK may process an app-instance identifier, device/OS/app version/language, usage times, sessions and duration, and approximate country/region/city inferred from IP. It does not request GPS or precise-location permission. These are pseudonymous installation-level statistics, not the complete audience or deduplicated people across platforms.

Analytics events exclude questions, conversations, advice, optional personal context, answers, audio, receipt/vehicle/place content, names, email addresses, account IDs and shared-result identifiers. Events the app sends use only fixed product and feature codes; no Analytics User-ID is set. Ad requests also exclude this content, so automatic ad events do not contain it. iOS 1.2.1(7) has no advertising SDK. Ads planned from 1.3.0(8) are described separately in “Advertising (Google AdMob)” below; even then, Android advertising ID, iOS IDFA/IDFV, advertising storage/user-data and ad personalization stay disabled for this measurement.

SLOX is the operator and Google LLC (United States) receives data for usage analytics, reports and service support. After consent, eligible app use transmits over encrypted connections. Google may process data in the US and countries where Google or its subprocessors maintain facilities; storage is not limited to the US or Korea. See the linked processing terms, subprocessors and privacy information.

Property settings verified on 22 October 2026 specify 2 months for event-level data and 14 months for user-level data, with user retention reset on new activity. Google applies monthly deletion. Standard aggregate reports do not have the same retention limit, so all data does not disappear after 2 months. The app remembers consent on the device until changed or app data is removed; website cookie retention is separate.

Google Signals and user-provided data collection are off, with no Google Ads link, and AdMob is not linked to Firebase or Google Analytics. Google products/services sharing is off, while account settings allow anonymized aggregate modeling/benchmarking, technical support and business recommendations. Existing AI transmission, accounts, sharing, server storage and deletion in Ask7, Room7 and Heart7 follow their own notices and are not authorized by analytics consent.

Turn this off at any time through “Share usage statistics (optional)” in settings. This stops future event collection and resets local analytics data and the analytics app-instance ID. If saving OFF fails, the app attempts to remove the previous grant. If both saving and removal fail, current collection stays off, an error is shown, and a retry is needed to preserve the choice on the next launch. This does not instantly delete previously sent server data, aggregates or other service records. For questions or rights requests, contact namurobori@gmail.com. Start with only the minimum app version and usage time needed; do not send full conversations or new sensitive information.

Google data processing terms ↗Google subprocessors ↗Firebase privacy and security ↗Google Analytics retention ↗

Optional website statistics and international processing

Only after separate consent in “Statistics settings” below the page, Google Analytics measures predefined localized entry-page visits. It is off by default; the Google tag is not loaded before consent. Questions, conversations, personal context, answers, accounts, shared links and result identifiers are excluded. URLs use only fixed public paths, without queries or fragments; referrers keep only a host. Detected in-app webviews are excluded, and app/web statistics remain separate.

Google may process a statistics cookie identifier, device/browser/OS/language information, entry views, sessions, usage times and duration, and approximate country/region/city inferred from IP. Google processes IP for connectivity and regional estimation. This measurement does not request GPS or precise-location permission. Names, email addresses and account IDs are excluded from events. These are pseudonymous browser statistics, not a deduplicated person count or the complete audience.

The recipient is Google LLC (United States), for visit analytics, reports and service support. After consent, data is sent over encrypted connections when eligible pages are used. Google may process it in the United States and any country where Google or its subprocessors maintain facilities. The official Analytics support-subprocessor list includes corporate locations in the US, Japan, Taiwan, Philippines, India and Ireland, among others. Storage is not restricted to the US or Korea. See Google’s processing terms and subprocessor list below.

Account settings verified on 22 October 2026 specify 2 months for event-level data and 14 months for user-level data, with reset on new activity enabled for user retention. Google applies monthly deletion. The same limit does not apply to standard aggregate reports, so all data does not disappear after 2 months. These measurement cookies last at most 90 days without activity-based renewal; this browser remembers the consent choice for at most 180 days.

Advertising storage, advertising user-data and ad-personalization consent remain denied for this measurement. Google Signals and user-provided data collection are off, with no Google Ads or AdMob links. Google products/services sharing is off, while account settings allow anonymized aggregate modeling/benchmarking, technical support and business recommendations. Existing AI, server and advertising operations in connected products are separate from this consent.

Refusing does not limit site use. Turn statistics off in settings below at any time to stop future collection and clear this measurement’s cookies. This does not instantly delete previously sent data or other services’ records. For access/deletion questions use namurobori@gmail.com below, with minimal timing/site details to identify a record. Do not send full questions, conversations or additional sensitive information.

Google data processing terms ↗Google subprocessors ↗Google Analytics retention ↗

Advertising (Google AdMob)

This section describes Google AdMob ads planned for the ARH7 app on iOS and Android from version 1.3.0(8). This update has not been released. ARH7 apps before 1.3.0(8) contain no advertising SDK, and this section does not apply to them. The only placements are one banner at the bottom of the Ask7, Room7 and Heart7 result screens, and the optional rewarded ad “Watch an ad for one more round” in Room7 after the daily free debates are used up. Each placement can be switched on or off remotely, so ads do not always appear.

There are no banner ads while a question or follow-up is being typed (keyboard open), while answering Heart7 questions, during debates in progress or on waiting screens, and there are no interstitial or app-open ads. The Ask7 result screen may show voting and a follow-up question field alongside the banner, and the Room7 question screen may show the “Watch an ad for one more round” offer, which you choose yourself, after the daily free debates are used up. Ask7 shows no ads on results with self-harm or violence support guidance, safety-flagged results such as drunk driving or drugs, sensitive-topic results, or results that used “My situation”. Room7 shows none on debates that used “My situation” or on ranked results, and Heart7 shows none while waiting for the other answer or preparing the result.

While any ad placement is switched on, the Google Mobile Ads SDK may process the IP address and approximate location inferred from it, the Android advertising ID and app set ID, identifiers related to accounts signed in on the Android device where applicable, the iOS identifier for vendor (IDFV), device/OS/app version/language, app-use records such as app launches, taps and video views, ad requests, impressions and clicks, performance information such as app launch time, hangs and energy use, and crash diagnostics. The IDFV has the same value in all apps from the same developer on a device, so it may match the value in other apps published by SLOX. ARH7 does not request App Tracking Transparency (ATT) permission, so the iOS advertising identifier (IDFA) is not used for ads. GPS or precise-location permission is not requested.

Ad requests never include questions, follow-ups, “My situation”, debate lines, AI answers, Heart7 questions, answers or results, nicknames, email addresses, account IDs, shared links or result identifiers. No ad keywords or screen URLs are sent, so question content is not used to choose ads. Ad content is limited to the Teen (T) rating or below. Ads are separate from optional usage statistics, and AdMob is not linked to Firebase or Google Analytics. If you have agreed to usage statistics, however, the Google SDK may record automatic events such as ad impressions in those statistics.

SLOX is the operator and Google LLC (United States) receives data to show ads, measure ad performance, prevent invalid clicks and abuse, and manage ad quality. Data is sent over encrypted connections at these times: when the app starts, for the ad consent check and SDK start, while any ad placement is switched on; when an ad loads, including the rewarded ad that Room7 preloads as soon as the “Watch an ad for one more round” offer appears, before you tap it; and when an ad is shown or tapped. Google may process it in the United States and other countries where Google operates facilities; storage is not limited to the US or Korea. Google processes and retains this data under its own policies, so see the Google information below for periods and methods. Apart from the rewarded-ad verification record described below, SLOX sees only aggregate AdMob reports and does not receive or store per-user ad records.

In the European Economic Area, the UK and Switzerland, a Google consent form appears before ads are requested, with a “Do not consent” option, and you can change the choice at any time under “Ad privacy settings” in the “Ads” part of app settings. The form is not shown in other regions. On Android you can reset or delete the advertising ID in the Google ads menu of device settings; deleting it limits personalized ads based on that ID, but the app set ID and the other data above may still be processed. iOS has no device setting that changes ad processing in this app (ATT is not requested, so the IDFA is never used). My Ad Center settings apply only to ad personalization linked to that Google account. These methods mainly limit personalized ads. Refusing may lead to non-personalized ads or no ads, and questions, debates and compatibility features keep working. The app has no setting that turns off ad requests or this data transfer on its own; while a placement is switched on, data is sent at the times described in the paragraph above. Report inappropriate ads through “Ads” in app settings or namurobori@gmail.com.

“Watch an ad for one more round” is optional. Room7 plays the ad only after the daily free debates are used up and you tap the button yourself. Watching to the end opens one more ordinary Room7 debate that day (once a day, not ranked play). Closing early gives no reward. The reward cannot be exchanged for cash, points or gift cards or passed to anyone else, and can be used only on the day it is earned (Korean time). Without it, free debates open again the next day and every other feature stays available.

To confirm the reward, Google notifies the Room7 server directly that the ad was completed. The notice carries only a random ticket issued by the Room7 server and the ad unit and transaction number, with no account or device identifier. For the daily limit and abuse prevention, the Room7 server stores the ticket, date, IP hash, ad unit and transaction number, status and times, and deletes them after 30 days.

The app decides which placements are on by downloading a settings file from arh7.kr (/config/arh7-ads.json). The request carries no questions or identifiers; the hosting provider (Vercel) may temporarily process ordinary access logs. If the file has never been received or is out of date, no ads are shown.

Behavioral information (Korean law): while ad placements are switched on, the Google Mobile Ads SDK in the app automatically collects behavioral information: app-use records such as app launches, taps and video views, ad request, impression and click records, the Android advertising ID and app set ID (including identifiers related to accounts signed in on the device where applicable) and the iOS IDFV. SLOX allows Google LLC, a third party, to collect and process it directly in the app to show ads, measure performance and prevent fraud; retention follows Google’s policies. The app has no setting to refuse this collection. The consent form above (shown only in the EEA, the UK and Switzerland), deleting the Android advertising ID and My Ad Center mainly limit personalized ads and do not stop all collection while placements are on, and iOS has no equivalent device setting. To avoid ad SDK collection entirely, do not use ARH7 app 1.3.0(8) or later. Send questions or complaints to namurobori@gmail.com.

Google advertising technologies ↗How Google uses data from partner apps ↗Google My Ad Center ↗

Microphone and device storage

Voice input is optional. When you tap the microphone, your operating system or browser asks for permission. Apple, Google, Microsoft or your device’s default speech service converts speech to text, on the device or its servers. Our service servers do not record, store or receive audio files; they process only converted text as questions or comments. You can always type without microphone permission.

Depending on the feature, your device stores language and optional profile settings, Room7 login sessions, transfer-consent choices and hidden nicknames, or Heart7 participation keys and your connection list. Heart7 web participation cookies (h7k_) last 90 days; its language cookie (heart7_lang) lasts up to one year. Clearing browser data or uninstalling an app removes local data, but does not delete server records.

Who can see shared information?

Anyone with an Ask7 result link (ask7.kr/r/…) or Room7 result link can see the question and AI results. Entering exactly the same Ask7 question may reopen the same stored result. The only Ask7 list anyone can see without a link is “Today’s best”, which shows only questions whose asker turned on posting on the result screen (verified with the asker token issued to the device that received the result) and an operator then reviewed (see below).

Room7 leaderboards and the Hall of Fame show nicknames, scores, persuasion results and the relevant board. Only you can view the lines you submitted in ranked play.

Anyone with a Heart7 connection link (heart7.kr/p/…) can see both people’s nicknames, answers and results. The creator’s answers are hidden from the other person until they respond, and connection pages are not indexed by search engines. A link is not an authenticated private space for just two people: consider its visibility before forwarding it.

Likes, best comments and Today’s best (Ask7)

Real users can tap a like (👍) on each answer in an Ask7 result. When you like or unlike an answer, we store the result ID, the time the result was created, the answer ID, the question language, the time of the like and an irreversible IP hash mixed with a secret value instead of your IP address. The IP hash is used only so each person can like an answer once. Only per-answer totals are shown, never who liked. Likes are not available on “My situation” (personalised) results or on safety-restricted or sensitive results.

“AI likes” are simulated: AI panel members mark answers they agree with. To create them, the same question and context used for the AI answers are sent to OpenAI. They are not real people’s reactions and are always shown separately from real likes.

The best comment is chosen by the asker on their own device and is not stored on our servers. The chosen answer travels in the share link (the b value, an answer ID), so people who receive the link see it too. If no answer is chosen, the answer with the most AI and real likes combined is shown automatically.

“Today’s best” only considers questions whose asker turned on posting themselves on the result screen (off by default). Posting and withdrawing are verified with an asker token issued to that device when the result was created, so someone who only received the link cannot post it. Each candidate goes through automatic safety checks again (including OpenAI safety checks), and only items an operator reviews and approves are shown in public lists on ask7.kr, arh7.kr and the ARH7 app for 24 hours after approval. In these lists anyone can see the question text, the result (percentage and verdict), the best comment and like counts without a link. “My situation”, anonymous profiles and earlier follow-up questions are never listed, and results saved before this feature are not posted. A submission stores the result ID, the time the result was created, the chosen answer ID, language, a copy of the question, the check and approval status and times, and the submitter’s IP hash.

Anyone can report a listed question. A report stores the result ID, the time the result was created, an optional reason, the time of the report and the reporter’s IP hash, and each person counts once. A question reported by 3 different people is hidden automatically, and an operator can remove or reject any item at any time.

If you change your mind, you can withdraw it on the result screen of the device that posted it, and it leaves the list and the candidates right away. To have the records deleted as well, email namurobori@gmail.com with the result link or question to withdraw consent or ask for deletion. After checking, we remove it from the list without delay and delete the submission and report records. You can ask for like records to be deleted at the same address. We cannot delete copies made outside the service while it was listed, such as other people’s screenshots or copied text.

Email support ↗

How long information is kept

  • Ask7 questions, results and related data: for as long as the service operates; deleted without delay on request.
  • Ask7 likes, “Today’s best” submissions and reports (including IP hashes): kept while the service operates and deleted without delay on a deletion or withdrawal request. A “Today’s best” item stays in the public list for 24 hours after approval.
  • Room7 debate results: until a deletion request or service closure. Safety reports, user reports and daily usage records: deleted within one year of collection.
  • Room7 ranked play: debate-progress transcripts are deleted after seven days; run records (submitted lines, processing results, scores and IP hashes) within 90 days. Daily best scores and Hall of Fame entries remain until you delete them or the service closes.
  • Room7 “Watch an ad for one more round” verification records (from ARH7 app 1.3.0(8): ticket, date, IP hash, ad unit, transaction number, status and times): deleted after 30 days.
  • Heart7 nicknames, relationship, answers, results, creation time, IP hashes and participation-key hashes become eligible for automatic deletion 90 days after creation. Daily cleanup can take up to one additional day. Earlier deletion by a participant removes both people’s related information together.

Your rights and minimum age

You must be at least 14 to use the services. We delete related information if we learn it belongs to a child under 14. Contact namurobori@gmail.com to request access, correction, deletion or suspension of processing. Include your question, result or connection link so we can verify and process the request.

Room7 ranked records can be deleted in My records. Deleting a SLOX account permanently removes the shared slox.co.kr account, profile and ranked records. Heart7 participants can delete both people’s answers and results from their connection screen. See our deletion guide for the exact routes.

Delete account & data ↗

SLOX · ARH7

Need a hand?

Use this address for privacy questions and deletion requests, too.

namurobori@gmail.com ↗
ARH7 ↗
PrivacyTermsSupportDelete account & data

AI-generated conversations and perspectives. Not a real survey or a substitute for professional advice.
© 2026 SLOX · ARH7