The following Part C Project Steps are the logical steps required for the transfer of the Customer ILO File and other associated parts of the Customer Information (i.e. “the Package”) into the I-LIVE-ON.Backend’s AWS S3 / Database. Once the Package is in AWS S3 / Database and Part C is complete then future Part D processing steps with be required (future work). I-LIVE-ON has a standard Consulting Contract that the Vendor will be required to sign as part of the engagement process.

The Diagram below shows the overall System Architecture for Part C that the Vendor may use as a Guide. The Vendor shall use a I-LIVE-ON Email address (provided by us) and shall initially setup the following:

i) a separate I-LIVE-ON AWS S3 and Database “facility” within our existing AWS account,

ii) a separate access to our System, and

iii) a separate access to a copy of this I-LIVE-ON.Com WordPress webpage (which shall be modified into a Production version).

so they may create an environment for them to dev / test and complete the work required for a production system as part of the I-LIVE-ON.Backend.



STEP C1: Drag and Drop your Life Story ILO File (that has been saved on your Desktop by the I-LIVE-ON.App) into the Drag & Drop Upload Box below (refer Note A):


STEP C2: Select your Life Story parameters:

Customer Birthyear (Note 1)

Passcode (Note 2)

Passcode Expiry Date (Note 3)

Life Story Activation Date (Note 4)


STEP C3: Select the Life Story SKU (with ILO File Size (in GB), Term of Service (in Years) and Presentation Style).


STEP C4: Just click on the “LifeStory Subscription Order” Radio Button below and place your order:

By clicking on the LIFESTORY SUBSCRIPTION SERVICE ORDER Radio Button above and ordering the Service, you are explicitly agreeing to the End License User Agreement (EULA), Privacy Policy (with associated Cookie Policy), and the Terms & Conditions.


STEP C5: Copy of Customer ILO file is then saved in AWS S3 Storage, and is never modified. Check if valid ILO (refer Note B), with appropriate notification whether the ILO File is accepted or rejected prior to payment acceptance.

STEP C6: Select “Package” info stored into AWS Database (refer C6 Spec).


Note 1: Birthyear is recommended as it will help differentiate the Customer vs other people who share your same surname. Your Life Story Profile Name will be used to help Search Engines find your Life Story, coded as LifeStoryProfileName/Birthyear/AssignedGUID.

Note 2: The Customer may assign a Passcode code that will be associated with the AssignedGUID (which is a unique code that has been assigned to your Life Story ILO File), which allows Users to see the PRIVATE Pages when viewing the Customer Life Story. If no Passcode is provided, then the PRIVATE Pages will not be viewable on the Internet.

Note 3: The Customer may wish to set a date wherein their Passcode expires, so that all the PRIVATE and PUBLIC Categories of their Life Story will be on full display in the future. If no expiry date is set, then the contents of all the PRIVATE Categories will be remain accessible only via the Passcode.

Note 4: The Customer may wish to set a date when their Life Story is published on the Internet. If no publish date is set, then their Life Story is published as soon as the I-LIVE-ON.Backend has processed the Customer Life Story Subscription request (usually within 48 to 72 hours).


Some Coding Logic Instructions

Note A: The Drag & Drop ILO File, Life Story parameters and HTML Shopify Payment customer information, will all be transmitted (via encryption) to the AWS S3 Bucket as a complete “PACKAGE”.

Note B: The input logic must then 1. check the size of the file, and 2. ensure it is an ILO extension, before accepting payment. THEN assuming 1. and 2. are verified, then move to the next step wherein payment is verified / processed. Finally, proceed with transmitting the PACKAGE into the AWS S3 Bucket – using the GUID name of the ILO as the specific S3 Bucket name for the Customer information.