FAQ

1. About the app

What is InView?

InView is a public profile analysis app by C6ISR. It lets you search a username, open the profile detail screen, view public profile information, open profile photos, and review available posts, stories, highlights, relationship snapshots, activity timing, and engagement summaries.

The app works only with data that is available on the internet through public profile and public media responses. It does not access private internal systems and does not show information that is not returned to the app by those public data services.

2. Bugs, errors, and missing data

Why does a screen look wrong or show an error?

Temporary errors can happen due to connectivity issues, platform changes, or a brief service interruption. First, make sure you are on the latest app version, then restart the app and try again. If the issue continues, contact support with a screenshot and a short description.

3. Common questions about data

How does InView load a profile?

When you enter a username, the app sends that username to the profile lookup service. If the request succeeds, InView saves the returned profile fields locally for the current view: username, full name, biography, post count, follower count, following count, profile photo URL, private account status, verified status, and the last update time.

What data does InView use?

InView uses public information that is available on the internet for the searched profile and its returned public media. This can include profile fields, public post metadata, public story or highlight items, public follower/following counts, public relationship list snapshots when available, and public engagement signals such as likes and comments returned for analyzed posts.

Private, deleted, expired, restricted, or non-returned data is not used in the app's calculations because the app cannot see it.

How often does data refresh?

Profile data refreshes when you search or open a profile again. The app records the refresh time as the last update time. Post, story, and highlight screens are loaded from the available response at the time you open those screens.

Can InView see private data?

No. InView can only show data returned to the app by its services. If a profile or media item is not returned, unavailable, private, deleted, expired, or blocked by the service response, it cannot be shown in the app.

Are these official platform numbers?

No. The numbers shown in InView are the values returned to the app by its lookup services. InView displays those returned values; it does not create official platform statistics.

4. Feature explanations

Profile Information

The profile screen is built from the profile response for the searched username. InView stores and displays the username, full name, biography, profile image, post count, follower count, following count, private/open status, verified status, and last update time.

Stories

The story screen uses the public story items returned for the selected profile. If story items are available, InView opens them in the story viewer. If no story items are returned, the app shows that no story was found.

Story availability depends on the response at the time you open the screen. Expired, unavailable, or non-returned story items cannot be displayed.

Highlights

The highlight list is loaded separately from profile data. InView opens the returned highlight items and then loads the media inside the selected highlight when you choose one.

Posts and Media

The posts screen loads public media by the selected profile identifier. InView displays returned photos, videos, albums, and reels where available. The post viewer shows the returned media file and caption/detail fields when present.

Profile Photo

The full profile photo view uses the profile image URL returned with the profile response. If a higher quality image is available in the response or through the image URL used by the app, InView opens that image in the photo viewer.

Followers and Following Counts

The follower and following numbers are not calculated by comparing local lists. They are the counts returned in the profile response and displayed on the profile screen.

Followers and Following Lists

When public relationship data is available, InView stores a timestamped snapshot of returned follower and following items. Changes such as new or missing items depend on comparing available snapshots. If a list is private, incomplete, restricted, or not returned, the app cannot calculate a complete relationship change result.

Admirers

Admirers are calculated from public engagement signals on analyzed posts. InView reads the latest stored public post snapshot for the selected profile, analyzes recent unique posts, and checks the returned public liker and commenter lists for those posts.

Each returned like or comment appearance gives that account engagement points. Accounts that appear more often as likers or commenters receive a higher score. The searched profile itself is excluded from the ranking, then accounts are sorted by score and shown as the strongest public admirers for that analyzed snapshot.

This is an engagement-based estimate from available public data. It is not a complete list of every person who may have viewed or interacted with the profile.

Private and Open Accounts

InView checks the returned private account flag and media count. The app uses those values to decide whether to show open account media, show a private account warning, or show premium/private-account messaging.

Last Activities

Last Activities are built from public activity events saved by the app while loading profile and media data. These events can come from returned profile activity timestamps, public stories, highlights, and posts. Each activity item keeps its source, title, event time, snapshot time, and related profile identifier when available.

Last Seen

Last Seen is an estimated timing prediction, not an exact online status. InView looks at the recent public activity event times saved for the profile, sorts them from newest to oldest, and measures the time gaps between those events.

When enough activity events exist, the app uses the median gap between events to estimate the next likely activity window. When there is not enough timing history, it falls back to source-based timing assumptions for profile, story, highlight, or post activity. The app then creates an approximate status window and confidence value based on the amount and variety of available activity data.

5. Purchases and refunds

How do purchases work?

Subscriptions and in-app purchases are handled by the app store (Apple App Store or Google Play). Pricing, billing periods, and renewal terms are shown before you confirm a purchase.

How do I cancel a subscription?

You can manage or cancel your subscription through your app store account settings. Canceling stops future renewals but does not remove access for the current paid period.

How do refunds work?

Refunds are managed by the app store, not by C6ISR. Please request refunds directly through your Apple or Google Play purchase history. If you need help locating the order or understanding a charge, contact us and we will do our best to assist.

6. Support

Have more questions? Contact us at support@c6isr.xyz and include your device model, app version, and a short description of the issue.