1. Open **Manage Form Questions** on the left control dock interface.
2. Establish clear **Sub-Headings/Categories** to compartmentalize the active data schema.
3. Organize entries cleanly using the manual drag-and-drop **Sort** matrix.
4. Select **Manage Questions** → **+Add** under the correct category to specify field data types.

Asterisk (*): Mandates a hard field compliance gate. Ingestion paths lock completely until field validation parameters are successfully achieved.

Custom Elements: Total configuration control of structural pages (Introduction, Thank You page, Terms of Service, and Use Policy frameworks) resides under the native Content Management interface layer.

Activate your account by selecting a plan. The FREE plan provides full features to safely map data entry strategies prior to operational scaling.

Path: Settings > Choose Plan > Change Plan (Click the red down arrow to see other FREE & Fee-based plans.)

• Access: 15 Questions (Q/A) and up to 10 participants/users.
• Features: Survey template architecture, full customization metrics, real-time tracking, and downloadable CSV datasets via the native export engine.
• Reminders: Automated notification alerts dispatched prior to the conclusion of the active lifecycle window.

Total Questions/Members: Establishes the designated question capacity and total active respondent allocations bound to the current subscription level.

Expiration: Email warnings trigger 3 days prior to validation drop dates. Datasets remain accessible during active cycles; regular CSV administrative backups using our native flat-file tool are highly recommended.

Deactivation: Framework profiles without systematic renewal terms transition cleanly to a deactivated state.

No. Once an account deletion is initiated, the user's login configurations and administration profiles are permanently removed. To uphold our strict data minimization standards, all associated survey records enter a secure 90-day notification window before being completely purged from system infrastructure blocks. System parameters cannot be recovered after this mandatory verification timeline.

The Access Code acts as the baseline token barrier. Field respondents require this explicit string parameter to validate submissions straight from the interface glass.

Security Lockdown: Updating the Access Code is strictly limited to a **one-time** option under Settings > Company Profile > Edit. This restriction eliminates unstable token cycling and guarantees absolute multi-tenant environmental isolation.

Branding: Custom logo deployment accepts static PNG files with fixed dimensions of 300 × 300 px (Settings > Company Profile > Edit).

Password Recovery: Functional across both mobile and desktop portals for any configuration layer. Inactive accounts receive standard recovery assets displaying associated active user identities securely on screen to restore clear system visibility.

Manage environment logic via Settings > Site Settings > Registration Feature:

• ON (Registered): Requires credentialed entry. Respondents must pass a secure email and password challenge along with the token string parameter. Recommended for closed data testing groups.
• OFF (Anonymous): Requires only the global entry token code, completely separating user identity attributes from individual entry data rows to guarantee field privacy.

Total allowable plan volumes apply uniformly across all omni-channel tracking variations.

Future-Block Logic: To ensure absolute forensic and audit accuracy, the user interface logic automatically blocks entry selectors from capturing any transactional metric beyond the active time framework.

Explicit Field Clearing: Date options feature an active delete tool to let users instantly clear erroneous inputs instead of committing invalid parameters to the dataset.

Captcha Enforcement: Before any intake packet or dataset row executes, a mechanical security verification challenge must be completed on the glass to isolate and completely drop automated script or bot traffic.

Self-Email Receipts: The internal Admin Notes operation offers a structured transaction verification layer, instantly firing a timestamped confirmation receipt directly to the user's primary mailbox upon submission.

Location data collection is currently available exclusively on mobile devices as an optional question field that client administrators can enable if their specific project requires it. This feature is not implemented for laptops or desktop computers. Restricting this capability on desktop platforms avoids unnecessary third-party development costs while perfectly preserving a streamlined, "born clean" presentation layer for your main administrative dashboard.

Yes. Because the web form treats these as distinct pieces of data, you must create them as separate question fields during your setup. The Location Field is created as a standard text entry question for mobile users to log geographic details if the admin chooses to collect it, while the Decimal Numerical Field is created as a separate, dedicated text/number field to capture the specific decimal time format required for your data ledger.

Yes. To maintain proper tracking across different devices, the Pure Calendar Date must be built as its own independent question parameters in your survey editor.

The fields adapt automatically based on the device to keep development cost-effective. The Mobile App includes the active Location text field, utilizes a built-in native calendar feature, and restricts decimal fields tightly to a numeric num pad. The Computer/Laptop view features NO Location field to save on development costs, and guides users on both date and decimal text inputs using clear, visual formatting examples.

Administrative sovereignty is strictly enforced. The platform infrastructure maintains no backdoors; platform management possesses zero direct or indirect means of data retrieval or forensic lookup. Environmental data tracking validation remains isolated under the exclusive authority of the primary account holder.

In accordance with our core principles of data sovereignty and zero-retention field deployment, RealTimeDataCollector enforces a strict accounts lifecycle safety window. Inactive spaces or accounts flagged for removal trigger a structured 90-day notification and tracking window.

The moment account deletion is initiated, all active access tokens are instantly destroyed, rendering the underlying encrypted dataset completely locked, unreadable, and dead. The data is entirely inaccessible to anyone, as the system can no longer accept or execute a readable compilation request. Upon the final conclusion of the 90-day window, all corresponding field data streams and ingest schemas are permanently cleared from system infrastructure blocks to maintain clean, isolated database nodes.

• "Born Clean" Data Architecture: Restricts data entry at the user interface glass so spreadsheets are pristine the second they hit the database.
• No-Coding Environment: A 100% visual, drag-and-drop form builder for admins and field practitioners to deploy forms instantly without writing code.
• Automated Security Guardrails: Integrated Captcha verification challenges before submission to block automated bot spam and prevent database corruption.

Every single row is automatically stamped with three immutable markers:

• SHA-256 Cryptographic Hash: Unique, immutable forensic fingerprint ensuring data integrity at the exact moment of entry.
• ZULU Date-Time Timestamp: Automated UTC timestamp tracking the exact millimetric moment of submission flawlessly.
• Sequential Serial Number: Strict serial ordering chronological tracking for precise, tamper-proof audit trails across long-term longitudinal studies.

• Location Data Capture: Outputs strict, space-free numeric coordinates (Latitude,Longitude,Altitude,Accuracy) for error-free GIS/ArcGIS mapping.
• Standardized Dates: Restricts quantitative calendar metrics strictly to standardized formats (YYYY-MM-DD).
• Verified Media: Restricts uploads strictly to secure images (JPEG/PNG) or PDF formats only to completely prevent system corruption prior to project approval.
• Null Cell Standards: Outputs explicit "null" allocations in absent cells where blank choices are set directly to NULL to preserve dataset integrity.